thank you for your feedback. I also agree that there are points on which we can do better (marketing and concentrate on functionality not only technology).

But there is no “one and only way” to do a thing. We do not want to set a standard in the world. Everybody is free to use qooxdoo, if he wants to, but we do not have a problem with people using other frameworks or technologies.

qooxdoo will survive as long as we have the powerful sponsor 1&1. Please keep in mind that this company pays all core developers and our tools. I would say that, apart from YUI, no other framework gets this much support from a company. Please do not only see the little attention qooxdoo that gets to judge our survivability.

Cheers
Jonathan

Documentation in Qooxdoo actually is nearly as good as Closure, but it’s still far from the documentation you would find in projects as Django. In my opinion more entry tutorials are needed to show common tasks, it would be nice to have a step by step tutorial about how to create a database oriented application like the Django tutorial.

I do not agree with Stefan, Django few years ago was less known than Qooxdoo and now just read http://jacobian.org/writing/django-community-2009/.

And yes, I’m Django biased, I have connected Django with Qooxdoo with success and I can see that the entry level for Qooxdoo it too high for the common user. So for me it’s not a matter of marketing it’s a matter of making the entry level step lower. I like to see a tutorial making a database application using Django and Qooxdoo, perhaps using jsQt to create the screens.

The amount an quality of Qooxdoo widgets is impressive, but it still lacks from an official rich text editor and a more sophisticated table grid, perhaps it doesn’t need to be as the Extjs one, but it would be great to have a jqGrid clone.

Actually I feel Qooxdoo is one of the best tools to create RIAs, it just needs to show the world how business tasks could be made, and for me business means database access and authorization.

I like Qooxdoo technically, but I can tell you that most will not choose qooxdoo as it is not and will probably never become a standard. If Qooxdoo is going to survive the market it needs to:
1. spread development on more heads around the world
2. orient the package less technically and more functional
3. look at marketing the package
4. cooperate with partners like IBM etc. antagonists to Google

If you do the above then there may be a chance for qooxdoo will survive on the market and become something it deserves and that is far beyond a “local” German project.

Think big now guys!!!!!!

Guys, thanks for a fantastic package,……but………. it is not enough for the market to accept!!!! You need to do more.

the code I used for “API forwarding” is incorrect. In PHP (4 and5), you cannot call a method directly on a newly instantiated object as you can do in JavaScript — e.g., (new Date).getTime(); — so the forwarding has to be done in two steps:

function method_methodSignature( $method ) {
$s = new ServiceIntrospection( $this )
return $s->method_methodSignature( $method);
}

Sorry for the glitch…