thron7-2 wrote:
>
>
>> 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 :).
>
The online manual is, as I said, an extremely useful resource. All I am
saying is that a more book-like-structuring (Introduction, Chapters,
Sub-Sections, Index etc.) would, just visually, help easing the learning
curve. For example, a Table of Contents of the whole manual should always be
available. I think the "Book of Dojo" is a good example:
http://www.dojotoolkit.org/book/dojo-book-1-0
It is also visually very pleasing. As I said, don't understand this as
nagging, just suggestions, since currently I am not contributing myself to
change the situation. What I would find cool is if the manual would be a
qooxdoo application itself, just like the API viewer....
C.
--
View this message in context:
http://n2.nabble.com/qooxdoo-IDE-Request-for-Comments-tp3782909p3809220.html
Sent from the qooxdoo mailing list archive at Nabble.com.
------------------------------------------------------------------------------
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
