On Fri, Dec 09, 2005 at 08:43:11AM -0500, Kevin Dangoor wrote: > > On 12/8/05, Jason Chu <[EMAIL PROTECTED]> wrote: > > We ran into a point where being able to pass a kid template (from a > > non-form (let's refer to it as display) widget) to a javascript function as > > DOM calls would be really really nice. Then to refresh a widget, your JSON > > method returns this specially rendered kid template and you can eval it and > > just call swapDOM(). > > > > I just wanted to let everyone know that it's done, but I'm not quite sure > > who I should submit it to. It's a Kid serializer, but it only outputs > > Mochikit DOM calls, and the project that uses both of them (turbogears) > > leaves the rendering/serialization up to Kid. > > Yes, this is the right place to send them. Usually things that cross > projects like this are only likely to find a home here. > > This is very interesting (and a remarkably small implementation :) > > What I'm wondering, though, is this "better" than using innerHTML? It > seems entirely possible that this would be slower. > > Kevin
It is possible that it'd be slowed. I was having problems with innerHTML on IE, in that it didn't work. My widget was also an entire table, so the widget would have had to change to be able to pull out just the inner part. After doing the DOM serialization, I had some other problems in IE, so I'm not sure if innerHTML was as bad as it was. It may be slightly slower, but the processing bottleneck is the user's machine (because it does the DOM execution), so I'm not all that worried. Jason -- If you understand, things are just as they are. If you do not understand, things are just as they are.
pgpWnjojfyG0Z.pgp
Description: PGP signature
