I do like that. Adding an even further layer of abstraction to the mix would be even cleaner for the non-technical to implement. We could have 3 or 4 sets of useful defaults which could be chosen via the second class, or even by an underscore separated single class name where class="accordion" is the default and class="accordion_extras" is another set of options. Actually, the multiple class method would probably be easier to find via a jQuery _expression_.... so nevermind on the underscores. Excellent suggestions! And Klaus, I'm afraid it is I who owes you and Jörn some beers, both for the help here and for the plugin. I've never been to Berlin, though I have been to Germany. I visited a friend who was going to school in Tubigen (not sure if I spelled that right). I made it to Bon (Beethoven rules) and Munich, but not Berlin. Would be fun though. If you guys are ever in or near Atlanta, Georgia (USA) then be sure to let me know. Beers will be had for sure.
I'm really hoping to be able to contribute some cool plugins soon. I'm completely hooked on jQuery. It's one of those few times in my coding career when I learn a technique or find a library that makes me feel like everything I've written without it is old, busted crap. Do you guys do that? It's just like doing a database backed website w/o Rails or Symfony. The MVC idea just makes that much sense to me. It seems painful and arcane to develop sites without it now. Just like jQuery... the DOM traversal and manipulation with CSS and Xpath in JS is just too good an idea to ever be without, and jQuery is by far the best implementation.
Thanks again everyone! I look forward to releasing the results of this discussion soon for you all to pick apart and make better.
Paul
On 10/31/06,
Dave Methvin <[EMAIL PROTECTED]> wrote:
...
> Here's another solution that may be suitable for you: Do not put
> all options into the class, instead simply subclass the accordion class:
>
> <dl class="accordion accDefault"> ... </dl>
>
> <dl class="accordion accExtra"> ... </dl>
I share Klaus' concern on this. His suggestion of using classes to
indirectly represent plugin parameters sounds like a good way to go. Text
inside <code>, <div>, or any other tag is supposed to be content for the
user to view. Text inside <script> or element attributes is meant for the
developer.
_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/
_______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
