Hi Burak! >> i tried qxtransformer some time ago. it's quite buggy, it did not >> look >> like a finished product. it's implemented using xsl/xslt, so its >> "code" >> looks horrendous. it'd be fine if it just worked but as it is now i >> wouldn't get near it. >> >> >> That seems a bit unfair. Having tried something "some time ago" and >> found it buggy is not necessarily indicative of current state. >> Christian and his gang have been very actively working on >> qxtransformer, as is seen from the frequent commits. I don't use it, >> but I highly suspect that it's currently in much better condition then >> this message would indicate. And if not, I'm quite sure that Christian >> would appreciate any bugs you do find being reported to him. >> > > I looked at my notes, and it turns out that "some time ago", it was > August 3rd. svn log shows the revision at that time was 130, committed > months before. Looking at the state of the project, I thought it was > abandoned and never looked at it again. it's quite unlucky because > commit 131 was the next day :-( I'm sorry if I hurt anybody's feelings.
I also think it's more than fair to apologize for your original statements, as they simply are not appropriate. In fact Siarhei and Christian are long-time contributors to qooxdoo, and qxtransformer is a fine addition to the qooxdoo ecosystem. AFAIK they keep developing most of qxtransformer in their spare time, so not everything may be polished, but they have already been using it for various real-life applications. So at least for them it's ready for production use, and it's great they keep sharing and refining their code and vision with the community. > But i still think that: > 1. defining a new set of xml tags is too much work. > 2. xsl/xslt is a maintenance nightmare. The technical arguments here are rather vague, I think the whole subject is rather a matter of taste. It keeps being a recurring discussion, whether a programmatic or a declarative way of setting up the UI is favorable. IMHO there just isn't much point in this kind of general discussion. Both ways have their advantages and disadvantages. It's not about "one way or the other", it's about "both". And that's exactly what is offered here - as open source, ready for collaboration. Great to be able to choose from such alternatives, picking the one that best fits your needs and thinking. Some prefer Java, fine, just use QWT or RAP. Others Delphi, no problem, use Delphi4PHP. And so on. At the end, it's more or less a qooxdoo application. Well, this one really matters. ;-) Bye, Andreas ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
