Hi Hugh! Hugh Gibson wrote: >> We are looking forward for your collaboration and feedback, and really >> hope that are you as excited about the new possibilities as we are. > > Looking good!
Great you like it! :-) > Will you be working through all existing classes adding debug code e.g. to > check parameters and so on? Well, I don't expect to go through all existing classes and add such checks at once. But at least we have some great possibilities here to help during development while it all has no negative impact on deployed applications (in terms of performance/size). Also, qooxdoo's new Java-like interfaces are even planned to be more powerful in some areas than their originals. qooxdoo interfaces allow for not only ensuring that the method signatures a correctly implemented, but also for a fine-grained control of values. That is, a subtract(number) could not only ensure that an integer value for the number argument is given, but for example that it is only within a range of 1 .. 100. This feature should be put into the wiki shortly. > My only problem is that I will have to redefine my auto-comment script in my > editor, which detects function and class header lines and creates a template > api comment for them... ;-) Well, hope you can adjust your handmade qooxdoo editing mode. In general, the new class declaration is tried to be as consistent and concise as possible, so that we all could hope for pretty good qooxdoo IDE-support in the future. > Hopefully you will have finished the basic architecture soon, and can get on > with finalising functionality, APIs and documentation. Pushing on to version > 1.0... Thanks for your good wishes. Regarding a 1.0 release, it is save to say that we are still far away from an 1.0. See the roadmap for the next major milestones. Other JavaScript libraries use to tell people that it is perfectly ok to have almost unusable, inconsistent releases 0.x, because the final 1.0 will be _the_ perfect solution. We seriously doubt that this is a fair or even realistic assumption. Instead, qooxdoo tries to have every release substantially better than the last one. While a qooxdoo 1.0 can be expected to be quite mature and stabilized API-wise, this does not mean that there won't be significant changes afterwards. Extending migration support certainly is a key in not limiting the potential of the framework. > Our application is coming on well, and showing stunning performance over the > web. qooxdoo is proving to be a very good choice for our AJAX solution, > hiding the complexities of rendering in browsers very well. Good to see qooxdoo allowing for so many advanced applications. Cheers, Andreas ------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys-and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
