[ros-kernel] Re: Proposed books for rosdocs

[Aliberti E. <ea...@io...>]

(I am back after a few days off line. I see the thread is large now. My
original proposal of two books {tutorials & reference} was probably
misinterpreted due to my lack of explanation. Here it is what I actually
meant.)

Behind "tutorials" is the spread unstructured design of the Linux
HOW-TOs. That is the most proactical way of writing documentation,
because it is based on real on-the-field needs. It is also the only one
that can (IMHO) succeed right now in this project. A top down design
failed in the past.

Behind "reference" is simply a database. Database concept is inherent in
the reference idea. If the backend is a database, you can write an
application for online/offline lookup and one for document generation
(XML, LaTeX, PDF...). I can help in writing the schema (SQL92 or MySQL
to be practical).

If (I hope so!) ReactOS succeeds, professional technical book writers
will write BOOKS about every possible subject one will need.

P.S. This is off thread or cross thread: the long term problem with C
header files needs a database approach too. MS has one and an
application that generates the public and the private sets of files.

====================================================
= To remove yourself from this mailing list, go to =
= http://www.reactos.com/home/mailing.html         =
====================================================