type: widget
realease: 0.0
priority: low
status: in planning
documentation: N/A
demo: N/A
1 - Description:
A carousel or push box acts like a scrolling panel except instead of a scrollbar, buttons are used to page through the set. This widget may also be set up to auto-play so it will display the frist page or items for a set interval, then automatically page forward to the next. If the user clicks on the paging arrows, the auto-play should have the option to pause itself. Any markup can be used inside the carousel (images, product listings, etc.) and the width of the widget should be customizable. Animations should be used for pagination with smooth horizontal movement with easing as the default. The number of items scrolled per click should be user controlled. An optional number bar or dot bar should be available for direction navigation to a specific page (See examples below).
Existing plugins:
Existing widgets:
2 - Visual designs:
3 - Functional Specifications/Requirements:
4 - Markup & Style:
4.1 Initial markup examples
4.2 Recommended transformed HTML markup
4.3 Accessibility recommendation
4.4 CSS & Theme
5 - Demo of the plugin
6 - Current issues and suggestions:
Comments (10)
riscarrott said
at 7:10 pm on Apr 13, 2011
Hi there,
I've recently started work on a Carousel leveraging UIs Widget Factory but as these specs aren't overly fleshed out at the moment I can't be sure if it's the sort of thing you guys are looking for but it'd be cool to get any feedback you may have: https://github.com/richardscarrott/jquery-ui-carousel/
Oh, and apologies for stealing your namespace, I never got round to coming up with a decent name to use for my own widgets...
Scott González said
at 8:18 am on Dec 1, 2011
@Ivan: Please do not leave comments/descriptions when making changes. If you leave a description, then pbwiki stupidly sends only your description and not a diff of your changes when sending notifications. Also, this is not something the team is focusing on any time soon.
Scott González said
at 8:20 am on Dec 1, 2011
Ivan: If you want serious feedback, please look at other widgets that are actually released or in planning and get an idea for what our APIs look like. Your proposed options are very far from what we do.
Ivan Kuzev said
at 8:49 am on Dec 1, 2011
i am trying...but if you can be more specific? i am going to change the plugin match the needed specifications.
it will be great if someone helped me with the planing...but thats too much to ask.
Jörn Zaefferer said
at 8:55 am on Dec 1, 2011
To start, drop all options that only achieve something that can be done using CSS only. Collapse animation-related options into one, preferably using _show/_hide methods from $.Widget.
For things that the theme controls, remove the options. If someone doesn't want rounded corners, he just uses a theme with no rounded corners.
Corey said
at 11:11 am on Dec 1, 2011
Also - regarding the options that are "cap" options, I assume these mean "caption" ? Please use "caption" instead of "cap" - its much more descriptive and doesn't require assuming or guessing at the meaning of the option
Ivan Kuzev said
at 11:25 am on Dec 1, 2011
i am trying to not use shortenings..and cap i call those two elements on both sides(the ones with arrows on them)
i dont think caption is adequate becouse there are two of them and one is at the bottom. ...if you have a suggestion what to call them please let me know
Corey said
at 2:12 pm on Dec 1, 2011
perhaps "navigation" - "paging" something along those lines?
Ivan Kuzev said
at 2:30 am on Dec 2, 2011
what about
navigation.ends
and i think i will use navigation.sides for a scrool bar or number pagination on the sides or in top-bottom when in horizontal orientation
Corey said
at 11:13 am on Dec 1, 2011
Should there be a way to leverage jQuery UI effects for the transitions?
You don't have permission to comment on this page.