1. field size
- Posted by gwalters at sc.rr.com
Jul 26, 2001
This is a multi-part message in MIME format.
------=_NextPart_000_00D9_01C115D7.4F2596E0
charset="Windows-1252"
Can someone tell me how to control the number of chars that can be =
entered in a field? Now the entered items continue to scroll. (i.e. for =
the state i would only allow 2chars to be entered)
...george
------=_NextPart_000_00D9_01C115D7.4F2596E0
charset="Windows-1252"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3105.105" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Can someone tell me how to control the number of =
chars that=20
can be entered in a field? Now the entered items continue to scroll. =
(i.e. for=20
the state i would only allow 2chars to be entered)</FONT></DIV>
<DIV> </DIV>
------=_NextPart_000_00D9_01C115D7.4F2596E0--
2. Re: field size
- Posted by irvm at ellijay.com
Jul 26, 2001
On Thursday 26 July 2001 13:31, gwalters at sc.rr.com wrote:
> Can someone tell me how to control the number of chars that can be entered
> in a field? Now the entered items continue to scroll. (i.e. for the state i
> would only allow 2chars to be entered)
>
> ...george
>
Here's a clip from Brian Broker in the archives:
On Wed, 6 Sep 2000 18:10:41 +0200, bobspringett wrote:
>Could someone please advise me how to limit the number of characters
entered in a one line EDIT CONTROL.
>Regards
>Bob
Use SendMessage( ControlID, EM_LIMITTEXT, limit_number, NULL )
where 'limit_number' is your limit.
Example:
include win32lib.ew
constant
Win = create( Window, "limit", 0, Default, Default, 200, 100, 0 ),
Box = create( EditText, "", Win, 10, 10, 180, 20, 0 )
procedure onOpen_Win()
atom nil
-- limit of 10 characters in Box --
nil = sendMessage( Box, EM_LIMITTEXT, 10, NULL )
end procedure
onOpen[Win] = routine_id( "onOpen_Win" )
WinMain( Win, Normal )
-- Brian
3. Re: field size
- Posted by gwalters at sc.rr.com
Jul 26, 2001
how in the world would you have found this. The Win32lib.doc shows the
sendMessage with several arguments but no detail at all. is their some other
doc what would go into more detail?
..george
----- Original Message -----
From: <irvm at ellijay.com>
To: "EUforum" <EUforum at topica.com>
Subject: Re: field size
> >
>
> On Thursday 26 July 2001 13:31, gwalters at sc.rr.com wrote:
>
> > Can someone tell me how to control the number of chars that can be
entered
> > in a field? Now the entered items continue to scroll. (i.e. for the
state i
> > would only allow 2chars to be entered)
> >
> > ...george
> >
>
> Here's a clip from Brian Broker in the archives:
>
> On Wed, 6 Sep 2000 18:10:41 +0200, bobspringett wrote:
>
> >Could someone please advise me how to limit the number of characters
> entered in a one line EDIT CONTROL.
> >Regards
> >Bob
>
> Use SendMessage( ControlID, EM_LIMITTEXT, limit_number, NULL )
>
> where 'limit_number' is your limit.
>
> Example:
>
> include win32lib.ew
>
> constant
> Win = create( Window, "limit", 0, Default, Default, 200, 100, 0 ),
> Box = create( EditText, "", Win, 10, 10, 180, 20, 0 )
>
> procedure onOpen_Win()
> atom nil
> -- limit of 10 characters in Box --
> nil = sendMessage( Box, EM_LIMITTEXT, 10, NULL )
> end procedure
> onOpen[Win] = routine_id( "onOpen_Win" )
>
> WinMain( Win, Normal )
>
> -- Brian
>
>
> >
> >
> >
4. Re: field size
- Posted by irvm at ellijay.com
Jul 26, 2001
On Thursday 26 July 2001 15:02, gwalters at sc.rr.com wrote:
> how in the world would you have found this. The Win32lib.doc shows the
> sendMessage with several arguments but no detail at all. is their some
> other doc what would go into more detail?
A lot of information is stored in the archives from this mailing list,
going back to 1996. Junko has written a nice search engine which
can often find answers if you can think of the right words to search.
http://rapideuphoria.com/listserv.htm
Regards,
Irv
5. Re: field size
- Posted by euman at bellsouth.net
Jul 26, 2001
MICROSOFT PLATFORM SOFTWARE DEVELOPMENT KIT
MS-PLATFORM SDK for short
start you search for it here>
http://www.msdn.microsoft.com
Win32lib docs will not tell you what you will need to do most of the stuff
it is currently capable of. I really suggest going about this the hard way
learn the SDK first. I never realized the potential until I did this.
Experiment with the couple demo's supplied by RDS for Euphoria
and grab a copy of Jacques Deschenes API wrappers to look at while
you read thru the SDK. Grab some books on Windows programming
I suggest Window programming annotative archives as a beginning
point the authors name is Herbert Schildt the book has code thats
written for C++ but, there is an example of a couple chapters on the
user contrib page written by me, Euman.
Of course, if you do this the hard way first, you wont need win32lib....:)
This info brought to you by someone who, like you, struggled hard at first.
As time passes you'll catch on as I have. I still stumble on parts of
th SDK but thats because either the documentation isnt real clear to me
or doesnt exist. In these cases I search the Web for examples and every so often
I
take a peak at Win32lib to see how those guys did it.
You may find that learning what a few of the Euphoria commands do.
c_func
c_proc
define_c_func
define_c_proc
call_back
allocate
allocate_string
free
poke
peek
poke4
peek4s
peek4u
just a small list but these are the main commands used to interact with the API.
This should take you a day or two to read and write some basic samples
to test them out.
Euman
euman at bellsouth.net
Advocate for Euphoria API
>
> how in the world would you have found this. The Win32lib.doc shows the
> sendMessage with several arguments but no detail at all. is their some other
> doc what would go into more detail?
>
> ..george
6. Re: field size
- Posted by gwalters at sc.rr.com
Jul 26, 2001
thanks for the references. I'll look them up. Probably BN will have some of
them.
..george
----- Original Message -----
From: <euman at bellsouth.net>
To: "EUforum" <EUforum at topica.com>
Subject: Re: field size
>
>
> MICROSOFT PLATFORM SOFTWARE DEVELOPMENT KIT
>
> MS-PLATFORM SDK for short
>
> start you search for it here>
>
> http://www.msdn.microsoft.com
>
> Win32lib docs will not tell you what you will need to do most of the stuff
> it is currently capable of. I really suggest going about this the hard way
> learn the SDK first. I never realized the potential until I did this.
>
> Experiment with the couple demo's supplied by RDS for Euphoria
> and grab a copy of Jacques Deschenes API wrappers to look at while
> you read thru the SDK. Grab some books on Windows programming
> I suggest Window programming annotative archives as a beginning
> point the authors name is Herbert Schildt the book has code thats
> written for C++ but, there is an example of a couple chapters on the
> user contrib page written by me, Euman.
>
> Of course, if you do this the hard way first, you wont need win32lib....:)
>
> This info brought to you by someone who, like you, struggled hard at
first.
> As time passes you'll catch on as I have. I still stumble on parts of
> th SDK but thats because either the documentation isnt real clear to me
> or doesnt exist. In these cases I search the Web for examples and every so
often
> I
> take a peak at Win32lib to see how those guys did it.
>
> You may find that learning what a few of the Euphoria commands do.
>
> c_func
> c_proc
> define_c_func
> define_c_proc
> call_back
> allocate
> allocate_string
> free
> poke
> peek
> poke4
> peek4s
> peek4u
>
> just a small list but these are the main commands used to interact with
the API.
> This should take you a day or two to read and write some basic samples
> to test them out.
>
> Euman
> euman at bellsouth.net
> Advocate for Euphoria API
>
>
>
> >
> > how in the world would you have found this. The Win32lib.doc shows the
> > sendMessage with several arguments but no detail at all. is their some
other
> > doc what would go into more detail?
> >
> > ..george
>
>
>
>
>
>
>
7. Re: field size
- Posted by gwalters at sc.rr.com
Jul 26, 2001
BTW how much is a MS SDK?? I pay $500/yr for Theos...
..george
----- Original Message -----
From: <euman at bellsouth.net>
To: "EUforum" <EUforum at topica.com>
Subject: Re: field size
>
>
> MICROSOFT PLATFORM SOFTWARE DEVELOPMENT KIT
>
> MS-PLATFORM SDK for short
>
> start you search for it here>
>
> http://www.msdn.microsoft.com
>
> Win32lib docs will not tell you what you will need to do most of the stuff
> it is currently capable of. I really suggest going about this the hard way
> learn the SDK first. I never realized the potential until I did this.
>
> Experiment with the couple demo's supplied by RDS for Euphoria
> and grab a copy of Jacques Deschenes API wrappers to look at while
> you read thru the SDK. Grab some books on Windows programming
> I suggest Window programming annotative archives as a beginning
> point the authors name is Herbert Schildt the book has code thats
> written for C++ but, there is an example of a couple chapters on the
> user contrib page written by me, Euman.
>
> Of course, if you do this the hard way first, you wont need win32lib....:)
>
> This info brought to you by someone who, like you, struggled hard at
first.
> As time passes you'll catch on as I have. I still stumble on parts of
> th SDK but thats because either the documentation isnt real clear to me
> or doesnt exist. In these cases I search the Web for examples and every so
often
> I
> take a peak at Win32lib to see how those guys did it.
>
> You may find that learning what a few of the Euphoria commands do.
>
> c_func
> c_proc
> define_c_func
> define_c_proc
> call_back
> allocate
> allocate_string
> free
> poke
> peek
> poke4
> peek4s
> peek4u
>
> just a small list but these are the main commands used to interact with
the API.
> This should take you a day or two to read and write some basic samples
> to test them out.
>
> Euman
> euman at bellsouth.net
> Advocate for Euphoria API
>
>
>
> >
> > how in the world would you have found this. The Win32lib.doc shows the
> > sendMessage with several arguments but no detail at all. is their some
other
> > doc what would go into more detail?
> >
> > ..george
>
>
>
>
>
>
>
8. Re: field size
- Posted by euman at bellsouth.net
Jul 26, 2001
I got my copy for free / just D/L what you need.
Euman
euman at bellsouth.net
>
> BTW how much is a MS SDK?? I pay $500/yr for Theos...
>
> ..george
9. Re: field size
This is a multi-part message in MIME format.
------=_NextPart_000_002D_01C11668.9F9163C0
charset="Windows-1252"
Hi George,
Its morning again here in Melbourne Australia.
When I saw your screen layout, I could see the same old problems that =
people in the USA make. The common thing for programmers (regardless of =
where they come from) is to make assumptions about certain data that =
don't hold up when the data is moved to different locales.
For example, in Australia, State codes are 3-characters long, and ZIP =
codes (called postcodes here) are 4-chars long, and telephone numbers =
are 8-chars long, dates are written as DAY/MONTH/YEAR sequence, etc.....
It might do you some good to ponder if these sort of locale-influenced =
data items need special treatment.
Of course, there's the 'character codeset' problem too, and the how much =
screen space needed for different languages?
----- Original Message -----=20
From: gwalters at sc.rr.com=20
To: EUforum=20
Sent: Friday, July 27, 2001 3:31 AM
Subject: field size
...george
This email was sent to: ddparnell at bigpond.com
------=_NextPart_000_002D_01C11668.9F9163C0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 5.50.4611.1300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi George,</FONT></DIV>
<DIV><FONT face=3DArial size=3D2>Its morning again here in Melbourne=20
Australia.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>When I saw your screen layout, I =
could see the=20
same old problems that people in the USA make. The common thing for =
programmers=20
(regardless of where they come from) is to make assumptions about =
certain data=20
that don't hold up when the data is moved to different =
locales.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>For example, in Australia, State codes =
are=20
3-characters long, and ZIP codes (called postcodes here) are 4-chars =
long, and=20
telephone numbers are 8-chars long, dates are written as DAY/MONTH/YEAR=20
sequence, etc.....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It might do you some good to ponder if =
these sort=20
of locale-influenced data items need special treatment.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Of course, there's the 'character =
codeset' problem=20
too, and the how much screen space needed for different =
languages?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dgwalters at sc.rr.com=20
href=3D"mailto:gwalters at sc.rr.com">gwalters at sc.rr.com</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DEUforum at topica.com=20
href=3D"mailto:EUforum at topica.com">EUforum</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, July 27, 2001 =
3:31 AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> field size</DIV>
<A =
the state i would only allow 2chars to be entered)</FONT></DIV>
<DIV> </DIV>
<DIV><FONT =
size=3D2>...george</FONT></DIV><PRE>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<A =
href=3D"http://topica.com/u/?b1dd66.${encoded_sub_id}">http://topica.com/=
u/?b1dd66.b2mL5y</A>
Or send an email To: EUforum-unsubscribe at topica.com
This email was sent to: ddparnell at bigpond.com
<A =
------=_NextPart_000_002D_01C11668.9F9163C0--
10. Re: field size
- Posted by gwalters at sc.rr.com
Jul 26, 2001
This is a multi-part message in MIME format.
------=_NextPart_000_0158_01C115F9.42677140
charset="Windows-1252"
Well Derick, it's beer time here in USA, SC (5:30pm). I'm about burned =
out at this point...Info is falling out my ears..
..george
----- Original Message -----=20
From: Derek Parnell=20
To: EUforum=20
Sent: Thursday, July 26, 2001 4:51 PM
Subject: Re: field size
=20
When I saw your screen layout, I could see the same old problems that =
people in the USA make. The common thing for programmers (regardless of =
where they come from) is to make assumptions about certain data that =
don't hold up when the data is moved to different locales.
=20
For example, in Australia, State codes are 3-characters long, and ZIP =
codes (called postcodes here) are 4-chars long, and telephone numbers =
are 8-chars long, dates are written as DAY/MONTH/YEAR sequence, etc.....
=20
It might do you some good to ponder if these sort of locale-influenced =
data items need special treatment.
=20
Of course, there's the 'character codeset' problem too, and the how =
much screen space needed for different languages?
=20
----- Original Message -----=20
From: gwalters at sc.rr.com=20
To: EUforum=20
Sent: Friday, July 27, 2001 3:31 AM
Subject: field size
...george
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3Dhttp://topica.com/u/?b1dd66.b2mL5y=
Or send an email To: EUforum-unsubscribe at topica.com
This email was sent to: ddparnell at bigpond.com
Or send an email To: EUforum-unsubscribe at topica.com
This email was sent to: gwalters at sc.rr.com
=3D
------=_NextPart_000_0158_01C115F9.42677140
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3105.105" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Well Derick, it's beer time here in USA, SC =
(5:30pm). I'm=20
about burned out at this point...Info is falling out my =
ears..</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>..george</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:ddparnell at bigpond.com" =
title=3Dddparnell at bigpond.com>Derek=20
Parnell</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:EUforum at topica.com"=20
title=3DEUforum at topica.com>EUforum</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, July 26, 2001 =
4:51=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: field size</DIV>
<A =
<DIV><FONT face=3DArial size=3D2>When I saw your screen layout, I =
could see=20
the same old problems that people in the USA make. The common thing =
for=20
programmers (regardless of where they come from) is to make =
assumptions about=20
certain data that don't hold up when the data is moved to different=20
locales.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>For example, in Australia, State =
codes are=20
3-characters long, and ZIP codes (called postcodes here) are 4-chars =
long, and=20
telephone numbers are 8-chars long, dates are written as =
DAY/MONTH/YEAR=20
sequence, etc.....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It might do you some good to ponder =
if these sort=20
of locale-influenced data items need special treatment.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Of course, there's the 'character =
codeset'=20
problem too, and the how much screen space needed for different=20
languages?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:gwalters at sc.rr.com"=20
title=3Dgwalters at sc.rr.com>gwalters at sc.rr.com</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:EUforum at topica.com"=20
title=3DEUforum at topica.com>EUforum</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, July 27, 2001 =
3:31=20
AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> field size</DIV><A =
FONT=20
entered)< be to 2chars allow only would i state the>
<DIV></DIV>
<DIV> </DIV>
<DIV><FONT =
size=3D2>...george</FONT></DIV><PRE>=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
<A =
href=3D"http://topica.com/u/?b1dd66.${encoded_sub_id}">http://topica.com/=
u/?b1dd66.b2mL5y</A>
Or send an email To: EUforum-unsubscribe at topica.com
This email was sent to: ddparnell at bigpond.com
<A =
<A =
href=3D"http://topica.com/u/?b1dd66.${encoded_sub_id}">http://topica.com/=
u/?b1dd66.b2IexA</A>
Or send an email To: EUforum-unsubscribe at topica.com
This email was sent to: gwalters at sc.rr.com
<A =
------=_NextPart_000_0158_01C115F9.42677140--
11. Re: field size
This is a multi-part message in MIME format.
------=_NextPart_000_0042_01C11640.78D61AA0
charset="Windows-1252"
Hi, George -well past midnight in Buenos Aires, and freezing cold. =
Still, a beer would be welcome -man does not live by coffee alone.
Here we have one-letter provincial codes, but they aren't quite well =
known, so most apps will offer you the more familiar (read traditional, =
and longer) abbreviations, as in 'Bs.As.' for Buenos Aires, 'Cba.' for =
C=F3rdoba, and so on. Like the oldtime Mass. and Fla. and Ore. in the =
USA.
The c=F3digos postales have recently changed from 4 to 8 chars (one =
letter, four numbers, three letters -looks quite British).
Standard telephone numbers are eight chars long. Add two chars for =
cellphones, up to four for area codes, at least a couple more for some =
strange special combinations, and changing all the time. I'd assign no =
less than 20 chars.
As in Derek's Australia, dates are always day/month/year (again, British =
influence). Watch out: Japan uses year/month/day! The hour is always =
based on the 24-hour clock. Coloquially, you will hear 'diez de la =
ma=F1ana' for 10 a.m., or 'nueve de la noche' for 9 p.m., but never in =
writing, never on a document -it's not just custom, it's the law.
Quite a chore, I know. Not even stable, since such conventions change =
all the time. I'd try for a manually editable config file (for =
experienced users), or a simple interface to same, much like the =
'International' applet in Windows. Or don't American versions carry it?
Gerardo
----- Original Message -----=20
From: gwalters at sc.rr.com=20
To: EUforum=20
Sent: Thursday, July 26, 2001 6:34 PM
Subject: Re: field size
Well Derick, it's beer time here in USA, SC (5:30pm). I'm about burned =
out at this point...Info is falling out my ears..
..george
----- Original Message -----=20
From: Derek Parnell=20
To: EUforum=20
Sent: Thursday, July 26, 2001 4:51 PM
Subject: Re: field size
When I saw your screen layout, I could see the same old problems =
that people in the USA make. The common thing for programmers =
(regardless of where they come from) is to make assumptions about =
certain data that don't hold up when the data is moved to different =
locales.
For example, in Australia, State codes are 3-characters long, and =
ZIP codes (called postcodes here) are 4-chars long, and telephone =
numbers are 8-chars long, dates are written as DAY/MONTH/YEAR sequence, =
etc.....
It might do you some good to ponder if these sort of =
locale-influenced data items need special treatment.
Of course, there's the 'character codeset' problem too, and the how =
much screen space needed for different languages?
------=_NextPart_000_0042_01C11640.78D61AA0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Dwindows-1252">
<META content=3D"MSHTML 5.50.4134.600" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>Hi, George -well past midnight in =
Buenos=20
Aires, and freezing cold. Still, a beer would be welcome -man does not =
live by=20
coffee alone.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Here we have one-letter provincial =
codes, but they=20
aren't quite well known, so most apps will offer you the more familiar =
(read=20
traditional, and longer) abbreviations, as in 'Bs.As.' for Buenos Aires, =
'Cba.'=20
for C=F3rdoba, and so on. Like the oldtime Mass. and Fla. and Ore. in =
the=20
USA.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The c=F3digos postales have recently =
changed from 4=20
to 8 chars (one letter, four numbers, three letters -looks quite=20
British).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Standard telephone numbers are eight =
chars long.=20
Add two chars for cellphones, up to four for area codes, at least a =
couple more=20
for some strange special combinations, and changing all the time.=20
I'd assign no less than 20 chars.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>As in Derek's Australia, dates are =
always=20
day/month/year (again, British influence). Watch out: Japan uses =
year/month/day!=20
</FONT><FONT face=3DArial size=3D2>The hour is always based on the =
24-hour clock.=20
Coloquially, you will hear 'diez de la ma=F1ana' for 10 a.m., or 'nueve =
de la=20
noche' for 9 p.m., but never in writing, never on a document -it's not =
just=20
custom, it's the law.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Quite a chore, I know. Not even stable, =
since such=20
conventions change all the time. I'd try for a manually editable config =
file=20
(for experienced users), or a simple interface to same, much like the=20
'International' applet in Windows. Or don't American versions carry=20
it?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Gerardo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dgwalters at sc.rr.com=20
href=3D"mailto:gwalters at sc.rr.com">gwalters at sc.rr.com</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DEUforum at topica.com=20
href=3D"mailto:EUforum at topica.com">EUforum</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, July 26, 2001 =
6:34=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: field size</DIV>
<DIV><BR></DIV>
<DIV><FONT size=3D2>Well Derick, it's beer time here in USA, SC =
(5:30pm). I'm=20
about burned out at this point...Info is falling out my =
ears..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>..george</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"PADDING-RIGHT: 0px; PADDING-LEFT: 5px; MARGIN-LEFT: 5px; =
BORDER-LEFT: #000000 2px solid; MARGIN-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A title=3Dddparnell at bigpond.com =
href=3D"mailto:ddparnell at bigpond.com">Derek=20
Parnell</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
title=3DEUforum at topica.com=20
href=3D"mailto:EUforum at topica.com">EUforum</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, July 26, 2001 =
4:51=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: field =
size</DIV><FONT=20
face=3DArial size=3D2>When I saw your screen layout, I could =
see the same=20
old problems that people in the USA make. The common thing for =
programmers=20
(regardless of where they come from) is to make assumptions about =
certain=20
data that don't hold up when the data is moved to different =
locales.</FONT>
<DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>For example, in Australia, State =
codes are=20
3-characters long, and ZIP codes (called postcodes here) are 4-chars =
long,=20
and telephone numbers are 8-chars long, dates are written as =
DAY/MONTH/YEAR=20
sequence, etc.....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It might do you some good to ponder =
if these=20
sort of locale-influenced data items need special =
treatment.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Of course, there's the 'character =
codeset'=20
problem too, and the how much screen space needed for different=20
languages?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><A the state i would only =
allow 2chars=20
to be entered)< FONT><FONT=20
------=_NextPart_000_0042_01C11640.78D61AA0--
12. Re: field size
- Posted by gwalters at sc.rr.com
Jul 27, 2001
This is a multi-part message in MIME format.
------=_NextPart_000_0017_01C11676.1E0FF9C0
charset="Windows-1252"
Well Gerardo, it's coffee time now (Colombian), 6:20 am and I'm back on =
it. Summer here, and we've had a very pleasant cool one so far. It's =
been in the upper 80's mostly... a few days in the lower 90's.... quite =
unusual. A couple of years ago it was 105 for a week....but that is =
unusual also.
The date thing could be handled with a date form switch, the phone by =
just a longer free form field and so could the state/province field. =
There are more serious issues of an accounting nature probably with =
payroll and the general ledger. For example our GL has all month's of =
the year open so you can go back and repair mistakes and redo =
financials, but in Venezuela once you close the month it's illegal to go =
back. (I consulted with a business there several years ago).
The OS I've been using (Theos... www.theos-software.com ) is =
international and has some presence in SA but mostly in Europe and Spain =
(www.theos.es) in particular. Spain does a lot of the development on the =
windows side. Theos has a client program that connects to a Theos server =
(tcp/ip connection written by AST in Spain), something like a smart =
terminal emulator. We can then have PC's for workstations and our =
software is point and click (on colored words) although it is not GUI. =
The basic problem that I and a lot of other dealers have is we can only =
take advantage of products in the theos environment, which is not a lot. =
Like myself, the dealers have a huge development effort to change since =
the basic they have is so complete and nothing similar or even close is =
available elsewhere.
So far I like EU, but it has some limitations that I would like to see =
improved. My (and Lucy's) programming style heavily uses =
select/case/cend...and EU being so structured i'm supprised that it =
doesen't have it.
select some.var
case 'a"
do something
case 'b'
do something
case 'c'
do something
otherwise
catch all here
cend .....or ala EU end select
I would also like to see variable names use periods...like =
'customer.name', 'customer.address' instead of customer_address. Not a =
big issue with this one just personal preference. And the 'goto label' =
issue... I'll have to sit this one out. It's the biggest road block in =
porting to EU to get something as a starting point to continue with and =
make complete redo's a piece at a time. And lastly as Irv points out a =
multiuser capability with a data base with record and file locking. I'm =
hoping that some of the contributions of others will solve this. I see =
that a 2.3 is on the way. I wonder what new things it will contain.=20
..george
----- Original Message -----=20
From: Gerardo=20
To: EUforum=20
Sent: Friday, July 27, 2001 1:04 AM
Subject: Re: field size
=20
Here we have one-letter provincial codes, but they aren't quite well =
known, so most apps will offer you the more familiar (read traditional, =
and longer) abbreviations, as in 'Bs.As.' for Buenos Aires, 'Cba.' for =
C=F3rdoba, and so on. Like the oldtime Mass. and Fla. and Ore. in the =
USA.
=20
The c=F3digos postales have recently changed from 4 to 8 chars (one =
letter, four numbers, three letters -looks quite British).
=20
Standard telephone numbers are eight chars long. Add two chars for =
cellphones, up to four for area codes, at least a couple more for some =
strange special combinations, and changing all the time. I'd assign no =
less than 20 chars.
=20
As in Derek's Australia, dates are always day/month/year (again, =
British influence). Watch out: Japan uses year/month/day! The hour is =
always based on the 24-hour clock. Coloquially, you will hear 'diez de =
la ma=F1ana' for 10 a.m., or 'nueve de la noche' for 9 p.m., but never =
in writing, never on a document -it's not just custom, it's the law.
=20
Quite a chore, I know. Not even stable, since such conventions change =
all the time. I'd try for a manually editable config file (for =
experienced users), or a simple interface to same, much like the =
'International' applet in Windows. Or don't American versions carry it?
=20
Gerardo
=20
=20
----- Original Message -----=20
From: gwalters at sc.rr.com=20
To: EUforum=20
Sent: Thursday, July 26, 2001 6:34 PM
Subject: Re: field size
Well Derick, it's beer time here in USA, SC (5:30pm). I'm about =
burned out at this point...Info is falling out my ears..
=20
..george
----- Original Message -----=20
From: Derek Parnell=20
To: EUforum=20
Sent: Thursday, July 26, 2001 4:51 PM
Subject: Re: field size
When I saw your screen layout, I could see the same old problems =
that people in the USA make. The common thing for programmers =
(regardless of where they come from) is to make assumptions about =
certain data that don't hold up when the data is moved to different =
locales.=20
=20
For example, in Australia, State codes are 3-characters long, and =
ZIP codes (called postcodes here) are 4-chars long, and telephone =
numbers are 8-chars long, dates are written as DAY/MONTH/YEAR sequence, =
etc.....
=20
It might do you some good to ponder if these sort of =
locale-influenced data items need special treatment.
=20
Of course, there's the 'character codeset' problem too, and the =
how much screen space needed for different languages?
=20
Or send an email To: EUforum-unsubscribe at topica.com
This email was sent to: gwalters at sc.rr.com
------=_NextPart_000_0017_01C11676.1E0FF9C0
Content-Type: text/html;
charset="Windows-1252"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=3D"text/html; charset=3Dwindows-1252" =
http-equiv=3DContent-Type>
<META content=3D"MSHTML 5.00.3105.105" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT size=3D2>Well Gerardo, it's coffee time now (Colombian), 6:20 =
am and=20
I'm back on it. Summer here, and we've had a very pleasant cool one so =
far. It's=20
been in the upper 80's mostly... a few days in the lower 90's.... quite =
unusual.=20
A couple of years ago it was 105 for a week....but that is unusual=20
also.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>The date thing could be handled with a date form =
switch, the=20
phone by just a longer free form field and so could the state/province =
field.=20
There are more serious issues of an accounting nature probably with =
payroll and=20
the general ledger. For example our GL has all month's of the year open =
so you=20
can go back and repair mistakes and redo financials, but in Venezuela =
once you=20
close the month it's illegal to go back. (I consulted with a business =
there=20
several years ago).</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>The OS I've been using (Theos... <A=20
href=3D"http://www.theos-software.com">www.theos-software.com</A> ) is=20
international and has some presence in SA but mostly in Europe and Spain =
(<A=20
href=3D"http://www.theos.es">www.theos.es</A>) in particular. Spain does =
a lot of=20
the development on the windows side. Theos has a client program that =
connects to=20
a Theos server (tcp/ip connection written by AST in Spain), something =
like a=20
smart terminal emulator. We can then have PC's for workstations and our =
software=20
is point and click (on colored words) although it is not GUI. The basic =
problem=20
that I and a lot of other dealers have is we can only take advantage of =
products=20
in the theos environment, which is not a lot. Like myself, the dealers =
have a=20
huge development effort to change since the basic they have is so =
complete and=20
nothing similar or even close is available elsewhere.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>So far I like EU, but it has some limitations that I =
would=20
like to see improved. My (and Lucy's) programming style heavily =
uses =20
select/case/cend...and EU being so structured i'm supprised that it =
doesen't have it.</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2> select some.var</FONT></DIV>
<DIV><FONT size=3D2> case =
'a"</FONT></DIV>
<DIV><FONT size=3D2> =
do=20
something</FONT></DIV>
<DIV><FONT size=3D2> case =
'b'</FONT></DIV>
<DIV><FONT size=3D2> =
do=20
something</FONT></DIV>
<DIV><FONT size=3D2> case =
'c'</FONT></DIV>
<DIV><FONT size=3D2> =
do=20
something</FONT></DIV>
<DIV><FONT size=3D2> =
otherwise</FONT></DIV>
<DIV><FONT size=3D2> =
catch=20
all here</FONT></DIV>
<DIV><FONT size=3D2> cend .....or ala EU end =
select</FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>I would also like to see variable names use =
periods...like=20
'customer.name', 'customer.address' instead of customer_address. Not a =
big issue=20
with this one just personal preference. And the 'goto label' issue... =
I'll have=20
to sit this one out. It's the biggest road block in porting to EU to get =
something as a starting point to continue with and make complete redo's =
a piece=20
at a time. And lastly as Irv points out a multiuser capability with a =
data base=20
with record and file locking. I'm hoping that some of the contributions =
of=20
others will solve this. I see that a 2.3 is on the way. I wonder what =
new things=20
it will contain. </FONT></DIV>
<DIV> </DIV>
<DIV><FONT size=3D2>..george</FONT></DIV>
<DIV> </DIV>
<DIV> </DIV>
<DIV> </DIV>
<BLOCKQUOTE=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; MARGIN-RIGHT: =
0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:gebrandariz at YAHOO.COM" =
title=3Dgebrandariz at YAHOO.COM>Gerardo</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:EUforum at topica.com"=20
title=3DEUforum at topica.com>EUforum</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Friday, July 27, 2001 =
1:04 AM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: field size</DIV>
<A =
coffee alone.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Here we have one-letter provincial =
codes, but=20
they aren't quite well known, so most apps will offer you the more =
familiar=20
(read traditional, and longer) abbreviations, as in 'Bs.As.' for =
Buenos Aires,=20
'Cba.' for C=F3rdoba, and so on. Like the oldtime Mass. and Fla. and =
Ore. in the=20
USA.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>The c=F3digos postales have recently =
changed from 4=20
to 8 chars (one letter, four numbers, three letters -looks quite=20
British).</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Standard telephone numbers are eight =
chars long.=20
Add two chars for cellphones, up to four for area codes, at least a =
couple=20
more for some strange special combinations, and changing all the time. =
I'd assign no less than 20 chars.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>As in Derek's Australia, dates are =
always=20
day/month/year (again, British influence). Watch out: Japan uses=20
year/month/day! </FONT><FONT face=3DArial size=3D2>The hour is always =
based on the=20
24-hour clock. Coloquially, you will hear 'diez de la ma=F1ana' for 10 =
a.m., or=20
'nueve de la noche' for 9 p.m., but never in writing, never on a =
document=20
-it's not just custom, it's the law.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Quite a chore, I know. Not even =
stable, since=20
such conventions change all the time. I'd try for a manually editable =
config=20
file (for experienced users), or a simple interface to same, much like =
the=20
'International' applet in Windows. Or don't American versions carry=20
it?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Gerardo</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- </DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:gwalters at sc.rr.com"=20
title=3Dgwalters at sc.rr.com>gwalters at sc.rr.com</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A =
href=3D"mailto:EUforum at topica.com"=20
title=3DEUforum at topica.com>EUforum</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, July 26, 2001 =
6:34=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: field size</DIV>
<DIV><BR></DIV>
<DIV><FONT size=3D2>Well Derick, it's beer time here in USA, SC =
(5:30pm). I'm=20
about burned out at this point...Info is falling out my =
ears..</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT size=3D2>..george</FONT></DIV>
<BLOCKQUOTE dir=3Dltr=20
style=3D"BORDER-LEFT: #000000 2px solid; MARGIN-LEFT: 5px; =
MARGIN-RIGHT: 0px; PADDING-LEFT: 5px; PADDING-RIGHT: 0px">
<DIV style=3D"FONT: 10pt arial">----- Original Message ----- =
</DIV>
<DIV=20
style=3D"BACKGROUND: #e4e4e4; FONT: 10pt arial; font-color: =
black"><B>From:</B>=20
<A href=3D"mailto:ddparnell at bigpond.com" =
title=3Dddparnell at bigpond.com>Derek=20
Parnell</A> </DIV>
<DIV style=3D"FONT: 10pt arial"><B>To:</B> <A=20
href=3D"mailto:EUforum at topica.com" =
title=3DEUforum at topica.com>EUforum</A>=20
</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Sent:</B> Thursday, July 26, =
2001 4:51=20
PM</DIV>
<DIV style=3D"FONT: 10pt arial"><B>Subject:</B> Re: field =
size</DIV><FONT=20
face=3DArial size=3D2>When I saw your screen layout, I could =
see the same=20
old problems that people in the USA make. The common thing for =
programmers=20
(regardless of where they come from) is to make assumptions about =
certain=20
data that don't hold up when the data is moved to different=20
locales.</FONT>=20
<DIV></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>For example, in Australia, State =
codes are=20
3-characters long, and ZIP codes (called postcodes here) are =
4-chars long,=20
and telephone numbers are 8-chars long, dates are written as=20
DAY/MONTH/YEAR sequence, etc.....</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>It might do you some good to =
ponder if these=20
sort of locale-influenced data items need special =
treatment.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Of course, there's the 'character =
codeset'=20
problem too, and the how much screen space needed for different=20
languages?</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT><A FONT entered)< be to =
2chars allow=20
only would i state the><FONT=20
=
size=3D2></FONT> </DIV></A></BLOCKQUOTE></BLOCKQUOTE><PRE>=3D=3D=3D=3D=
<A =
href=3D"http://topica.com/u/?b1dd66.${encoded_sub_id}">http://topica.com/=
u/?b1dd66.b2IexA</A>
Or send an email To: EUforum-unsubscribe at topica.com
This email was sent to: gwalters at sc.rr.com
<A =
------=_NextPart_000_0017_01C11676.1E0FF9C0--
13. Re: field size
Euphoria uses a single statement for single conditional and multiple =
conditionals:
if some_var =3D 'a' then
elsif some_var =3D 'b' then
elsif some_var =3D 'c' then
else
end if
Assuming this is a menu, and I want multiple choices to call the same =
routine, I can use the find() function if 'menu' is an atom:
if menu=3D'a' then
elsif find(menu,"QqXx9") > 0 then
close_program()
abort(0)
else
end if
As for goto, there are several pros and cons which have been discussed at =
length on this forum. Goto can be programmed around by using subroutines =
and routine_id(), which doesn't always make the cleanest solution. Yet, =
if your Basic program were written properly, goto would only be used in =
if/elsif, while, or routine() situation (Disclaimer: this is my own =
opinion as a BBx programmer, and does not reflect the opinions of most =
others on this list).
HTH,
Michael J. Sabal
>>> gwalters at sc.rr.com 07/27/01 08:28AM >>>
So far I like EU, but it has some limitations that I would like to see =
improved. My (and Lucy's) programming style heavily uses select/case/cend.=
..and EU being so structured i'm supprised that it doesen't have it.
select some.var
case 'a"
do something
case 'b'
do something
case 'c'
do something
otherwise
catch all here
cend .....or ala EU end select
14. Re: field size
- Posted by irvm at ellijay.com
Jul 27, 2001
On Friday 27 July 2001 08:28, gwalters at sc.rr.com wrote:
> So far I like EU, but it has some limitations that I would like to see
> improved. My (and Lucy's) programming style heavily uses
> select/case/cend...and EU being so structured i'm supprised that it
> doesen't have it.
>
> select some.var
> case 'a"
> do something
> case 'b'
> do something
> case 'c'
> do something
> otherwise
> catch all here
> cend .....or ala EU end select
That's a minor problem, just causes a bit more typing, since you can
replace the above with
if some_var = 'a' then
do something
elsif some_var = 'b' then
do something
elsif some_var = 'c' then
do something....
else
catchall
end if
Of course, it helps if some_var has a short name:)
As an alternative, since my variables never have short names, I sometimes use:
object case -- declare this once at top of your progm.
case = customer[PREFS][DISCOUNT_LEVEL]
if case = 'a' then
do ...
elsif case = 'b' then
do ....
else
err("Customer has not been assigned a valid discount level!)
end if
> I would also like to see variable names use periods...like 'customer.name',
> 'customer.address' instead of customer_address. Not a big issue with this
> one just personal preference.
Rob has hinted that he is reserving the dot notation for something in the
future.
Putting that aside for the moment, I strongly urge you to not use
individual variables (such as customer_address seems to be)
but instead use Euphoria's nested sequences to store these things:
example:
customer -- a sequence which contains 0 or more records
each record consists of:
name -- a sequence of characters
addr -- a sequence which might contain street, city, state, zip
balances -- a sequence which contains current, pd30, pd60, pd90 values
You can then select customer #2's name:
customer[2][NAME] -- "Joe Smith"
or customer #88's whole address:
customer[88][ADDR] -- {"1234 Fifth St","Bourbon","KY","54321"}
or customer #88's state:
customer[88][ADDR][STATE] -- "KY"
or customer #129's past-due 90 balance:
customer[129][BALANCE][PD90] -- 199.95
or customer #129's balances:
customer[129][BALANCE] -- {12.99, 23.55, 66.98, 199.95}
Because things are neatly packaged, it's easy to add or delete or sort
customers, and to extract groups of customers for reports, etc.
length(customer) returns the number of customers on your list.
Extracting pieces of this data, such a a list of names or zip codes, or a
total past-due, is very simple, just a loop from 1 to length(customer)
There's one hassle, however: the current implementation of Euphoria
makes you declare the meaning of NAME, ADDR, CITY, BALANCE, PD90, etc,
for yourself. These need to be constants declared at the
beginning of your program. Some other programming languages do this
automatically, but for us it requires extra work:
constant -- customer record layout:
NAME = 1,
ADDR = 2,
STREET = 1,
CITY = 2,
STATE = 3,
ZIP = 4,
BALANCE = 3,
CURR = 1,
PD30 = 2,
PD60 = 3,
PD90 = 4
> And the 'goto label' issue... I'll have to
> sit this one out. It's the biggest road block in porting to EU to get
> something as a starting point to continue with and make complete redo's a
> piece at a time. And lastly as Irv points out a multiuser capability with a
> data base with record and file locking. I'm hoping that some of the
> contributions of others will solve this. I see that a 2.3 is on the way. I
> wonder what new things it will contain.
No comment on goto's ;)
File locking is no problem - a very simple thing for a programmer to
implement him or herself. Record locking is a bit more difficult, but
Jonas Temple has a library to do that on the RDS contributions page.
http://www.RapidEuphoria.com/edsnet.zip
Regards,
Irv
15. Re: field size
Gerado writes:
> Hi, George -well past midnight in Buenos Aires, and freezing cold.
> Still, a beer would be welcome -man does not live by coffee alone.
Hi, it's supper time in Ostrava, Czech Republic.
It is sunset and the sky is nice game of various colors from pink
to dark blue, clouds shapes are invoking my imagination,
the weather is just ok - neither cold nor hot...
...and I'm sitting behind my computer...
> Coutry specifics listed...
I won't list my country specifics since nobody
is interested in them.
> Quite a chore, I know. Not even stable, since such conventions change all
the time.
> I'd try for a manually editable config file (for experienced users),
> or a simple interface to same, much like the 'International' applet in
Windows.
> Or don't American versions carry it?
> Gerardo
The Win32 API provides function GetDateFormat for getting
local formatted date. GetLocaleInfo also provide some info
about local's specifics:
LOCALE_ICALENDARTYPE
LOCALE_SDATE
LOCALE_ICURRDIGITS
LOCALE_SDECIMAL
LOCALE_ICURRENCY
etc.
Regards,
Martin Stachon
16. Re: field size
Boy, EU does move around....
..george
----- Original Message -----
From: <martin.stachon at worldonline.cz>
To: "EUforum" <EUforum at topica.com>
Subject: Re: field size
>
>
> Gerado writes:
> > Hi, George -well past midnight in Buenos Aires, and freezing cold.
> > Still, a beer would be welcome -man does not live by coffee alone.
>
> Hi, it's supper time in Ostrava, Czech Republic.
> It is sunset and the sky is nice game of various colors from pink
> to dark blue, clouds shapes are invoking my imagination,
> the weather is just ok - neither cold nor hot...
> ...and I'm sitting behind my computer...
>
> > Coutry specifics listed...
>
> I won't list my country specifics since nobody
> is interested in them.
>
> > Quite a chore, I know. Not even stable, since such conventions change
all
> the time.
> > I'd try for a manually editable config file (for experienced users),
> > or a simple interface to same, much like the 'International' applet in
> Windows.
> > Or don't American versions carry it?
> > Gerardo
>
> The Win32 API provides function GetDateFormat for getting
> local formatted date. GetLocaleInfo also provide some info
> about local's specifics:
>
> LOCALE_ICALENDARTYPE
> LOCALE_SDATE
> LOCALE_ICURRDIGITS
> LOCALE_SDECIMAL
> LOCALE_ICURRENCY
> etc.
>
> Regards,
> Martin Stachon
>
>
>
>
>
17. Re: field size
This is a multi-part message in MIME format.
------=_NextPart_000_0030_01C11706.02C397E0
charset="Windows-1252"
