jCarousel: AJAX support does not work in Views 3

For example, if your view was of NID's, and you chose to display "all items" in the Views menu, then the view DOES originally have to load ALL of the items, no?

Thoughts? Thanks.

Really appreciate your attention to this! I'm excited for this to work. Will keep following up.

I think everything is working properly. Is there any way to specify how many items an ajax load will display. It seems to do 3 at a time by default.

Please excuse me if there have been further updates here that I am unaware of, but I noticed a new problem. When the Views JCarousel using ajax is on the page w/ other views using ajax, Views Jcarousel ajax updating is broken after the View using an ajax filter is used.

The reason for this is that the Drupal.settings.views.viewsAjax object is updated improperly. The properties held by the carousel are overwritten by another object.

I have a hackish solution. Basically, I clone the Drupal.settings.views.viewsAjax object in the following way when Drupal.behaviors.jcarousel in the jcarousel.js is run for the first time:

if(typeof Drupal.settings.jcarousel.ajaxViews==="undefined") {
			Drupal.settings.jcarousel.ajaxViews = $.extend(true, {}, Drupal.settings.views.ajaxViews);
		}

I then utilize the Drupal.settings.jcarousel.ajaxViews object that is unaffected by my other views to keep things running smoothly. Obviously, there is a deeper problem w/ the interaction between the Views, but this is the solution quality I can achieve w/ the time I have.

OK, I still think there is work to do to make this compatible with Views 3. It seems to me that caching will require for this View to be pluggable. Currently the module works through changing the offset of the view, which means that the same set of results get returned over and over again. I think something like the following would need to be implemented instead (using Views Infinite Scroll as a reference which does function with caching):

class views_plugin_pager_infinite_scroll extends views_plugin_pager_full {
function query() {
    parent::query();

    $next_page = TRUE;
    if (!empty($this->options['total_pages'])) {
      if (($this->current_page + 1) >= $this->options['total_pages']) {
        $next_page = FALSE;
      }
    }
    if ($next_page) {;
      $limit = $this->options['items_per_page'];
      $this->view->query->set_limit($limit + 1);
    }
  }
}

It seems that setting a new "limit" triggers a new query to run. Changing the offset does not seem to run a new query.

Quick update. Tried to add: $view->set_current_page(($last)/($last-$first)), since it appears that this is a factor in caching (see cache_set in views_plugin_cache), but it is not helping.