Posted by omjn on May 15, 2009 at 3:46pm
Jump to:
| Project: | DraggableViews |
| Version: | 6.x-3.x-dev |
| Component: | Code |
| Category: | feature request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
OK, I'm just throwing this out there, so feel free to put me in my place!
I was just wondering if there would be much work involved in adding a handler for book module outlines?
Although the book module has its own drag and drop hierarchy reordering page, I find it gets quite unwieldy to use on large books (no expand/collapse being the main reason). Draggableviews could act as an excellent replacement book outliner with expand/collapse, while also being able to reorder a book at an arbitrary parent using views arguments. It would also allow arbitrary content to be added to the outline that cannot be added using the book module outline.
Comments
#1
If anybody is able to consult or assist in the creation of a book handler please let me know. This is quite a big requirement for me right now. I'm able to provide some funds, depending on how much is actually involved.
#2
I just added the Book handler to the DraggableViews project.
The module "DraggableViews Book handler" is a sub-module of the DraggableViews module and must be activated seperately. It provides a default view that appears on each book node page (tab: "rearrange").
Try and report! :)
Greetings,
sevi
#3
Well color me impressed! Thanks a bundle. I'll check it out and give some feedback directly.
#4
Awesome! This could be very useful...
#5
I committed big chances concerning the book handler to cvs.
Now all book-pages can be used as the root of the tree in the view.
The intelligent book handler lets the root node in the view think that it is the book-root node (without changing values in the database). So all not-shown hierarchy levels above will not have to be changed if the root node in the view changes.
..just to be mentioned for DraggableBooks developers: Me :)
Greetings,
sevi
#6
I tried out the original commit last night and it works as advertised. This is really a huge leap in usability for books. For the site I was working on I ended up using the native handler, but I'll be using this in the future. I was just wondering if you coded that in response to my asking, in which case I feel kind of rough as I'm not at present able to justify funds as I was in July. Nonetheless, I am extremely thankful. If that means anything!
#7
You just gave me a hint of what can be useful. Well, and i found it very, very useful :)
First I thought it's too complicated to work with the menu system, but then I did it though.
I'll close this issue now. Documentation for this Book handler will follow.
Greetings,
sevi