Druplicate Module

It states nowhere that it's compatible with 6.x. So it's not just you, it's the module :)

This module is a duplicate module. You can achieve the same thing via jCarousel and Views Carousel (patch)..... Panels Carousel needs a port.

I suggest we work with those modules instead of sticking them all into one module. We also should recommend people use those modules instead.

Uhh, didn't mean fixed, meant active.

The funny thing is that most people found it rather annoying to have separate modules, which is why I started this module in the first place. Many folks (including the maintainers of other carousel-related modules) had promised their cooperation but failed to do so due to lack of time (myself included). So it's not so much ah duplicated module as it was meant to be the next logical step to consolidate several related modules…

Consolidating modules is not a good idea as it just ends up becoming a family of unmaintained modules (like Views Bonus Pack, panels and export are the only maintained ones there). Modularizing jCarousel also allows other systems to use jCarousel without depending on Views Carousel, or the Panels integration. I'm running two sites so far that use jCarousel without Views or Panels. Also, other modules that could take advantage of jCarousel as its own entity, rather then needing the full Carousel family.

If people find it rather annoying to download separate modules, then they're using the wrong CMS ;-) . The CAPTCHA family does the same thing. CAPTCHA is the base API, and then there are addon packages (reCAPTCHA, CAPTCHA Riddler, etc). It's modular and whatever doesn't have to be part of the base API isn't in there.

What if Carousel became some kind of integration point for all carousel related modules. It would allow you to use either jCarousel or jCarousel Lite, through a single API, or something? I don't know, what are your thoughts?..... Also take note that only 9 websites are using Carousel, while 800ish websites are using jCarousel. Seems like 800 websites don't mind downloading the separate modules ;-) .

i'm thinking it should be part of Views Slideshow as a submodule (standalone project requiring VS)

also, a lot of modules are moving towards /sites/all/libraries for their external libraries/scripts, some also requiring Libraries API.

would be nice if the same was done for Carousel.
the scripts would have to be downloaded separately, but they would then be sharable.

but then again... if there's already jCarousel, why create Carousel?
i'd say patch jCarousel in that approach and avoid creating yet another module.

actually, there's a LOT of other modules.
i think you should look at them.

i also think separate modules is the best way.
and jCarousel should be fetched from the libraries directory, and downloaded and installed by the user separately.
this is Drupal.

duplicating issue:
---------------------------------------------------
hey
i'm finding a LOT of slideshow modules, but particularly, too many jQuery Carousel modules.
any plans to merge/replace these kind of modules?

jCarousel (jquery plugin) modules (the big two):
jCarousel vs JCarousel formatter framework

Views modules (depends on the modules above):
Views Carousel vs jCarousel for Views

Other similar modules:
Carousel - uses jCarousel (jquery plugin), the reincarnation of jCarousel for D7, in development
jCarousel Lite - uses jCarousel Lite (jquery plugin), limited configuration
Views Slideshow JCarousel Thumbs - uses jCarousel Lite (jquery plugin), integrated with Views Slideshow
jQuery UI Carousel - uses jCarousel (jquery plugin)
jcarousel block - uses jCarousel (jquery plugin), very limited configuration

there are a few other jCarousel modules and lots of other slideshow modules (many use jQuery.cycle or other plugins)

Closing the issue queue. This project has been (re-)merged with jCarousel in the 2.x branch. It includes Views integration so Views Carousel is no longer necessary either.