Neat, and has it's place, but I'm not sure about it's scaleability or utility as a catch-all widgetry engine. Try 200 rows. Via client side XSLT I get a "script is taking too long" alert in FF. Via server side XSLT it takes a while (longer than I would expect for 200 rows). 200 rows isn't a lot of data (at least not the data set represented on the demo page).

Maybe it can be tweaked though. But personally I think maybe XSLT is better suited for something like skinning. I noticed in your XSLT file you are attaching a bunch of event handlers inline. Have you made any XSLT widgets yet where the behavior/event wiring is de-coupled from the presentation?




On 6/9/06, Lindsey Simon <[EMAIL PROTECTED]> wrote:

See this post for a test page / test case for using XSLT to produce an
Ajax Datagrid widget: http://development.finetooth.com/?p=15 - I'd like
to find some other XSLT/_javascript_ developers out there who are
interested in this approach as well!

I used prototype/scriptaculous in my widget and I've posted about it
before. What's neat about this page is the client-side implemenation of
XSLT to actually create the thing from semantically proper xhtml markup
instead of some serverside object or from _javascript_ code.

--

Lindsey Simon
[EMAIL PROTECTED]
Key fingerprint = C6A9 B9D9 677E A631 3E7F  43BF 5E2F 77F1 A33C B117
Public Key: http://www.commoner.com/pubkey.asc
_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

_______________________________________________
Rails-spinoffs mailing list
[email protected]
http://lists.rubyonrails.org/mailman/listinfo/rails-spinoffs

Reply via email to