Howdy! Sebastian Werner wrote: > [EMAIL PROTECTED] schrieb: > >>"Alexander Trauzzi" <[EMAIL PROTECTED]> writes: >> >> >>>So, given the big talk around the namespaces release, its clear that my >>>effort should be geared towards 0.6. >>>How does one obtain a copy of qooxdoo 0.6 right now? Is there any way to >>>generate documentation from it? >>> >>>I think a real feather in your hats would be to have some tutorials ready to >>>go as soon as 0.6 is "released to the masses". If I can write some programs >>>using the most stable parts of the API, it would get me familiar with your >>>script's lifecycle & runtime behaviours...Something that can only be learned >>>through trial & error. >> >>The current 'namespaces' branch, soon to be 'trunk', is what will become 0.6. >>There is no announced release date for 0.6 yet. My opinion is that it >>shouldn't be released until it has some descent user documentation, so that >>new users have a much smaller learning curve than exists currently. > > > In my opinion we should release it and afterwards update the > documentation. This would mean an earlier release date and a higher > pressure to get the documentation up-to-date :)
No need to worry. ;-) Of course, what Sebastian was trying to say is that qooxdoo 0.6 will come with some initial amount of documentation at the very time of the next release. qooxdoo should be accessible by an average qooxdoo user, right. Keep in mind, though, that the current target audience for qooxdoo is still developers. On the other hand the documentation can not be expected to be complete by the time of a release 0.6. 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. I doubt we will have a full-blown documentation section or inline-comment coverage *before* the actual release. As we need the communities help here as well, some contributions will certainly arrive only after people start working with the release. What will happen is that documentation will be made available at any time it is generated. Certainly nothing is held back before the actual release, and I would like everyone to go through all pieces of information and provide feedback. Even better, since most of it will be put into the wiki-based homepage, everyone can update and correct any information right away. The earlier the better. I like to repeat myself here again by inviting people to transer the old articles (documentation section under http://old.qooxdoo.org) over to the new site http://qooxdoo.org. While it should be quite an easy task, only a few volunteers have ported some contents so far. For the task of generating new or updated documents it is essential to have _all_ existing material moved to the current site. Any help is appreciated! Andreas ------------------------------------------------------------------------- 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 [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
