Create a branch to support jCarousel 0.3

Thanks, this looks like a good start! Considering 0.3 isn't even released yet, it might be a bit early to try and use it on production sites, but I agree it would be a good idea to get rolling on a branch that supported it.

A few thoughts:

-    if (!options.hasOwnProperty('buttonNextHTML') && !options.hasOwnProperty('buttonPrevHTML')) {
-      options.buttonNextHTML = Drupal.theme('jCarouselButton', 'next');
-      options.buttonPrevHTML = Drupal.theme('jCarouselButton', 'previous');
-    }
-
-    // Initialize the jcarousel.
     $carousel.addClass('jcarousel-processed').jcarousel(options);

I find it odd that you specifically removed theming functions here, yet output the same markup in a non-configurable location later:

+        case 'control':
+          // Add the control buttons
+          $('<div class="prev-wrapper"><a class="jcarousel-prev" href="javascript:void(0);"></a></div>').appendTo($carousel);
+          $('<div class="next-wrapper"><a class="jcarousel-next" href="javascript:void(0);"></a></div>').appendTo($carousel);

Also, what's the need for "prev-wrapper" and "next-wrapper"? And aren't those awfully generic class names to be including in a module?

As stated in the patch, there are also a lot of TODOs that should be addressed, things like pagers being broken or options being hard-coded instead of using the available configuration options. What's you're thinking on moving that forward? I'd like to have something that works before branching. Leaving things mixed up to the bare-minimum of being functional leads to confusion.

Regarding the use of sub-libraries, how signficant is the advantage versus just using a compressed version of the whole library? I imagine 3-4 uncompressed src files are going to be larger than just all the libraries compressed together into a single file. Is the primary reason for this because the final version of jCarousel isn't released (and so there isn't a compressed package available)?

Regarding the theme options for options.buttonNextHTML etc - these options do not exist in 0.3 - which is why they are added as part of the control options. Thinking about this though navigational control elements should still be configurable.

I'm saying that instead of this:

+        case 'control':
+          // Add the control buttons
+          $('<div class="prev-wrapper"><a class="jcarousel-prev" href="javascript:void(0);"></a></div>').appendTo($carousel);
+          $('<div class="next-wrapper"><a class="jcarousel-next" href="javascript:void(0);"></a></div>').appendTo($carousel);

You should keep the theming code in tact like this:

+        case 'control':
+          // Add the control buttons
+          $(Drupal.theme('jCarouselButton', 'previous')).appendTo($carousel);
+          $(Drupal.theme('jCarouselButton', 'next')).appendTo($carousel);

It produces the same output and allows users to override Drupal.theme.prototype.jCarouselButton in their theme.

Thanks for your work on this, it's definitely going to save me work in the long-run as we'll need to support the 0.3 version eventually.

0.3 is out now, is there a branch out we can start helping with?

+1 on this and I hope the issue (or module) isn't dead. I ran into a problem with Safari 6 not playing nice with the navigation. The fix was simple (http://theweblab.com.bd/blog/jcarousel-safari-navigation-issue/). Before I made the change in the module's version of the script, I tried using it with the current jcarousel version (0.3) and it blew chunks. Would be nice to use the latest.

@knoebel the module definitely isn't dead.

We're working on a rewrite of the module including v0.3 support, and to hopefully fix a lot of the issues that user's are experiencing.

I'm torn as to whether to continue maintaining the current 7.x-2.x branch with jCarousel v0.2, so thoughts would be welcome.

Hi,
are there updates about the v0.3 support?

Is there any update on this? Any plan to support 0.3 version?

jCarousel 0.3 is a big improvement, but is architecturally very different.

We are working on a 7.x-3.x-dev branch for this module in git, which contains very early stages of a rewrite of the module to support jCarousel 0.3 and to resolve some long standing issues such as block caching.

This is fixed. Further discussion should probably happen on this issue: #2349751: [META] Support jCarousel v0.3