Hi, first, I'm happy that a constructive design discussion has started :-)
Christian Foltin (GMX) said: >> And the most important thing for me is communication do that the design >> become more clear and evident. So I shall try to work in this direction >> and create some diagrams when I have time for it. >> > Perhaps, I should start to document the plugins, but I must do this > offline. Any proposals how to achive this? Yes, as part of the javadoc documentation, either as package or overview comment file, or as Miscellaneous Unprocessed File (see [1] and [2]). This way it's near to the source and gets less easily outdated (dream!), you get it on your computer together with the CVS export/update (offline!), and you can easily cross-reference class documentation (standard Class Source Code Files) and overall documentation. Eric PS: [1] also explains how to integrate test and template files (a template file for plugins would be great). [1]<http://java.sun.com/j2se/1.4.2/docs/tooldocs/solaris/javadoc.html#sourcefiles> [2]<http://java.sun.com/j2se/javadoc/writingdoccomments/index.html#sourcefiles> -- Eric de France, d'Allemagne et de Navarre ------------------------------------------------------------------------- Check out the new SourceForge.net Marketplace. It's the best place to buy or sell services for just about anything Open Source. http://ad.doubleclick.net/clk;164216239;13503038;w?http://sf.net/marketplace _______________________________________________ Freemind-developer mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/freemind-developer
