Thomas 'PointedEars' Lahn wrote:
Go away!
Another bad day, Tommy? Take a glass of milk and go to bed earlier
today.
To OP:
XML/XSLT scheme I mentioned before consists of three components:
1. Page template with persistent parts (like title, copyright, about
etc.) and script
2. Page style table (equiv to CSS)
3. XML data file
Joined together on the client-side they produce one ready to use page.
The trick is that you don't need any special actions for data
allocation: it's all defined on the page template. Using rather
primitive scripting you can just switch from one XML source to another
(from separate files or served from a server script). Kind of
"zero-maintenance" page. This technique was long time kind of a taboo
for the same reason that Microsoft Data Island: "other cannot support
it". But now I see no reason to not use it. Other "others" support it
too... mainly...
Other approach is Microsoft Data Island. It's amasin *what* actually IE
had to propose for a longest time (since 5.x). But of course it will
never be supported by FF / W3C.
I have a data island implementation I had to do this summer. My
customer did not want to pay for the extra cross-browser coverage :-(
and I did not feel like doing that on my own time expences :-)
So I did this store solution and I called it Helen (which stays from
the Greece myth but also sounds close to "Hell on them"). Absolutely
nothing ingenius: just all data island/behavior collected, cleaned and
connected. If you're interested, I can give you a link.
The third approach would be I guess Sarissa - like programs. I cannot
say too much on it because I never managed to run the provided test
cases but maybe I just pressed the wrong buttons. You may get more
lucky:
<http://sarissa.sourceforge.net/doc/overview-summary.html>
And what code did you write?