Hi,
What I means is that, jCarousel arose out of combining a number of carousel modules in order to minimize the number that were being created.
It's done really well in that regard, but the jCarousel javascript plugin itself continues to display a number of issues with missing items and glitchy behaviour.
The jCarousel.js creator is planning to release a jCarousel 3 that fixes a lot of these bugs, and there is also a jCarousel 2.8 which apparently has a number of fixes too. I've attempted to switch the Module javascript, with the updated jCarousel 2.8 but it failed, so reverted back to the 2006 version, which we have to admit is very out of date now.
There are probably loads of great jQuery carousel style plugins out there now which would do a better job than the plugin and perhaps we need a jCarousel module to do just that. One of the problems with the jCarousel javascript module was that the creator took a long time to fix these issues, and that's fine because people are busy, but in that time other people have been producing alternative scripts.
I think we need to update the javascript plugin for this module or even change it to one that has very few issues. Because apart from the issues with the javascript plugin itself, the module does exactly what it needs to and very well.
An alternative module could be developed but I don't think that would help if the current one can solve the problem with javascript plugin?
It would be good to keep it here.
What do people think?
Comments
Comment #1
quicksketchTo correct these statements, the author is planning a 0.3 release. There is also a 0.2.8 release, which the jCarousel module is already using. See #1196558: Update to Version: 0.2.8
Do you have any suggestions here? jCarousel became popular because it works (for the most part). The author of the jCarousel script is working on a 0.3 version (essentially a rewrite) that builds on the experience of the existing jCarousel script, I'm guessing that it will probably be a pretty respectable script by the time it's finished. At that time, a new branch of the jCarousel module will probably be created to support that particular version, since it will have quite a different set of requirements as the way things like AJAX paging, navigation, and circular carousels have all changed significantly.
At the current moment, I don't know of a better script. jCarousel certainly has it's faults, but honestly any script is going to have faults or at least limitations. Most of the newer scripts available focus on simplicity and leave out things like circular carousels or AJAX loading. That's not necessarily a bad thing, but I think jCarousel will continue to be useful for being a flexible solution. The last thing you want is to end up with multiple carousel scripts on the same site.
Comment #2
Bensbury commentedI agree jCarousel does a good job.
There is an update to the current jCarousel script which apparently fixes a number of issues with it.
I would be concerned about waiting for the creator to create the new version only because it's been such a long time in the works, and there is no indication when it's going to be released.
Comment #3
quicksketchThe latest official tag is 0.2.8, which we're already using: https://github.com/jsor/jcarousel/tags
Yes true. The jCarousel library had a 6 month release between 0.2.7 and 0.2.8, so this isn't too much beyond the normal release cycle. It's clear that the developer has been working on it recently in any case. When the next release comes out we'll update the module to support it.
So back to the original request: What exactly do you want here? Just "a better library"? Such a request isn't exactly actionable, especially within the issue queue for the jCarousel module, which will undoubtably continue providing integration with the jCarousel library. If a better library comes along, I (or someone else for certain) will write an integration for it.
Comment #4
quicksketchSee also #1422542: Create a branch to support jCarousel 0.3.
This issue itself doesn't really have anywhere to go, so I'm marking it won't fix.
Comment #4.0
quicksketchmodules ---> plugins : to avoid confusion use of module is misleading when referring to jQuery and not Drupal