I've found that writing my code with a modular OOP plugin mentality,
it's a lot easier to reuse my own code and trade snippets with others,
since it's already abstracted into a plugin.
I don't know if you've seen Mike Alsup's recent Learning jQuery post
about Plugin Dev, but it's a good read abou
Thanks all. I did have a think about which way around I wanted it to
work. Thinking about what will be returned is also handy.
I can see me wrting more plugins now.
Thanks again.
Adrian
On Oct 30, 2:51 am, Dave Methvin <[EMAIL PROTECTED]> wrote:
> > $(ELEMENTS_TO_CHANGE).syncValue(ELEMENT_I_WI
> $(ELEMENTS_TO_CHANGE).syncValue(ELEMENT_I_WISH_TO_COPY).show();
> That way your focus is on the changing element.
I tend to agree; if that's what you want then it's pretty short
already.
$(syncElements).val(formatter(elementToCopy.val())).show();
The other way around isn't a lot longer but it
Adrian,
Which elements would you likely work on next after copying values?
The order matters because you're going to return a jQuery element or
element set. I think it's better to be able to do something like
this:
$(ELEMENTS_TO_CHANGE).syncValue(ELEMENT_I_WISH_TO_COPY).show();
That way your fo
It'd be best to post a link to the sample. Most people won't go through the
time to copy and paste the above code to execute it.
Cheers,
-js
On 10/29/07, Adrian Lynch <[EMAIL PROTECTED]> wrote:
>
>
> I hope this is ok to do. I've just done my first plugin and I thought
> I'd ask for anyone's opi
5 matches
Mail list logo
