Hey,
> OK, I would like to see anyone else backing up you in that decision, because 
> until now its been many in favor of modelPath and just you in favor of 
> keeping that out.
Well, I know it sounds hard but in the end, I am responsible for the framework 
so my decision should be enough. I don't want to be the dictator here which is 
why I joined the discussion and wrote down my arguments why I would change that.

> I've developed apps in html(plain), extjs, qooxdoo, apf, sproutcore. And 
> qooxdoo is the only one that doesn't support what I'm asking here. 
Come on, we are talking about an additional / alternative API, not about any 
features missing. You are able to do what you desire no matter if we add that 
or not!

> And if you look what qooxdoo has to offer(playground, mobile, demobrowser, 
> widget set, stability, architecture) it is a lot more than others offer right 
> now, but even so it attracts less developers than other frameworks do. Why is 
> that?
> 
> IMHO, that's because qooxdoo is harder to use, and slower to develop 
> something with. 
I don't want to start some debates about common use of qooxdoo here but sure, 
its harder to lear and thats one of the reasons I don't want to make the API 
even more complex.

> That's just my opinion, but I thought I should write something here because 
> others developers can be switching to other frameworks because of those 
> things too and in the end I really want qooxdoo to succeed.
As we all do here. But I'm not worried about people leaving qooxdoo because of 
that. I am more concerned about people not even giving qooxdoo a try because 
the API is way too complicated.

Regards,
Martin
------------------------------------------------------------------------------
BlackBerry® DevCon Americas, Oct. 18-20, San Francisco, CA
Learn about the latest advances in developing for the 
BlackBerry® mobile platform with sessions, labs & more.
See new tools and technologies. Register for BlackBerry® DevCon today!
http://p.sf.net/sfu/rim-devcon-copy1 
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to