"IMHO it is the best practical way to have a release including a fair
amount of docs and then add even more information, articles and
tutorials afterwards."
That makes sense because then qooxdoo isn't being deprived of potential interest. If the automatic API documentation can be polished and perfected, maybe people can take a spin through the source and clean up and expand on the comments. My experience with Java is that it's documentation provides everything I need, qooxdoo should follow that example.
Of course, a few tutorials and examples just to help with the overall structure will still have to be made. But a *perfect* API resource often covers 90% of peoples' needs.
_________________________________________________
Alexander Trauzzi
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
