Closed (fixed)
Project:
Nodequeue
Version:
7.x-2.x-dev
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Unassigned
Reporter:
Created:
30 Sep 2008 at 06:29 UTC
Updated:
15 Feb 2009 at 17:20 UTC
Jump to comment: Most recent file
Comments
Comment #1
davideads commentedHere's a better version of this patch, which properly enables random fetching, and drops display-related arguments from the fetch function signature.
Comment #2
ezra-g commentedThis sounds reasonable to me . Thanks for the revised patch - I hope to review this soon,
Comment #3
tirdadc commentedThis is definitely useful, it would be great seeing this integrated into the next release.
Comment #4
ezra-g commentedhope to review and commit this this coming weekend. It does need some rerolling by someone, possibly me, to remove the lowercase 'true' changes that are unrelated to this patch.
Comment #5
ezra-g commentedI finally got a chance to give this some attention.
The code here is solid but it seems like the function naming has the potential to be confusing. nodequeue_fetch_nodes returns loaded (but not rendered) node objects, while nodequeue_fetch_front, nodequeue_fetch_back and nodequeue_fetch_random return rendered node objects. Perhaps the fetch functions should be renamed nodequeue_load_front (and so on), nodequeue_nodes would then be renamed nodequeue_view_nodes, and nodequeue_fetch_nodes would become nodequeue_load_nodes. Then, when using the load (formerly fetch) functions, module developers could simple call node_view from within their modules.
What do you think?
Thanks for your interest and patience. I'll review any feedback (or rerolls) quicker this time ;).
Comment #6
ezra-g commentedI made those name changes and did the related refactoring. Committed. Thanks!