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
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
Would there be an official bug fix sometime? I am using it with
validation plugin
Thanks
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
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
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
>
> 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
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,
>
> 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...
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
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
Hi all, any idea?
thank you!
-will
On 29-mag-07, at 06:51:07, Will Arp wrote:
having an issue with svn metadata plugin if compressed with
packer 3.0 beta 8 or beta 9. code below will return undefined,
works fine with uncompressed version.
This is a p
$.meta.setType("attr", "data");
alert( $
having an issue with svn metadata plugin if compressed with
packer 3.0 beta 8 or beta 9. code below will return undefined,
works fine with uncompressed version.
This is a p
$.meta.setType("attr", "data");
alert( $("#one").eq(0).item_label );
thank you, have a great day!
-will
On 28-mag-0
howard chen wrote:
anyone can help?
It looks like you are missing the DOM-ready code. In addition, if you
use an attribute other then class there is no need to add curly
brackets. data="item_id:1, item_label:'Label'" should work.
--
Jörn Zaefferer
http://bassistance.de
14 matches
Mail list logo
