The whole XML issue is interesting and one of the reasons that I got into Webware.
I used to develop w/ Enhydra - an java servlet type engine that converted an HTML document to an XML DOM object. That was great for well defined problems, but it was becoming tedious to make 'simple' changes. Then I got into Velocity (Java's Cheetah) and moved into 'pure' servlets. Now I hit XML files again - There is an XML file to setup the server and multiple XML entried that have to be made for each page. Its was getting to the point where it actually took me longer to install a new servlet then write the stupid thing. So I do my latest work w/ webware. If I want to add a page I just create the servlet and its all good. Now I need to do a portal page. I'm looking at jetspeed.apache.org and now I get another set of XML files AKA the Portlet markup language. Its everywhere! The preceding comment had no point. My FFK comment is this: I use XML when needed, but the form fields are just a small part of the overall page. So it is logical to allow me to define my fields and validation in the same place as where I write the rest of my page. - In the servlet as a Python structure. Now that I am using Cheetah I have one file open that defines the form and the logic and another file just for presentation. The logic is python and the presentation is HTML. I would not like a system where the logic is partially in python and partially in XML. I think if you are going to go XML, go all the way like Zope Presenatation Templates or Java's XMLC. A forms library should be a quick, easy to use helper system. If you try to make it more then that you are butting into workflow, logic, and presenatation. On the other hand I would love to use ZPT in webware, its great for teams. Thanks, _Aaron Held _______________________________________________ Webware-discuss mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/webware-discuss
