Hej Martin!

First, I must say that I appreciate the answers.

>You missed one of the most important things sencha has and thats its licensing 
>model. They want and need go get money out of it so sure they are working hard 
>to get it done. As you know, thats not the case with qooxdoo. So I guess its 
>kind of an unfair comparison in general but we still can go one.

It is true and that is one issue we can not live with. I still think the 
comparison is adequate, regardless of licensing. We prefer to compare with the 
better ones if there are any...

>We do have currently an internal project we are helping out so not everyone 
>usually working on the core is available 100%. That may be one reason that it 
>seems that development speed dropped a bit.

I have full understanding for that. We all have to be a bit commercial too :-) 
But I actually meant in general the last 6 months.

>Our main long term goal is, as it has always been, to be a good framework for 
>the applications we need to build. If none at 1&1 needs a server based GWT 
>version, then  I'm quite sure this will not be added by the core team. But 
>that does not mean it is never added as everyone out there is free to build 
>it. In fact, there is something like that already out in the community which 
>is called QxWT [1].

A modest goal for such an excellent base structure and design of qooxdoo. No 
one, regardless of licensing, in the market beats the design of the framework. 
I am just pointing out functionality differences.

We tried QxWT but it was far from our expectations. There is also a lag between 
the development trunks and little sync.

>The future will tell. I can't tell you more than we have on the Roadmap, which 
>is available on our public website.

Also modest in comparison, but as always resource limited as for any commercial 
company. But the good about it, you keep what you promise!

>At the moment, we plan with the guys we have here. If demand changes within 
>1&1, we sure hire some more people but that all does depend on the company 
>because in the end, they have to pay the developers.

Do you believe that broadening, under your supervision, of the core developers 
by inviting community developers would enhance the functionality of the 
framework. Then you might release time for project lead and quality control and 
participate more in the discussion and the work is done by the community in a 
greater extent than today? Would you see it as leveraging the framework?

>You mentioned "some" but always talked about one, sencha. It's quite obvious 
>to the already mentioned reasons that they do have more to offer than we have 
>but of what other competitors do you speak? Maybe there are some other 
>frameworks we don't have an eye on.

I agree it is biased, but I chose the most new and complete from a 
functionality point of view. The others have parts and not as many parts as 
Sencha. I prefer to compare with the lead.

Stefan                                    
------------------------------------------------------------------------------
EditLive Enterprise is the world's most technically advanced content
authoring tool. Experience the power of Track Changes, Inline Image
Editing and ensure content is compliant with Accessibility Checking.
http://p.sf.net/sfu/ephox-dev2dev
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to