That looks good guys
Just a few design notes on the book itself;
o For each Chapter, start a new page.
o With ALL the code, change the font of it ( I suggest Courier New, 10pt ), and name it. Ie., give it an "example" number, like "Example 3.1" ( where the 3 is the chapter number, and the 1 is the example number ). Also, I'm not too sure if it's possible with PDF documents, but try to place the code examples in a box of some sort, so that it's easily discernable from the rest of the text ( along with the font change ).
o The "+---+" wraps around, Just as a suggestion, instead of trygin to make it span the whole page, just make it short, about half the page width, then centred, It still looks just as good, If not better IMO.
o Again, I am not too sure if it's possible with PDF documents, but try to set up links from the index at the start, so that you just have to click on a chapter heading to jump to it. If that's not possible, set up Bookmarks for the chapters, which IS possible.
o With the code ( again ), Try to
Bold the DBP commands, and
Italicise the remarks. And, if it's possible, at the end of each chapter, give a fully commented working code summary that can be just written straight into DBP and run, and will output some sort of result.
o With the General text, Justify it. So that the right hand side has a hard edge, it looks so much better than simply Left Aligning it.
o Thesub headings you use ( mainly the ones at the start for "Integer" and "String" etc ) aren't very noticable. Put their Point Size up a bit, Bold it and get rid of the underline.
Well, that's all for now...
Hope I wasn't too harsh
If I was, sorry, lol.
Jess.
Team EOD :: Programmer/Logical Engineer/All-Round Nice Guy