Hi, (Sorry it's been so long, been away doing server side coding). I agree with what most peopl have said, but wanted to comment on something possibly unique. When I find a bug or quirk in the framework, or I want to know how something works internally so I can tweak it, I just look at the source code. There has been many times when I've been going through other frameworks and have been shocked at some of the source code. Several TODO comments, comments saying that this line of code won't work under a certain condition, really bad programming habbits, seriously obvios bugs etc... And quite often in comercial frameworks!!
Whilst browsing the qooxdoo source code, I have to be honest and say that there has been a few times I haven't seen what I like, but then that is expected, I'm a picky perfectionist (Well try to be)! But a lot of the time I am impressed. I have actually said "awesome" out load a few times when I've realised something ;) Out of all of the frameworks I have source code for qooxdoo is deffinately the best to follow, it seems well written, thought out, complete, maintained well and it is easy to read. This has helped us greatly! There are a few things that we've tweaked in qooxdoo, knowing what we want it's been so easy to go through the source code, follow a locially chain, find the right class and then create a patch to do the job. Keep it up! Matt P.S. The same actually applies for the toolchain. I've found a few generator bugs in the past but have usually been able to look at the scripts and fix it within minutes, and I've never even written a python script! Signs of a deffinately well thought out framework! Andreas Ecker wrote: > Hi all, > > while approaching the qooxdoo 1.0 release due next week, we'd like to > gather some feedback from you about the strong points of qooxdoo. > > This is valuable input (targeting about/feature pages, announcements) > for other users, particularly new users, to get to know about the most > important aspects of qooxdoo. > > It is important that you don't really think about what _could_ be > relevant for others, but what were and are the most relevant aspects > _for you_ and your project specifically. Your individual "user's view" > if you will. This certainly includes technical aspects, of course, but > also non-technical ones like project and/or community. > > Looking forward to your favorite "pros", > > Andreas > ------------------------------------------------------------------------------ Return on Information: Google Enterprise Search pays you back Get the facts. http://p.sf.net/sfu/google-dev2dev _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
