Hallo, Although I've been programming many years it has all been "desk top" type application work. The Qooxdoo design approach, IMHO, seems to go a whole long way to shelter a client-side newbie from CSS, HTML, and such overwhelming (volume wise) issues as Browser discrepancies. Qooxdoo, does this in some ways that takes a client-side beginner awhile to appreciate and understand. One thing qooxdoo cannot hide from uso, in fact, must do the rather the opposite of is shelter us from some pretty serious OO and the nitty gritty commas and semicolon ridden details of doing things in JavaScript. (Otherwise this package might be too easy to use, I guess. :)
Well, the manual, I will guess just assumes a pretty good understanding of JS - which is fine - but for those of us without this it can be pretty confusing to try to figure out what is going on. After evaluating Qooxdoo I really "bookmarked" this approach but went off to study more packages while continuing with our back-end work. Up recently came the Cappaccino package. And I rather got excited about this until I released how "foreign" Objective J (and confusing to me) compared to "good old" JavaScript which has, all said and done, a lot of similarities to Java and Ruby and so on. So I came back last week to take a good "second look" and I was lucky enough to find this 2year old slide show: http://www.slideshare.net/fjakobs/rap-course-at-the-university-of-szeged-lecture-8-qooxdoo-1194880 Which included some really simple but meaningful to me examples of class inheritance and all. I started USING it in some tests (yes you can have multiple classes in a file) and built up some really stupid examples based on buttons, events, but using real JavaScript Objects and statics to try things - and all of a sudden a lot of things that looked confusing in the examples is now like "wow - I can do this THAT way - and I can't wait to going on this project again.) So, I just hope that might help somebody get started. I'd even go so far as to suggest that some of the Demos / might go out of their way to use Mixins, Interfaces, Inheritance and other features of the language in a couple of incrementally more complex examples. Or I could re-contribute the originally Qooxdoo examples back into the demo system? Sincerely, George K. SwarmShepherd -- View this message in context: http://qooxdoo.678.n2.nabble.com/Note-to-Newbies-especially-without-good-Javascript-background-tp6090591p6090591.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ What You Don't Know About Data Connectivity CAN Hurt You This paper provides an overview of data connectivity, details its effect on application quality, and explores various alternative solutions. http://p.sf.net/sfu/progress-d2d _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
