RE: XSLT and XForms

yes, that's exactly what I do. But it's not that slow unless
you use large tables (grids). For normal forms with some 
kilobytes of HTML it's still fast enough.

Table manipulation performance decreases significantly for
larger tables. The separate "table object model" in IE is even 
slower than DOM.

Again, DOM seemed to be more flexible then XSLT because XSLT 
demands the use of innerHTML. 
For instance, if you wanna disable your INPUT using XSLT
you have to do this:

X.innerHTML = "<INPUT name='i1' type='text' disabled='true' size='15'
value='ABC'...";

Of course the string must be generated by the XSL processor fist.
With DOM it's just

i1.disabled=true



BTW, I still use XSLT for client side sorting and filtering in
my dataset component.



> -----Ursprüngliche Nachricht-----
> Von: Plechsmíd Martin [mailto:Martin.Plechsmid@merlin.cz]
> Gesendet: Montag, 10. Juni 2002 10:55
> An: Schulze, Matthias; 'www-forms@w3.org'
> Betreff: RE: XSLT and XForms
> 
> 
> Can you explain what you mean by "DOM manipulations"? You 
> mean that when
> your XForms processor sees in an xforms:group an xforms:input 
> element, than
> it adds it into the resulting HTML using something like
> 
> 	group.appendChild(document.createElement("INPUT"))
> 
> ? I would guess that this is unbearingly slow for large 
> forms, knowing how
> slow DOM manipulations in IE are (were).
> 
> 	Martin.
> 
> 
> > -----Původní zpráva-----
> > Od: Schulze, Matthias [mailto:schulze@dresden-informatik.de]
> > Odesláno: 10. června 2002 10:39
> > Komu: 'www-forms@w3.org'
> > Předmět: RE: XSLT and XForms
> > 
> > 
> > 
> > These are my experiences with GUIs and XSLT:
> > 
> > I've started creating client side GUI components for IE6 a few 
> > months ago.
> > First I used XSLT for the HTML generation. The transformation 
> > alone was really fast but the IE parsing and rendering took too
> > long, especially for large grids. 
> > 
> > Later on I found that XSLT was unpractical, especially for small
> > pieces of HTML. And when it comes to user interactivity changes 
> > to the HTML are really small!
> > 
> > At this time I had already started coding GUI changes as DOM 
> > manipulations. Suddenly I had two implementations for one 
> > problem: one as XSLT and another as JScript DOM manipulation. 
> > Thus I decided to abandon XSLT.
> > Now the 100% DOM version is not really faster, but more flexible.
> > IE parsing and rendering still takes about 70% of the response 
> > time. Perhaps M$ can improve that...
> > 
> > 
> > But anyway, IMHO DOM manipulation is the best way for 
> > implementing rich client side GUIs in a browser. 
> > 
> > 
> > greets,
> > 
> > Matthias
>

Received on Monday, 10 June 2002 05:28:00 UTC