IMO, thats too restrictive. What, if the designer wants to have more than one
prev and next controls, ie. two above and two below the list?
What if he wants to use <button> elements or whatver instead if images (ok
john, you noticed that at the end of your posting)?
I also thought about passing the selectors for buttons as options. But that
restricts setting up multiple (static) carousels with just one line of
jQuery('.jcarousel').jcarousel();
As it is now, you have many options to follow "progressive enhancement". You
can pre-format the markup with css or just hide it from browser without
javascript:
<div class="jcarousel-clip" style="display:none">[...]</div>
and you use
jQuery('.jcarousel').jcarousel().show();
(BTW, thats why i love jQuery so much :))
John Resig wrote:
>
> What everyone is getting at - and I agree - is that the extra
> (non-semantic) markup should be included dynamically by the plugin.
> The code to do so would be trivial:
>
> $("#myCarousel")
> .wrap("<div class='jcarousel'><div
> class='jcarousel-clip'></div></div>")
> .parent().before(" prev-disabled.gif next-disabled.gif"
class="jcarousel-next ");
>
> Which would give you identical markup to what you have, if you target
> the OL or UL directly. Additionally, I would recommend that you wrap
> the images in additional helper <div>, giving the developer the
> ability to fully customize the layout with CSS (rather than being
> forced to use the element).
>
> --John
>
> _______________________________________________
> jQuery mailing list
> discuss@jquery.com
> http://jquery.com/discuss/
>
>
--
View this message in context:
http://www.nabble.com/jCarousel-tf2205628.html#a6141173
Sent from the JQuery forum at Nabble.com.
_______________________________________________
jQuery mailing list
discuss@jquery.com
http://jquery.com/discuss/
