> nevertheless: now my application is coupled to your xml-DTD or schema > :-). and if this changes ...
Schemas can be versiond, backwards compatible, the converter can be versioned. The XML can be designed with extensibility in mind. If it is an actively used schema there can be convertes to upgrade etc... > i think this is one reason for xul, because this is standarized. but > imho it will be real real real hard to map xul to qooxdoo. imho it is > not possible. Realistically we will likely end up borrowing some things from XUL rather than completely map it. > but if you think serverside xml helps, no problem :-) For me it does not matter if the XML is parsed server side or client side. As long as loading it into qooxdoo will not slow down application loading/rendering. My motivation for using XML is to generate UI components based on existing meta information I can draw out of my applications. This way I can auto-generate for example form field definitions including validation rules and only need to implemenet the business logic to save the data once it gets back to the server. Sure I can generate javascript out of the meta information but I think XML provides a much cleaner option. Christoph -- View this message in context: http://www.nabble.com/qooxdoo-PHP-framework-project-t1389226.html#a3787898 Sent from the qooxdoo-devel forum at Nabble.com. ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
