> > Indeed! We (Leon really) have written our own set called
> > XMLSitePage/Layout/Screen. What we do is take an XML file
> > with embedded
> > Webmacro (our page CONTENT template), then execute the WM (to
> > get our page
> > CONTENT), and then transform this into HTML using XSLT. The
> > XML schema we
> > use is one we designed ourselves and describes content components in a
> > screen, e.g. "report", "grid", "form", "menu", etc. This is totally
> > independant of layout and formatting - it only describes the
> > CONTENT of a
> > screen.
>
> This sounds great. Any chance to take a peek at it?
> Would you consider adding it back to Turbine?
I'm the sharing type :-) If I get enough interest now I could add it soon, or
maybe send a copy to you.
The XMLSite* classes are all working and tested (we've been using them for a
while). The main reason for not adding it now is that I was waiting to move the
code to Velocity. I currently have not way of substituting xml entities
automatically, but Velocity would make this possible. WM also had the nasty habit
of adding newlines to the template (don't know if it's been fixed by now). In
short: Vel is my main reason.
Other than that the only thing that keeps me back is some other work I'm doing at
the moment. If I could get an example working is anybody else interested in
getting the WM version in the cvs and then switch to Vel when the time comes? If
enough people wants it I'll shift my priorities. (Let the +1's decide :-)
~ Leon
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
