On 09/10/2014 07:46 PM, Graeme Geldenhuys wrote: > > * Start documenting the base units like mseactions, mseapplication, > mseevent etc. Then working your way up the class hierarchy. Use fpdoc's > ability to inherit documentation from parent classes so you don't have > to duplicate help contents. >
How do I document somethng like mseactions, mseapplication, mseevent? I don't use them. I would not know what to write as a short / long descripton for the constants, types, classes, etc. I would not know what to write for what individual values in the constants / types mean. So how do I / we go forward from here? Patrick ------------------------------------------------------------------------------ Want excitement? Manually upgrade your production database. When you want reliability, choose Perforce Perforce version control. Predictably reliable. http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk _______________________________________________ mseide-msegui-talk mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mseide-msegui-talk
