On 5/17/07, Paul McNett <[EMAIL PROTECTED]> wrote: > Nate Lowrie wrote: > > On 5/17/07, Paul McNett <[EMAIL PROTECTED]> wrote: > >> I'm going to work on removing all references that point to The Dabo > >> Book, but in so reviewing I believe the outline has basically survived > >> with not much need for revision. > >> > >> I'm going to keep the book repository intact, and while the > >> already-written sections will likely be redone, if anyone wants to help > >> polish up the outline for the book that would at least be a start. > >> Having a book to accompany Dabo 1.0 would be a worthy endeavor, but I am > >> presently unable to do it myself. > > > > Having more documentation to accompany v1.0 would be handy... > > > > I took a look at the book and seems like a really good idea. I might > > take the lead on it. If I do, do you have a problem with using LaTeX > > instead of a WYSIWYG like OO? Still open source, but far better for > > typesetting and the book will look and feel professional. The source > > is just text files with markup. > > No problem at all. I started in docbook but it seemed quite tedious, and > kept me from wanting to work on it. Then I switched to OpenOffice, but > didn't like the binary file format, and that kept me from wanting to > work on it. > > I've never used LaTeX but it certainly has a great rep...
LatTeX markup is easy to learn, especially for programmers. It also has GREAT code snippet features including full syntax highlighting. > > >> So, to focus on the outline: > >> http://svn.dabodev.com/dabodoc/trunk/book/outline.txt > > > > I see that you have started mainly on the introduction chapters. I > > will go for a minimalistic complete book and then add additional > > sections. I will focus on sections II and III for now. I see section > > III including multiple projects eventually. Note that the projects I > > will write for section III will not use the CD. If someone wants an > > example using that, someone else will have to write it. > > I see III being the meat of the book. Not using the CD is fine, even > better, at least until we have the IDE polished and the format has > stabilized... > > IV.B may or may not be printed in a final book, since it'll end up > taking hundreds of pages if we print out every PEM for every class in a > repetitious manner. OTOH, it may be handy if the online API docs aren't > available. But some sort of guidemap through Dabo's class library should > be printed. I was thinking about this. An in between solution is to identify to the user all of the permanent properties (dPemMixin props), data properties (dDataControlMixin), etc. and when we identify the GUI class just say it has this and that set of properties. Then, we just need to tell what properties the GUI object has itself (like WordWrap for dEditBox). I will focus on this portion last though. > > You already have subversion commit access to dabodoc; feel free to take > the bull by the horns and run with it. Will do. > > -- > pkm ~ http://paulmcnett.com > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/dabo-dev Searchable Archives: http://leafe.com/archives/search/dabo-dev This message: http://leafe.com/archives/byMID/dabo-dev/[EMAIL PROTECTED]
