Paul McLanahan wrote:
> @jake
> I'm really liking the <code> tag idea. If I'm understanding you
> correctly, it would work something like associating a label to an input
> using the "for" attribute. I'd just be associating a code tag's
> contents with a specific DL either by location in the markup or maybe by
> some specific classes. That might prove to be the easiest and most
> semantically correct solution.
I find that a good way of passing data/options/etc to javascript is
using hidden inputs:
<input type="hidden" id="stuff" value="{put:'your',options:'here'}"/>
I often use JSON notation in the value, then you can just eval() it.
var options = eval($('#stuff').val());
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
