RE: Book outline

new topic     » goto parent     » topic index » view thread      » older message » newer message

Hi Mike,

I have started writing a book already and am intending to keep to
the very basics.  ie. someone that has never programmed before
should be able to read it.

I am steering away from third party libraries and am concentrating
on basic logic using only generic commands.

* The first chapter introduces the basic concepts of what is a 
language, what is a program, errors, development process etc 

* Next will be installing Euphoria, edit program, run program,
debug.

* basic variables and their uses (numbers are characters, 
strings are a sequence of numbers etc.  Here i will introduce 
basic input/output to demonstrate variable usage.

* basic program flow: if then, while, etc

* functions / procedures

 ... the rest is on my other computer which I'm not going to turn
on because i'm just off to bed.

I'd also like to "somehow" mention top down and bottom up methodolgies

The book I'm writing is not about "how to program in euphoria" ...
but how to program (and we just happen to be using Euphoria as the
language) ... if that makes sense.

My working title is:

"An Introduction to Computer Programming with Euphoria"

very original hey!

I'm hopig to have the first couple of chapters finished in about a 
week so I can post it and get some feedback.
I expect it's probably about 4-6 month part time project.

I've spent the last couple of days getting Latex working which will
allow me to produce postscript, pdf, and html versions from the
one source.

I've pretty much got the first half of the book organised and haven't
thought much past that.

anyway I better get off to bed before the sun comes up

Ray Smith



Sabal.Mike at notations.com wrote:



> Based on my experience learning and teaching programming, I propose the
> following outline for the introduction to Euphoria programming book
> whatever form it may take (print, HTML, PDF, etc.).
> 
> i. Foreward & Credits
> I. Introduction & installation
> II. Hello, Hello, Hello
>    A. puts
>    B. for loops
>    C. explanation of literal strings and variables (as used in puts and
> for)
>    D. Exercises
> III. Numbers up
>    A. constants
>    B. atoms
>    C. simple expressions
>    D. print and printf
>    E. using sprintf with & (concat) and puts
>    F. printing to a file (open / close)
>    G. Exercises
> IV. Need input....
>    A. sequences and includes
>    B. gets with puts and & (concat)
>    C. while, getc, and wait_key
>    D. object types and get
>    E. Exercises
> V. Ifs, ands, and ors
>    A. simple if
>    B. building cases with elsif
>    C. A simple menu using getc, if/elsif, and find
>    D. The guess-a-number game
>    E. Exercises
> VI. Getting fancy
>    A. Functions & procedures
>    B. Using text_color and position
>    C. Making sounds (mention sfx2.e & other DOS/Linux sound libraries)
>    D. File commands (chdir, rename, etc.)
>    E. A more complex (i.e., colorized / formatted) menu
>    F. Exercises
> Unit review: Text-based battleship game (expanding on sequences and
> indexing).
> VII. Paint me a smile (graphics.e for DOS, euengine for Linux)
>    A. Using the mouse (mention gpm for Linux)
>    B. Graphics modes and metrics
>    C. Designing a font and using the existing DOS font libraries
>    D. A simple paint program
>    E. Exercises
> VIII. A spritely step
>    A. Differences between BMP, GIF, and JPEG files
>    B. Saving and loading bitmaps (mention libraries for other file
> types)
>    C. Displaying and moving bitmaps
>    D. The concept of double-buffering
>    E. Resizing techniques (based on the recent mailing list thread)
>    F. Exercises
> IX. Other DOS-based graphics libraries
> [I'm not an expert on these, so you all will have to fill in this
> chapter]
> Unit review: A shoot-the-aliens type game
> X. Winding your way into Windows
>    A. Win32Lib (mention other libs, but this book will use Win32Lib)
>    B. Creating windows
>    C. Creating menus & menuitems
>    D. Creating pushbuttons
>    E. event handlers: onClick, onMenu -- introducing routine_id
>    F. Exercises
> XI. A little dialog
>    A. Creating sub-windows, explain the difference between Modal and
> Normal windows
>    B. Labels
>    C. EditText
>    D. MleText
>    E. getText and setText
>    F. Dropdownlists and Combo boxes
>    G. onOpen, onClose, and onChange
>    H. setEnable, setVisible
>    I. Exercises
> XII. Ah, input!
>    A. introducing database.e (and associated libraries)
>    B. db_open, db_create
>    C. tables: opening and creating
>    D. Adding, deleting, and updating records & keys
>    E. Switching between tables and finding records
>    F. Exercises
> Unit review: Making a Windows-based address book
> Appendices of terms, other resources, libraries, commands, etc.
> 
> I post this primarily for discussion purposes, but if the ultimate
> author of said book wishes to follow this outline, modified or intact, I
> wish you the best.
> 
> Michael J. Sabal
> 
> 



Ray Smith
http://www.geocities.com/ray_223

new topic     » goto parent     » topic index » view thread      » older message » newer message

Search



Quick Links

User menu

Not signed in.

Misc Menu