nodequeue pager (pager through nodes in a queue) - code provided
litwol - May 16, 2009 - 06:47
| Project: | Nodequeue |
| Version: | 6.x-2.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | needs work |
Jump to:
Description
So this may not be perfect but i think its a good start to get the ball rolling.
here is the code : http://drupalbin.com/9359
This is my first time using nodequeue so i am having a hard time providing a proper integration with nodequeue and views etc etc.
#1
Thanks for taking the time to write this code!
There has been some discussion about the potential complications of such a feature at #378160: Pageing for long nodeques which is worth reading. Please see the discussion there and feel free to jump in.
If this is not a duplicate, feel free to re-open this issue.
Thanks!
#2
This is not a dup. That issue talks about the admin view of a nodequeue.
This is a pager for an individual node, using next/prev to go through a nodequeue jumping from one node to the next. This is the kind of pager you would use on galleries, and it is one of the features that could make nodequeue an excellent tool for creating user gallery sets (think: flickr)
Though this use a paging object which is probably unnecessary...nodequeue's code isn't OO.
#3
Thanks for the clarification. This would be an awesome addition, litwol! I agree with merlinofchaos that it would be more consistent with the rest of Nodequeue to have his feature not be OO. In any case, I hope to review soon.
#4
There is no technical reasons behing me doing this in OO, i just wanted to scratch my own itch. I do not know nodequeue well enough to provide proper inegration, but with some guidelines and points from you i'm sure i could do it *the right way*.
#5
Any reason not to base this on http://drupal.org/project/custom_pagers ?
#6
Marked #459830: Previous/Next Navigation based on current node as a dupe of this.
#7
Needs more information for more than 5 weeks -> closed.
#8
It doesn't need more information. It needs work to port OO code to drupal/nodequeue standard.
#9
Could you answer the question in #5?
#10
It is different on a basis that it is more light weight, it is more an an API for developers than a self contained feature like custom_pagers. IMHO both are not mutually exclusive and have their own use cases. Best outcome would be to have both integrations. have to start somewhere right ?