Duncan Gibson wrote: > Now that the FLTK-1.3.x documentation is being restructured to use > doxygen, would it be worth while to introduce two, or possibly three > new chapters or appendices: > > a. Frequently Asked Questions:
+2 ;-) > b1.Build environments: > One paragraph per build environment or IDE outlining what settings > are required for that environment, where libraries should be located, > how to handle dynamic/static linking, etc. +/- 0 I'm concerned that this might be too big and soon be outdated. But if someone would do it, it'd be okay for me. That would be one chapter (doxygen \page) [which you could reach from the main page, sequentially from the new/coming navigation bar, or via explicit links from anywhere) with one \section for each environment or (for more complicated environments ?) even a \subpage (you would have to click on a link from the main Build Environment page). If appropriate, we could also have direct links to subpages on the main page, as in chapters 3,6,9 now (but they refer to sections within a page). > b2.Cross compiling: [could be a part of build environments] > As a minimum, Ian MacArthur's basic guidelines on how to modify the > makefiles, comment out fluid, etc to build for another platform. +/- 0, same as above. > Or are these all subjects that are simply too dynamic for the main > documentation and should therefore only be offered via the web pages > and forums where people can add comments or discuss them in depth? There could be links to the online pages for the more dynamic info, but I don't think that the online info would be better. You can't make updates there, you can only add new (and changed) articles. > Are there other subjects that deserve to be covered in more detail in > the main documentation? (e.g. Resizing; Raw image data handling) +1 for resizing +1 for (raw) image (data) handling Maybe more, don't know. Albrecht _______________________________________________ fltk-dev mailing list [email protected] http://lists.easysw.com/mailman/listinfo/fltk-dev
