RE: [xsl] Site structured on XSLT.

["Claudio Russo" <crusso@xxxxxxxxxxxxxxxxx>]

Robert,

I'll do it. Mainly on the interface gap issue.

Claudio.

-----Original Message-----
From: Robert Koberg [mailto:rob@xxxxxxxxxx]
Sent: Martes, 08 de Julio de 2003 10:45 p.m.
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject: RE: [xsl] Site structured on XSLT.


Hi,

> -----Original Message-----
> From: owner-xsl-list@xxxxxxxxxxxxxxxxxxxxxx [mailto:owner-xsl-
> list@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Wendell Piez
> Sent: Tuesday, July 08, 2003 1:43 PM
> To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
> 
> Claudio,
> 
> At 03:58 PM 7/8/2003, you wrote:
> >As I've been addressing this issue tangencially, and I understand a
> little
> >bit where I want to be in my next step, I would like to know if somebody
> >can help me on this task: I would like to create a site entirely using
> XSLT.
> 
> That's cool.
> 
> >My initial approach was, as I said efore, an HTML with frames, which
> loads
> >a DOM,
> >that passes parameters to an XSLT, which is run and fills the HTML
> fields.
> 
> This is fine -- but going down this road, you are in advance (considerably
> in advance!) of where web standards have specified behaviors on clients.
> There are simply no vendor-neutral specifications for loading an HTML
> document with a DOM, invoking an XSLT process (with or without
> parameters),
> and "fill[ing] the HTML fields".

You could check out Sarissa:

http://sarissa.sourceforge.net/

>From the overview:

" Sarissa is a JavaScript meta-API. It bridges the gap of DOM XML extentions
between Internet Explorer and Mozilla (or Moz-based) browsers. It is an
effort to provide a common interface for those extentions, bringing them
closer to eachother. It was originally created to protect my sanity ;-)"

Best,
-Rob


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list