Ajax loading for blocks

Hi there,
this module was originally conceived with sidebar content in mind, and more as a space-saving idea than a performance-enhancing one. The idea was that where previously you would have your blocks positioned underneath each other, taking up a lot of vertical space, they can now take up the same space - just using tabs to view them. However, I will look into the possibility of adding the option to have the content loaded via ajax calls, so that it could be used for larger views.
Thanks for the feature request ;-)

Katherine

subscribe

subscribe

subscribe

Hi,

Been doing some research and found http://drupal.org/project/jquery_ui which is now installed.

In the quicktabs.module I've added:

jquery_ui_add('ui.tabs');

That's taken away that the content from the tabs load below each other before settling, but was that the correct ui to add?

I think everything still loads fully, and would prefer if content loaded on selecting a specific tab.

Any suggestions would be greatly appreciated.
Lilian

Hi Lilian,
I had just been thinking that the way to go about this would be to use jQuery UI tabs ;-) So you say it works well? I will play around with it and then I can modify the code so that it behaves differently if you have this jquery plugin installed and have chosen "ajax loading" for a particular qt block. I just need to figure out how to tell the tabs where to get the content if it's not going to be loaded straight away. But hopefully that won't prove too difficult

Katherine

Oops, in regards to jQuery, when installed, it does not work with Hierarchical Select .. totally incompatible .. what a pity.

Perhaps have another solution to load the tabs via ajax?

Thank you so much for your help.
Lilian

I am wondering this too. Help please.

cool feature for usability (with performance in mind !)

OK, so I'm taking a different approach on this and it's only going to be available in D6. It will not use jQuery UI Tabs. I have an extremely rough version of it working: it provides a separate interface for creating ajax-based QT blocks, allowing you to select only from views that have displays with paths associated with them (for the purposes of degrading without js so that the tabs otherwise when clicked will go straight to the path of the view). When the Ajaxified QT block is diisplayed, it pulls only the view for the first tab. An ajax callback allows the content for the subsequent tabs to be loaded on click. I might also add the ability to add nodes to tabs on these ajax-based QT blocks.
When I have made more progress on this I will create a new 6.x-2.x branch and put up a dev snapshot. In the meantime feel free to leave feedback about this approach.

Hi Katherine,

Hope this message finds you very well. Have been checking your project almost daily .. what a pity, there will be no 5.x version? Your beautiful module would be so amazing on my site.

All the best,
Lilian

Hi Lilian,
well it's not that it won't be possible in 5.x, it's just that I have to be realistic about what I'll find the time to do. Once I get it working in 6.x I'd be happy for someone to backport it - the only big difference will be the functions for retrieving the views to choose from - because of the huge differences between Views 1 and Views 2.

Katherine

FYI there's a dev snapshot up of the D6 version with this functionality - see http://drupal.org/node/327414#comment-1089667. There's nothing about it that's not backportable to D5; I guess I'll try to gauge the level of interest in this for D5 and see if I can put in the time, unless somebody else out there would like to have a go ;-)
@Miraploy - that blocktools module looks interesting. I don't think it is of use for this particular issue but it might be of help with http://drupal.org/node/279773

Hi,
no there's no technical difficulty - it's just time-consuming ;-) I'd need to re-jig the form to have 3 options. I guess I felt that ajax loaded blocks wouldn't be as useful as ajax-loaded nodes but maybe I'm wrong. My next priority on this is doing the code cleanup that I did on the 1.x branch. After that it's investigating the ajax paging problem. Then maybe I'll get around to adding in blocks...

Katherine

this is fixed in 6.x-2.x