1. The Tutorial That Would Not Die
- Posted by David Gay <moggie at INTERLOG.COM>
Jan 26, 1999
-
Last edited Jan 27, 1999
Greetings:
I was planning on retiring "A Beginner's Guide To Euphoria" this coming
April. However, the emails I've been getting asking for questions and
assistance, while not a torrent, has prompted me to think a bit regarding
putting an end to writing a tutorial.
While I still plan to close down ABGTE, I think a tutorial should still be
written. It should be written by several computer programmers, not just me.
I feel this is necessary because, quite frankly, it is taking me longer to
learn Windows programming than I prefer. It's totally different from DOS.
Having said this, I would like to write (with other Euphoria programmers) a
brand new tutorial, with a new name. Here's what I would like to see:
1) The tutorial would go along the same lines as ABGTE, but would include an
introduction to Windows programming, and how to do so using Euphoria.
Because there's many ways to do Windows programming in Euphoria (such as
David Cuny's win32 approach and David Bernstein's Visual Euphoria), we
should offer the newbie programmer a choice to take which of each.
2) The tutorial should run on DOS, Windows, and a third OS (Unix?????)
3) A decision should be made on whether to include the source code for the
tutorial or not. My decision not to include source with my two past
tutorials was because I did not want many cooks spoiling the broth...perhaps
that was a wrong decision....maybe not.
4) A name for the tutorial is required (A Beginner's Guide To Euphoria is
already taken :P')
If anyone wishes to form a group to write the tutorial, please let me know
in here or at moggie at interlog.com
Thank you
David Gay
2. Re: The Tutorial That Would Not Die
- Posted by Greg Phillips <i.shoot at REDNECKS.COM>
Jan 26, 1999
-
Last edited Jan 27, 1999
David Gay wrote:
> 3) A decision should be made on whether to include the source code for the
> tutorial or not. My decision not to include source with my two past
> tutorials was because I did not want many cooks spoiling the broth...perhaps
> that was a wrong decision....maybe not.
>
What about simply offering the source to people who want it, but don't actually
include it with the release. That way, people who want to contribute to the
tutorial, or who simply want to see how you did it, can contact you by email,
and recieve it that way.
> 4) A name for the tutorial is required (A Beginner's Guide To Euphoria is
> already taken :P')
>
The Inscrutable Euphoria Revealed?
hehe =)
--
Greg Phillips
i.shoot at rednecks.com
http://euphoria.server101.com
--
Useless fact of the day:
The poison arrow frog has enough poison to kill about 2,200 people
3. Re: The Tutorial That Would Not Die
At 11:06 p.m. 26-01-99 -0500, you wrote:
>1) The tutorial would go along the same lines as ABGTE, but would include an
>introduction to Windows programming, and how to do so using Euphoria.
>Because there's many ways to do Windows programming in Euphoria (such as
>David Cuny's win32 approach and David Bernstein's Visual Euphoria), we
>should offer the newbie programmer a choice to take which of each.
About Windows programming I think it's better to learn the API way first.
It should
start with some concept about OS, multitasking (pre-emptive), and DLL's. Then
how this functionality CAN be used in Euphoria, followed by the basic API
calls
and their Euphoria implementation (RegisterClass, CreateWindow, etc.). Finally
a must is a good and complete Windows programming bibliography (starting with
"Programming Windows (95)" by Charles Petzold).
>2) The tutorial should run on DOS, Windows, and a third OS (Unix?????)
How about a tutorial viewer specific for each platform and a common content
file?
Regards,
Daniel Berstein
daber at pair.com
4. Re: The Tutorial That Would Not Die
> The Inscrutable Euphoria Revealed?
>hehe =)
>
That sounds pretty good.....a shorter variant would be,
"Euphoria...REVEALED!!!" (yes, I shamelessly stole that from an old C primer
book)
David Gay
5. Re: The Tutorial That Would Not Die
>About Windows programming I think it's better to learn the API way first.
>It should
>start with some concept about OS, multitasking (pre-emptive), and DLL's.
Then
>how this functionality CAN be used in Euphoria, followed by the basic API
>calls
>and their Euphoria implementation (RegisterClass, CreateWindow, etc.).
Finally
>a must is a good and complete Windows programming bibliography (starting
with
>"Programming Windows (95)" by Charles Petzold).
>
That works. The API portion of the tutorial should be geared to anyone who
has little or no programming experience. Most likely it would be put near
the end of the chapter and would use examples that clearly and distinctly
show how to do this in a step by step manner...in short, we explain the why
and not just the how.
>How about a tutorial viewer specific for each platform and a common content
>file?
Can you expand a bit more on "common content"?
David Gay
6. Re: The Tutorial That Would Not Die
>>How about a tutorial viewer specific for each platform and a common content
>>file?
>
>
>Can you expand a bit more on "common content"?
The common content file would be for example an enhanced HTM, or other
format we create to hold the actual tutorial. The user will download a
viewer specific to it's OS and the content file. Contents can be then
actualized independent of the viewer and vice-versa. The viewer can also
exploit all the funcionality of the target OS. Thing like Windows
winhelp.exe (the viewer) and the .hlp files (the content files).
Regards,
Daniel Berstein
daber at pair.com
7. Re: The Tutorial That Would Not Die
>The common content file would be for example an enhanced HTM, or other
>format we create to hold the actual tutorial. The user will download a
>viewer specific to it's OS and the content file. Contents can be then
>actualized independent of the viewer and vice-versa. The viewer can also
>exploit all the funcionality of the target OS. Thing like Windows
>winhelp.exe (the viewer) and the .hlp files (the content files).
>
Probably HTML would be the best choice, so it can be viewed by any sort of
tutorial or a browser, regardless of platform. We would need to create an
editor that would make maintaining this large file painless, in case we need
to update it as new features of Euphoria comes in.
David Gay
8. Re: The Tutorial That Would Not Die
Hello,
As a complete novice I am very interested in the proposal to write
a new tutorial for Euphoria, especially as I have ABGTE.
> 1) The tutorial would go along the same lines as ABGTE, but
> would include an introduction to Windows programming ......
>(such as David Cuny's win32 approach and David Bernstein's
> Visual Euphoria), we should offer the newbie
> programmer a choice to take which of each.
I'm afraid I don't know what these (Visual Eu and win32 approach)
are. They sound interesting. Could someone please explain? Or
should that be done in a tutorial? 
From: Alan Tu
>I can start with the assumption that the newbie knows
> about the OS, and that's it.
> Also, I'd like to make sure that the mouse isn't the only way to run the
> tutorial. This makes it impossible for those who can't easily use a
> mouse.
I for one would appreciate this. I keep clicking in the wrong part of
the page, bringing up the bleeping noise.
Also:
The tutorial cannot be run in a window and does not have things
like exercises we could do.
I wish I could run the Euphoria editor side by side with the tutorial
and try out the things I am learning right there and then -- which is
how I learnt HTML and (tried) to learn QBasic.
I am not looking for "Euphoria for Dummies" but I do think a more
hands-on approach might help newbies.
Having said that, the tutorial is very comprehensive and shows the
effort and time put into it. Thanks Mr Gay.
Regards,
Natasha Rudra
9. Re: The Tutorial That Would Not Die
> I'm afraid I don't know what these (Visual Eu and win32 approach)
> are. They sound interesting. Could someone please explain? Or
> should that be done in a tutorial?
Daniel Bernstein suggested we stick with the introduction to API
programming as the core to Windows programming. Win32 is a library
allowing you to easily program in Windows, written by David Cuny. Visual
Euphoria is an alternative yet effective approach to Windows programming,
written by Daniel Bernstein.
> I for one would appreciate this. I keep clicking in the wrong part of
> the page, bringing up the bleeping noise.
>
> The tutorial cannot be run in a window and does not have things
> like exercises we could do.
The tutorial was done in graphics mode 18, which is why it could not be
done in a Windows window. Perhaps a text mode version of the new tutorial,
or a Windows-variant tutorial viewer would address that?
> I wish I could
run the Euphoria editor side by side with the tutorial
> and try out the things I am learning right there and then -- which is
> how I learnt HTML and (tried) to learn QBasic.
The current tutorial did have the ability to view source and run it, but
it did not have an editor. Maybe we can put it in the tutorial.
> Having said that, the tutorial is very comprehensive and shows the
> effort and time put into it. Thanks Mr Gay.
>
You're welcome :)
David Gay
> Regards,
>
> Natasha Rudra
>
10. Re: The Tutorial That Would Not Die
- Posted by C & K L <candk at TICNET.COM>
Jan 28, 1999
-
Last edited Jan 29, 1999
There's a beginning Beginner's section on the "Encyclopedia EUPHORIA"
web site at the following address:
http://euphoric.webjump.com
Looking for additional content.
