Wishlist for qooxdoo (by whomsoever, in no particular order, with no particular preference, and with no implied commit status):
* add 2 new standard themes * re-design the web site * finalize move of the web site to new hardware (we're still using the old one as well) * improve the manual * re-write the manual * write a book about qooxdoo * write more tutorials * hold more tutorials (we came just back from Bucharest doing that) * replace the mailing list with something better * replace bugzilla with something better * replace the wiki with something better * write more blog posts * answer more blog posts * write more tweets * write more answers on the mailing list * write less(!) answers on the mailing list * provide IDE support for qooxdoo * provide an interface builder for qooxdoo * provide a GUI for the generator * re-write the generator * make the generator faster * make the generator use multi-core * improve the framework API * keep the framework API stable * write more unit tests * publish test results * test test coverage (no typo!) * move the test infrastructure to a dedicated host * fix bugs for the next release * implement features for the next release * advertise qooxdoo to inhouse projects * teach qooxdoo to inhouse projects * support inhouse projects * add virtual widgets * add lightweight widgets * write the next killer demo * implement the next killer JS feature * ... These are only the first things that come to my mind. Shall I continue?! T. On 09/10/2010 11:01 AM, Tom Schindl wrote: > Hi, > > I've often tried that but when I point people to the show case the > biggest problem is that if you compare the L&F with the one from the > competitors (ext, smartclient, ...) qooxdoo can't compete - we can argue > a long way that the code quality and the design of qooxdoo is better but > you'll won't get people to buy into qooxdoo with giving them a default > state of the art visual design. > > What qooxdoo needs are 2 new designs: > * a very flashy one (the one from Norbert is going into the right > direction) > * one a bit more conservative one than the above to catch up with > competitors > > Tom > > Am 10.09.10 10:46, schrieb Daniel Wagner: >> Here's one thing that could help a lot: If you come across an >> interesting blog post or discussion where other frameworks are >> mentioned, leave a comment suggesting people check out qooxdoo. Just >> don't be too "evangelical" about it, let people discover qooxdoo's >> strengths on their own. >> >> >> Regards, >> Daniel >> >> Jean-Baptiste BRIAUD -- Novlog schrieb: >>> Hi Stefan, >>> >>> I would not be able to summarize as well as you did. >>> This is the 100% exact copy of what I think :-) >>> >>> Thanks. >>> >>> Now, why not consider the second stage : what can we do all as a community ? >>> Any idea ? >>> >>> On 10 sept. 2010, at 09:38, Stefan Andersson wrote: >>> >>>> Hej! >>>> >>>> I agree on your interest and I can assure that qooxdoo is the best for >>>> many settings. Maybe not satisfies all tastes, but I have not found >>>> anything more complete out there. I am sure that the core team will be >>>> adding functionality as browsers change. You have to be aware of it is >>>> a slow process to upgrade all browsers out there and therefore the >>>> work with new implementations must have some degree of backward >>>> compatibility. >>>> >>>> Fortunately, qooxdoo is definitively one of the, if not the most, >>>> advanced javascript framework in the market. The design is really good >>>> and in some parts based on excellent new ideas. Javascript is not an >>>> easy language to build a framework on! Lots of tricks to get it >>>> going...mostly due to a rain forest of wild browsers living their own >>>> lives. >>>> >>>> Unfortunately, qooxdoo is more or less a garage project from a >>>> marketing perspective. Very few know of it in the world. The website >>>> is in its functionality average, but its design is already old. Almost >>>> no money and too little time is spent on marketing of this fantastic >>>> tool. Until that will be done, it will still be in the garage >>>> division. Unfortunately development goes fast and the competitors >>>> don't wait. Especially not the commercial alternatives. One scenario >>>> could be an alliance with one of the big market players. We have not >>>> seen this happen so far. If nothing drastic happens, it will still be >>>> a small alternative, but maybe still technically the best. >>>> >>>> Even though this insecurity due to the market and fame, we chose >>>> qooxdoo because the code has been fairly well documented, the >>>> structure is robust and it is technically the best. It still has a lot >>>> of things to improve, but already now it is the best. We have >>>> developed about 1,200,000 lines of "qooxdoo" code and converted a >>>> system which soon will "fly"... We are satisfied about it. The support >>>> is fast and mostly accurate. The core team is mostly very skilled in >>>> its answers. But we would never choose qooxdoo for such a big project >>>> without knowing we have our own resources if qooxdoo dies or if the >>>> qooxdoo team disappears in some or the other way. Too big investment >>>> and too big risk, if we wouldn't have the resources by ourselves. >>>> >>>> I hope the above clarifies one of many views from the community. >>>> >>>> Stefan >>>> ------------------------------------------------------------------------------ >>>> Automate Storage Tiering Simply >>>> Optimize IT performance and efficiency through flexible, powerful, >>>> automated storage tiering capabilities. View this brief to learn how >>>> you can reduce costs and improve performance. >>>> http://p.sf.net/sfu/dell-sfdev2dev_______________________________________________ >>>> qooxdoo-devel mailing list >>>> [email protected] >>>> <mailto:[email protected]> >>>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >>> >>> >>> ------------------------------------------------------------------------ >>> >>> ------------------------------------------------------------------------------ >>> Automate Storage Tiering Simply >>> Optimize IT performance and efficiency through flexible, powerful, >>> automated storage tiering capabilities. View this brief to learn how >>> you can reduce costs and improve performance. >>> http://p.sf.net/sfu/dell-sfdev2dev >>> >>> >>> ------------------------------------------------------------------------ >>> >>> _______________________________________________ >>> qooxdoo-devel mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel >> >> ------------------------------------------------------------------------------ >> Automate Storage Tiering Simply >> Optimize IT performance and efficiency through flexible, powerful, >> automated storage tiering capabilities. View this brief to learn how >> you can reduce costs and improve performance. >> http://p.sf.net/sfu/dell-sfdev2dev >> _______________________________________________ >> qooxdoo-devel mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ------------------------------------------------------------------------------ Automate Storage Tiering Simply Optimize IT performance and efficiency through flexible, powerful, automated storage tiering capabilities. View this brief to learn how you can reduce costs and improve performance. http://p.sf.net/sfu/dell-sfdev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
