1. Please help...
- Posted by echope_ at excite.com
Jul 11, 2001
I have a few questions that I just would like answered so anyone that
can help, please do.(Im not very learned in Euphoria...)
1,) My first question is very simple actualy and I just wanted to know
if there was a command that made anything that the user type upper-case,
so as in a wait_key() statement or such that you wouldn't have to
specify that whatever they type could be read in lowercase or caps-lock
such as:
keypress = wait_key()
if keypress = 'a' or keypress = 'A' then...
--Also if waiting for a word its annoying to do this,
if word = "word" or word = "Word" or word = "WORD" then...
--this is also very annoying|
2,) My second question is if there is another tutorial for plain
euphoria proggraming that goes over more consepts and stuff than David
Gays... begginers tutorial, not to easy but not to complicated or
advanced. I realy like this language but at this point it seems like it
would be so much easier for me to have a second tutorial picking up
where David's left off, or at least expanding on areas around there. It
does get annoying to ask every question I have on the message board to
you people :). I'm just checking if theres any way that I can learn more
than I know all in a step by step way, unlike memorizing the help
section or something...
Thankyou very much,
Scott Husen
2. Re: Please help...
On 11 Jul 2001, at 22:39, echope_ at excite.com wrote:
>
> I have a few questions that I just would like answered so anyone that
> can help, please do.(Im not very learned in Euphoria...)
I wasn't born knowing Eu either, it's ok.
> 1,) My first question is very simple actualy and I just wanted to know
> if there was a command that made anything that the user type upper-case,
> so as in a wait_key() statement or such that you wouldn't have to
> specify that whatever they type could be read in lowercase or caps-lock
> such as:
> keypress = wait_key()
> if keypress = 'a' or keypress = 'A' then...
> --Also if waiting for a word its annoying to do this,
> if word = "word" or word = "Word" or word = "WORD" then...
> --this is also very annoying|
Have you looked at upper() in the help files?
keypress = wait_key()
keypress = upper(keypress) -- convert it all to uppercase
if equal(word,"WORD") then whatever end if
> 2,) My second question is if there is another tutorial for plain
> euphoria proggraming that goes over more consepts and stuff than David
> Gays... begginers tutorial, not to easy but not to complicated or
> advanced. I realy like this language but at this point it seems like it
> would be so much easier for me to have a second tutorial picking up
> where David's left off, or at least expanding on areas around there. It
> does get annoying to ask every question I have on the message board to
> you people :). I'm just checking if theres any way that I can learn more
> than I know all in a step by step way, unlike memorizing the help
> section or something...
The best way is to read the entire help file, memo yourself the words you are
most likely to use, and look thru source code that does things you are
interested in. I have found refman.chm to be quite useful too. To find
instances of the keywords in use, do simple word searches for them in your
Eu directory. And experiment, try things. Don't answer "yes" to the question
"Do you want to play Thermonuclear War?", but anything else should be
safe.... except for file manipulation..... ymmv.
Kat
3. Re: Please help...
On Wed, 11 Jul 2001 echope_ at excite.com wrote:
> 2,) My second question is if there is another tutorial for plain
> euphoria proggraming that goes over more consepts and stuff than David
> Gays... begginers tutorial, not to easy but not to complicated or
> advanced. I realy like this language but at this point it seems like it
> would be so much easier for me to have a second tutorial picking up
> where David's left off, or at least expanding on areas around there. It
> does get annoying to ask every question I have on the message board to
> you people :). I'm just checking if theres any way that I can learn more
> than I know all in a step by step way, unlike memorizing the help
> section or something...
I am puzzled by this kind of question, because it seems to me that
Euphoria is probably the easiest of all languages to learn. Of course the
fact that I learned Basic and Action! and C and a smattering of Pascal
first probably helped. I was at first slightly confused by sequences,
because I had never seen sequences before in any previous language.
I have never been able to learn anything except by doing it. For
example I've never been able to learn any programming language except by
making programs in it. Doesn't matter how many books or tutorials or
HTMLs I read if I don't apply it. That's me; I don't know if this is true
of anyone else.
About memorizing. Don't need to memorize anything. Use the F1 key. If
you use something enough times, eventually you remember it.
About win32lib. At first I found that somewhat formidable, probably
because I didn't understand event-oriented programming very well. The
breakthru was when I started fiddling with David Cuny's examples to find
out how they work.
Jerry Story
4. Re: Please help...
- Posted by irvm at ellijay.com
Jul 12, 2001
On Wednesday 11 July 2001 18:39, Scott Husen wrote:
.............
> 2,) My second question is if there is another tutorial for plain
> euphoria proggraming that goes over more consepts and stuff than David
> Gays... begginers tutorial, not to easy but not to complicated or
> advanced. I realy like this language but at this point it seems like it
> would be so much easier for me to have a second tutorial picking up
> where David's left off, or at least expanding on areas around there. It
> does get annoying to ask every question I have on the message board to
> you people :). I'm just checking if theres any way that I can learn more
> than I know all in a step by step way, unlike memorizing the help
> section or something...
This is a fairly frequent request - one that I am beginning to believe is
nearly impossible to fulfill. Looking thru some of the programming books on
my shelf, many of which run to 600 or 800 pages, I find that the best of them
do little more than give a thorough coverage of what commands are available,
and perhaps give examples which combine two or three basic commands to
perform some simple task. The docs that come with Euphoria provide much
the same thing.
I think that, beyond explaining the basic "building blocks" of a language,
tutorials aren't practical. There are just too many ways to combine the basic
building blocks, and there's no way to predict what those
combinations might be. Nor is it possible to come up with an example
project that is at the same time small enough to be clearly understood
by everyone, and complex enough to interest everyone.
That's why this mailing list is valuable. You can ask your question, and
usually someone will have the answer. Most likely that answer will be
helpful to others as well.
Regards,
Irv
5. Re: Please help...
- Posted by euman at bellsouth.net
Jul 12, 2001
include wildcard.e
Euman
euman at bellsouth.net
6. Re: Please help...
- Posted by DanMoyer at PRODIGY.NET
Jul 12, 2001
echope,
1. The best way to turn the users input back to what they typed is to
*save* it first before it's turned into uppercase (in case of a mixture of
lower/upper case in input). So, using Kat's example,
include wildcard.e
keypress = wait_key()
UsersOriginalInput = keypress
UsersInputAsUpperCase = upper(keypress) -- convert it all to uppercase
if equal(UsersInputAsUpperCase ,"SOMETHING") then whatever end if
You should bear in mind, though, that wait_key() returns *one key*, not a
series of keypresses entered by the user, (unless you loop it and combine
the keypresses), and there is a command which *would* return all of the
users input in one variable, "prompt_string", which also lets you specify
what you might like to be asking the user at that point.
2. And when you put either the wait_key or prompt_string, together with
upper(keypress), where you want in your code to process user input, it is
already *only* (and permanently) working in relation to that user input.
Look at the code example: "upper" is *only* acting on "keypress", nothing
else.
Dan Moyer
----- Original Message -----
From: <echope_ at excite.com>
>
> Ahh... Wildcard.e...
> OK, thats pretty much it, but how do I turn thinks back to
> normal after using upper()??? And is there a way to make it permenently
> on for what the USERS type ONLY? Not the in-program text and everything?
>
>