[jQuery] Re: Metadata plugin performance issues

2007-09-24 Thread voltron
Oh! I skipped that, thanks! On Sep 24, 7:51 pm, Jörn Zaefferer <[EMAIL PROTECTED]> wrote: > voltron schrieb:> Would there be an official bug fix sometime? I am using it > with > > validation plugin > > As mentioned in the previous post: I already fixed that. > > -- Jörn

[jQuery] Re: Metadata plugin performance issues

2007-09-24 Thread Jörn Zaefferer
voltron schrieb: Would there be an official bug fix sometime? I am using it with validation plugin As mentioned in the previous post: I already fixed that. -- Jörn

[jQuery] Re: Metadata plugin performance issues

2007-09-24 Thread voltron
Would there be an official bug fix sometime? I am using it with validation plugin Thanks

[jQuery] Re: Metadata plugin performance issues

2007-09-23 Thread Karl Swedberg
On Sep 23, 2007, at 5:19 PM, Jörn Zaefferer wrote: polyrhythmic schrieb: If you need to store just key/value pairs mapped to an element, why not use the new jQuery.data method (aka "Expando Management")? I'm using this in a caption plugin I'm writing to store the id of the caption element t

[jQuery] Re: Metadata plugin performance issues

2007-09-23 Thread Jörn Zaefferer
polyrhythmic schrieb: If you need to store just key/value pairs mapped to an element, why not use the new jQuery.data method (aka "Expando Management")? I'm using this in a caption plugin I'm writing to store the id of the caption element to its image. The code is fast and has been working sup

[jQuery] Re: Metadata plugin performance issues

2007-09-23 Thread polyrhythmic
If you need to store just key/value pairs mapped to an element, why not use the new jQuery.data method (aka "Expando Management")? I'm using this in a caption plugin I'm writing to store the id of the caption element to its image. The code is fast and has been working super smooth for me, I pref

[jQuery] Re: Metadata plugin performance issues

2007-09-23 Thread Erik Beeson
> > I do it like this: > > It costs more performance-wise, but I think it is worth it in terms of > flexibility and clarity, which is why I went out of my way to fine- > tune the metadata plugin. I went with the nested script block because I think it's the only way that's actually valid HTML. Th

[jQuery] Re: Metadata plugin performance issues

2007-09-23 Thread Diego A.
I'm not arguing with you either, and I'm not discrediting your method. I was intrigued to know more because we had similar requirements and went in different directions. I see the benefits of your method. It is without a doubt the fastest and most efficient of the two. > With the metadata plugin,

[jQuery] Re: Metadata plugin performance issues

2007-09-22 Thread Erik Beeson
> > I didn't know about logical operator short-circuiting, thanks for the > info - it's good to know. > > But this obviously wasn't in place on my tests or I wouldn't have got > the results I did. So I don't think logical operator short-circuiting > is a reliable enough solution to this problem...

[jQuery] Re: Metadata plugin performance issues

2007-09-22 Thread Diego A.
Hi Erik, I didn't know about logical operator short-circuiting, thanks for the info - it's good to know. But this obviously wasn't in place on my tests or I wouldn't have got the results I did. So I don't think logical operator short-circuiting is a reliable enough solution to this problem... I

[jQuery] Re: Metadata plugin performance issues

2007-09-21 Thread Erik Beeson
Thanks for this info. I eventually gave up on the metadata plugin in favor of a global variable for holding my metadata. So instead of $('#someID')[0].data, I now just do mynamespace.mydata['someID']. You mention breaking up the if statement to keep a function call from happening. Thanks to logica