help us by reading what we have so far and share your views, criticism, suggestions
Well, I've just downloaded and had a quick look at this document, so here are my very first impressions:
Having in mind those new users for Code::Blocks, IMHO the documentation should begin with a chapter explaining how to obtain the latest version for C::B (stable or nightly, explaining those concepts), how to install it and how to configure a working enviroment with the usual compilers in the usual platforms. Perhaps, this could be introduced in a preface, as a beginner approach.
Currently, this manual directly begins setting up a TriCore project (??) and explaining the PXROS wizards (??), and afaik these components seems to be integrated in a "custom made" C::B. I don't know if it's intended to remove these chapters or adapt them to the standard C::B version, but in any case, i think that the logical sequence would be to begin having a general quick look for the main components and user interface (currently explaind on chapter 3).
Perhaps, the index could be organized in a manner that all the core plugins were covered inside the main document and all the contrib plugins explained into some appendices (beginning on how to obtain, build and configure them inside C::B), but not merged with the core plugins.
Could be defining the contents (i.e. to specify a reference index) the correct way to plan a well structured documentation?
We make available the PDF version for reviewal. The plan is to provide it in more formats (like CHM) later.
I know that this is only a preview, but I think that, for future draftings and compositions, it could be interesting to include the documentation into the svn repository accompaining the source code, in plain text format (or XML, or something editable and standarized), organized hierarchically on chapters/sections/paragraphs and languages, so it could be more easilly completed, corrected, updated or translated into other languages (the same way that does the svn-book itself). A generated PDF (preferably HTML, though) could come with the C::B releases.
In any case, it really nice to see that there is an active initiative for providing an "official" documentation acompaining C::B, so I can only celebrate it and congratulate those involved in his development (e.g. mariocup). It's really a hard work.
Regards.