Re: The tutorial
>May I suggest an oranizational "dividing line" between type 1 & type 2 (ie:
>Chapter 1 -- "If you already know a programming language (such as Basic or
>Pascal etc) you may wish to skip to Chapter 2 now.").
No offense, but when the RDS documentation is not clear enough for you, you
know too little of programming, and need the first chapter anyway. If the
switching over causes so-much confusing, etc. that the person would benefit
alot of a tutorial, then the person is question knew Basic or Pascal (your
example languages), however, he/she did not know how to program.
Im not saying I did. (hell, I was 14, I think, when I discovered Euphoria)
But even for me, RDS documentation, some questions on the list & some
example programs were enough. Not even being in my native tongue.
I dont want to insult people here. But many hobbist and also professional
programmers, are trained in a certain language, rather than in programming
itself.
>Also, as to overall design of the tutorial. I am personally fond of a
"build
>a project" approach, where each chapter explores new concepts & features of
>the language and applies them to a master project such as a simple database
>or editor. Not knowing a whole lot of Euphoria I do not know if this would
>be good in this case.
I like the big project idea, however, if you do not fully understand any of
the parts, your complete project fails. We should also try not to shape the
structure of the tutorial to the project. However, Many routines and
techniques that you create during the tutorial, can all come together at the
end of the tutorial into one big project. That would work.
Ralf Nieuwenhuijsen
nieuwen at xs4all.nl
|
Not Categorized, Please Help
|
|
