> Jason, this is EXACTLY the kind of thing that Leon and I have been thinking
> about! We would like to give input on this, especially the XML schema that
> will obviously be developed as we go along. We already use our own XML
> schema to describe the content of pages, e.g. forms, reports, lists, etc.
> (NOT the HTML kind!).
Cool!
> Here is a snippet from one of our XML+WM screen
> templates, so you can see what I mean:
>
>
> <screen title="3dGenesis Administration - Customers">
>
> #parse "menus/mainadmin.wm"
>
> <heading1 name="customers">
> <title>Administration: Customers</title>
> <action text="add" tip="Add a new customer"
> url='$link.setPage("customerform.wm")'/>
> </heading1>
<snip>
>
> Look Ma, no formatting #@$%!!! This we then transform into HTML using Xalan
> XSLT, through our own Page, Layout and Screen classes. Adding new pages or
> changing the global look of a form is now as easy as pie.
Neat. We can definitely combine different forms of site
generation. I work with a lot of designers who would still
be put off by not having direct control over the look. For
some reason they love formatting #@$%!!! html. But Xalan
would be awesome the uniform presentation of larger bodies
of info, like say catalogues.
In your example above, do the macros get passed into
the resultant HTML and the HTML templates pull in
info, or do you run the transformation everytime
the page is hit?
>
> Lets keep talking about your (and our!) ideas...
>
> Frank (and Leon)
That would be great!
jvz.
--
Jason van Zyl
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
