Would be nice in an open source project to have means to the documentation to be developed in community.
I'm freak sure that lot of people knows a lot of examples and cases of use that could help a lot, a lot of people. A lot sure, hihi. The problem is always how to organize that, and in that, i strongly suggest some kind of database. Documentation direct in the code is always hard to format and hard to keep a sense of unity and integrity. And on a open source project must be some means of multiple contribution, some times even multiple ways of views of the same matter. Another challenge lays on that, how to keep multiple views of the same matter. After all, what helps one, sometimes doesn't helps other. Well, this are ideas about documentation. Em 10/02/2012, às 09:32, Hans-Peter Diettrich escreveu: > Again I found almost all of my notes removed from the LCL documentation. If > this is how my work is honored, I see no reason why I should spend any more > time with contributing to the Lazarus documentation :-( > > When somebody is not happy with notes about wrong or missing documentation in > the final docs, a feature (tag?) should be added to FPDoc, allowing for > editor notes and to show or hide these in the final docs. > > DoDi > > > -- > _______________________________________________ > Lazarus mailing list > Lazarus@lists.lazarus.freepascal.org > http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus -- _______________________________________________ Lazarus mailing list Lazarus@lists.lazarus.freepascal.org http://lists.lazarus.freepascal.org/mailman/listinfo/lazarus
