Posted by Woggers on April 2, 2009 at 3:30pm
Jump to:
| Project: | DraggableViews |
| Version: | 6.x-3.x-dev |
| Component: | Documentation |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
So I guess it's always supposed to be NATIVE handler now? Can I drop my Weight CCK field from the content types then? or should it remain?
Comments
#1
Initially I used cck fields to satisfy my needs. Then I restructured the module in order to expand its scope and introduced handlers. At this point the native handler became a better alternative (performance) if you don't really need the order/parent fields to show up on the node/edit page.
Yes, the Cck fields can be dropped when native handler is used.
Greetings,
Sevi
#2
Is the native handler persistent beyond the draggable view? In other words, can alternate views be made which will respect the native handler order? This, as I see it, is one advantage of using a CCK field to store order.
The other advantage is that nodereference opens up integration with any module that uses or hooks into it. In this light, do you foresee that CCK handlers might warrant inclusion?
#3
Where the CCK handler glitters because of integration with other modules the Native handler scores because of its nonexistence (performance).
Yes and no, kind of.
The yes-part: The values provided by the native handler cannot be used by other views but by other displays. As far as I know there's no need for persistence in other views when you simply can use different displays to "group" all views (actually displays) which use the same order values.
The no-part: But there's no way for other modules to use these values. This is why I'll never drop CCK handler.
Is this what you wanted to hear? :)
greetings,
sevi
#4
Thanks for the thoughtful explanation. In a sense, it is precisely what I wanted to hear.
#5
question, answered.
#6
I used to be able to setup draggableviews easily with the CCK number field. I have tried following the handbook documentation and the README using the native handler, but I haven't had any luck.
I see there is an included cck handler, but I'm not sure how to use it. And given what's been stated above, I'm lead to believe that the functionality was even removed.
So, I'm not sure if this issue is actually to help explain the current code or recommit the older handler too.
#7
"DraggableViews CCK Implementation" is a separate sub-module that comes with the DraggableViews module. Activate this module and you will find another option you can choose for the "Handler" (Style-plugin settings).
When this issue is fixed please rename it back to it's original title.
#8
I guess this issue is fixed.
#9
Automatically closed -- issue fixed for 2 weeks with no activity.