> I have been playing around with XML/DVSL :-) I will probably add a view > system that uses DVSL instead of XSL. You can find information on DVSL > here:
Ohh interesting. I have not really descovered DVSL until now. I am really not sure if that is a direction I want to go in however. The thing I like about using XML and XSL is the further seperation between logic and layout. Even with pure Velocity/html files you end up with some non display logic sitting in your templates... (I am using pull model by the way). The thing I like about using XML and XSL is that you end up with xml describing the content. Then the XSL file is used for JUST layout of the content. The advantage I in this is that I can modify the back end however I want. My customer can modify the front end how ever he wants. As long as the xml remains consistant neither of us has to worry much about what the other does. My logic in this might be flawed so please feel free to tell me wrong :) > This is all in Turbine 3. I will attempt to make Velocity, JSP and DVSL all > work with the classic model in t3: layouts, navigations and screens. However, xsl is a bit limiting. (and rather verbose.) I would be interested in learning more about DVSL. I would actually rather like to play with t3 some... However, it seems that right now, the torque stuff is commented out of the build.xml file in the TDK for t3. (and some parts seem to be missing, like the taskdef's.) So I could build an app, and if I wanted to, I could manually get the DB stuff working............... I guess I will check out the tdk in a few days and see if the torque stuff is working again :) Thanks for the reply :) Luke -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
