Hey Dave, so I re-engineered the event listeners to get registered on
initialization in js - and used basically the technique you describe. So
thanks ;)
-l
http://development.finetooth.com/?p=15
Dave Crane in message Re: [Rails-spinoffs] XSLT Ajax Widget implementation
(Fri, 06/09 09:42
things in the grid to work
with this technique, but that's not going to be too tough. I think
I'm reasonably satisfied by the speed of Sarissa to continue developing
along this path.
-l
http://development.finetooth.com/?p=15
Ryan Gahl in message Re: [Rails-spinoffs] XSLT Ajax Widget impl
Hey Ryan, check out the new button that does the clientside XSLT using
the Sarissa library. Try the 200 rows, and notice how lightning fast it
is w/ Sarissa. I think Sarissa uses the native xsl engine, but anyhow,
it is really swift!
Ryan Gahl in message Re: [Rails-spinoffs] XSLT Ajax Widget
Hi Lindsey,
Without looking at the internals of your app... if you're building up a table
and assigning event handlers to every row, you could make it quicker by
assigning one event handler to the entire table, which then figures out which
row was clicked (using Event.element, for example) and
up better ;) Is there any particularly fast way for
assigning all the events to prevent that slowdown time onload?
Ryan Gahl in message Re: [Rails-spinoffs] XSLT Ajax Widget implementation (Fri,
06/09 09:39):
> Neat, and has it's place, but I'm not sure about it's scaleability or
> u
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
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
