On 10/03/2007, at 5:56 AM, Brice Burgess wrote: > Joel, > > I wrote those reviews/changes @ 4am, and after more thought realize > most of them were unnecessary. The original code would work @ multiple > menus at once without the return this.each(...); The reasons I began > with that is I wanted to do my "serializing" within the .each > statement, > instead of the "over" function (at first). Also, as for settimeout > returning an integer instead of a referencing function, this would > eliminate the need for the serializing in the first place -- unless of > course, you want to attach more data to the element (such as item > specific timeout values, effects, etc). > > As for attaching your functions over/out functions to the jQuery > object -- I would not do this... unless you need them available > globally. Having them within the scope of the plugin is more > appropriate. > > ~ Brice
Well, an extra thank you for taking time @ 4am to respond! I learnt a lot from your advice regardless of whether it turned out to be the way to go or not. Just for closure (not the JS kind), here is the beginnings of a demo page (which I also did at 4am last night!) showing the plugin working not only with 3 levels of heading without having to change a thing (I was surprised!) but also on multiple .nav elements using one call to the plugin. http://users.tpg.com.au/j_birch/plugins/superfish/ Thanks again Brice. Joel. _______________________________________________ jQuery mailing list discuss@jquery.com http://jquery.com/discuss/
