Hi, Erik! Erik A. Onnen wrote: > Derrell, > > Thanks for the helpful post, but I think your response echoes the OP's > point that more needs to be done towards documentation. Not only is > the namespace documentation light to non-existent, but the > documentation you site on how to generate the documentation is out of > date.
Full ack, more documentation is needed. :-) There is some limited documentation of the development branch. But since it is a rather fast-moving target, it often is infeasible to provide full documentation along its development. Once the dust settles, there will certainly be more docs (from developers and hopefully users alike). Hard to change, but primary target audience for such a branch is developers rather than users. > I tried following the steps listed at > 'http://qooxdoo.org/documentation/developer/api_documentation' and the > structure of the subversion tree has changed. The better way to do > things from what I can tell is to enter the 'frontend' directory in > the source and perform a 'make docs' (frontend vs. backend isn't even > discussed in the referenced link, nor is the make file). > Unfortunately, after I figured that out from parsing the makefile, > running 'make docs' still didn't help because the docs point us to > 'source/demo/apiviewer/index.html' which does not exist. I found what > I think the viewer should be at '/frontend/api/build/index.html' but > opening that produces a popup window with loads of errors and no > documentation that I can actually view. After all that effort, my > interest in getting the docs working for the namespaces API is all but > gone and sadly I've given up and gone back to cranking dojo widgets. Sorry for your trouble. :-( The new powerful api generation has had worked for quite a long time now, but was announced to be broken for a few days. Too bad you hit exactly this time frame. > <rant-warning/> > <rant> > The lack of API (the examples are great) docs is one of only two > things keeping me from using Qooxdoo straight away. Besides the assumed lack of API docs (they _do_ exist as mentioned above), may I ask what's your second reason? > Sure, it's a > volunteer effort and I understand that but the lack of docs is an huge > barrier to entry for those interested in helping out. If Qooxdoo is > the best toolkit available and nobody but the devs can figure out how > to use it, Qooxdoo will join a long list of projects that were great > but never reached their uptake potential. I truly think Qooxdoo is the > best paradigm for rich ajax development out there right now, but sadly > I can't recommend using it to my customers due to things like the > documentation issues and this dead zone between the 'no new > development' 0.5.x branch and the 'no releases or docs yet' namespaces > branch. > </rant> Yeah, maybe we should think of being in the eye of an hurricane. ;-) Anyway, there has been a continuous development of qooxdoo ever since it started. You may be right: The more ground-breaking the advancements, the longer the rather quiet "zones" between releases. Can't wait for all the impressive features that are within reach. ;-) 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
