John Spackman wrote: > Documentation: usually the Achilles’ heel of OS products, this has > been great since I started (0.7.x) > > >
hi, i agree that documentation for individual features/modules is great, and the example code is abundant. but i think the qooxdoo documentation lacks real-life case studies, a la "samba by example" there are lots of modules and features, but when will i really need them? which application sizes? when will it pay off to invest time? places where this way of doing things should not be used, because it won't scale, so you should use that module instead. (manual verification vs. form handling, when to use fsm, when to use the message bus, etc) it would be great addition to those of us who are new, not only to qooxdoo, but also to gui development in general. just my two kurus. best, burak ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
