> There is an example of a layout that does not use ECS, WebMacroOnlyLayout.
>
> BTW, Layout/Action/Screen and to some extent Page modules are completely
> replaceable. Turbine provides some default implementations but you should
> feel free write your own whenever the supplied ones do not meet your
needs.
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.
Frank
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
