panyasan wrote:
Hello,
I think that much of the problems that Tom refers to are related to the fact
that qooxdoo is still a moving target and will be until the 1.0 release.
Yes, but not in terms of its general orientation, I would hope (Tom
writes "I have been asking myself what Qooxdoo is" - "is"!).
I
am thrilled by the fast progress and the changes that are made to the API
are all sound. But if one chooses to stay with the bleeding edge code, it is
not surprising that one finds oneself constantly rewriting parts of one's
own application because of changes and additions in the framework. Don't get
Ok, but I wouldn't recommend going with the bleeding edge when you are
still trying to find your way through qooxdoo and its bits and pieces.
This would be asking for trouble. For such a phase, sticking with a
released version is the right way to go.
me wrong - that is not a complaint! But we'll have to wait until 1.0 for a
fully stabilized API and feature set, and then something like the "Dojo
Book" can be written. I applaud the qooxdoo team for keeping up a detailed
and informative documentation. But in order to give developers a full and
comprehensive introduction into all aspects of the framework, I think that a
real book (online or in print) needs to be written that is a bit more
structured.
Yes, I definitely agree with this, though I hope we will achieve this
with the online manual. A book-like format should be more of an icing :).
T.
Just my 2 euro-cent.
Christian
thron7-2 wrote:
Tom,
In my opinion, Qooxdoo has the potential to be the de facto web
development
environment. However as Qooxdoo has been growing I have been asking
myself
what Qooxdoo is. It used to be simple. Qooxdoo was a framework that
allowed you to create object oriented software in javascript with Qooxdoo
supplied widgets and a bit of server communication.
I wonder what you are thinking of particularly. I think your description
what qooxdoo was still holds. What are the things you see have been
added and have blurred the basic characterization of qooxdoo? The only
entirely new thing I can think of is data binding, which is an addition
and still fits nicely in the existing frame.
Also, Gene wrote he has been following the mailing list closely since
March, and if that was also the time when he started working closer with
qooxdoo and trying various things, then he hasn't seen dramatic changes
in qooxdoo that would make it harder for him to oversee it.
T.
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
------------------------------------------------------------------------------
Come build with us! The BlackBerry(R) Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9 - 12, 2009. Register now!
http://p.sf.net/sfu/devconference
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
