Hi, there is now a dropzone.module in my sandbox http://cvs.drupal.org/viewvc.py/drupal/contributions/sandbox/chx It provides a block where you can add "stuff" and then there can be certain things you can do with it (the "stuff" is persisted in session). I have implemented menu reparenting as an example. The idea behind this is that you already have various navigation tools in your site and such an admin block lets you use all those to find the item you want to admin and, in this case, the parent as well. Another fine example could be comment mover. Taxonomy terms parenting. And so on. As the name suggests drag-and-drop would be a welcome addition to this module. I am really curious what people think about it. Note: it's very alpha. Using it on a production site will destroy said site. Regards, NK
I guess an example won't hurt.... So, let's say you want to move menu item foo under menu item bar. So, you first put "foo" into the dropzone. Second, you go to "bar". Third, you press the button.
Sounds very cool! Can we see some screenshots and/or a demo/screencast? Bevan/ -- Drupal.geek.nz | Gtalk bevan@lucion.co.nz | YIM rudgy_m_nz | .Mac/AOL b.rudge | skype b.rudge | Twitter.com/BevanR
Interesting. I tried this out. I really like the whole idea of collecting things in a block to have some sort of access to on an unrelated page. I noticed how you can use this to move menu items about, I'm just unsure why it would be more useful then the current drag-and-drop system in /admin/build/menu. I tried this out by installing, enabling the Dropzone block on the right, going to /admin/build/, clicked the "Menu item Site building in navigation" radio that appears in the Dropzone, and clicked "Add". I then went to /admin/settings and clicked the button "Move below current item in navigation" and it was succesfully moved. Now you could get to /admin/build from within admin/settings. Then I tried moving it back and the order was out of whack, so that when I go to /admin, instead of seeing the "Site Building" on the right hand column, "Site configuration" is the first item on the right instead. I cannot see any use for the "Path .." radio button. If someone were to build a drag-and-drop interface for this, what sort of items would you be limited to using? If it was pretty much anything, images, node areas, or whatever... and the module gave you a block to keep multiple items, or a 'collection' of things, I could see a better use for this module. I'm wondering what you envision this module better enabling someone to do? ~Jerad On Jan 20, 2008 4:47 PM, Bevan Rudge <bevan@lucion.co.nz> wrote:
Sounds very cool! Can we see some screenshots and/or a demo/screencast?
Bevan/
-- Drupal.geek.nz | Gtalk bevan@lucion.co.nz | YIM rudgy_m_nz | .Mac/AOL b.rudge | skype b.rudge | Twitter.com/BevanR
Interesting. I tried this out. I really like the whole idea of collecting things in a block to have some sort of access to on an unrelated page. I noticed how you can use this to move menu items about, I'm just unsure why it would be more useful then the current drag-and-drop system in /admin/build/menu.
Try the current system with a couple (hundreds of) thousands menu items and you will see :D
I cannot see any use for the "Path .." radio button.
Because I have not coded any other button in there :) though I might.
I'm wondering what you envision this module better enabling someone to do?
Any time when you need to administer things which are one in a huge lot, it's very useful. Administer path aliases when you have a million of them. Create node references. Etc. About collections, that's a different usage than what I envision here. Screencast ... I could create one, sure.
Interesting. I tried this out. I really like the whole idea of collecting things in a block to have some sort of access to on an unrelated page. I noticed how you can use this to move menu items about, I'm just unsure why it would be more useful then the current drag-and-drop system in /admin/build/menu.
Try the current system with a couple (hundreds of) thousands menu items and you will see :D
I cannot see any use for the "Path .." radio button.
Because I have not coded any other button in there :) though I might.
I'm wondering what you envision this module better enabling someone to do?
Any time when you need to administer things which are one in a huge lot, it's very useful. Administer path aliases when you have a million of them. Create node references. Etc. About collections, that's a different usage than what I envision here. Screencast ... I could create one, sure.
On Jan 20, 2008, at 2:14 PM, Jerad Bitner wrote:
I'm wondering what you envision this module better enabling someone to do?
Some possibilities for d.o: - Reclassifying a bunch of issues into another project's queue. (drag a bunch of issues into the block, then navigate to the project node you care about, then press the button) - Reclassifying project nodes into the module categories. - Reorganizing books. - Bulk operations on release nodes? - As chx already said: comment mover. Other ideas: - As catch said: manipulating node queues. (excellent!) - Populating panes in a panel (when you don't want or need the nodequeue/views combo). - shopping cart? Sounds great, chx. I hope to have a chance to play with it sometime soon. Hopefully someday it'll be ready for prime time on d.o. ;) Cheers, -Derek (dww)
In zope [1] management interface [2], there is similar functionality. It works like a clipboard. You can cut/copy items to it, and paste them somewhere else. A clipboard metaphor might be a good idea ? Philippe [1] http://www.zope.org [2] http://www.zope.org/Resources/ZopeIntro/index_html/screenshot1_640.jpg ps : I'm from the few who think a lot can be learn from 1990's zope interface :-) On Jan 20, 2008 9:36 PM, Karoly Negyesi <karoly@negyesi.net> wrote:
I guess an example won't hurt....
So, let's say you want to move menu item foo under menu item bar.
So, you first put "foo" into the dropzone.
Second, you go to "bar".
Third, you press the button.
There is a somewhat similar project that is based around administering nodes which has some drag-n-drop functionality you might wanna check out. http://drupal.org/project/nodestack On Jan 21, 2008 2:58 AM, Philippe Jadin <philippe.jadin@gmail.com> wrote:
In zope [1] management interface [2], there is similar functionality. It works like a clipboard. You can cut/copy items to it, and paste them somewhere else.
A clipboard metaphor might be a good idea ?
Philippe
[1] http://www.zope.org [2] http://www.zope.org/Resources/ZopeIntro/index_html/screenshot1_640.jpg
ps : I'm from the few who think a lot can be learn from 1990's zope interface :-)
On Jan 20, 2008 9:36 PM, Karoly Negyesi <karoly@negyesi.net> wrote:
I guess an example won't hurt....
So, let's say you want to move menu item foo under menu item bar.
So, you first put "foo" into the dropzone.
Second, you go to "bar".
Third, you press the button.
Karoly Negyesi wrote:
Hi,
there is now a dropzone.module in my sandbox http://cvs.drupal.org/viewvc.py/drupal/contributions/sandbox/chx
It provides a block where you can add "stuff" and then there can be certain things you can do with it (the "stuff" is persisted in session). I have implemented menu reparenting as an example. The idea behind this is that you already have various navigation tools in your site and such an admin block lets you use all those to find the item you want to admin and, in this case, the parent as well. Another fine example could be comment mover. Taxonomy terms parenting. And so on.
As the name suggests drag-and-drop would be a welcome addition to this module.
I am really curious what people think about it. Note: it's very alpha. Using it on a production site will destroy said site.
Regards,
NK
When all the drag and drop patches were going in, I immediately thought of something like this as the natural next step for it - to handle dragging across multiple pages and the rest. At the moment the only way to do drastic changes to the weight of a taxonomy term in a large vocabulary, is to use the 'weight' field from the edit term form, a bit less exciting - it'd be great to eliminate that form element completely in D7 and this seems like an ideal way to do it. Amazing to see it at least partially coded already. For collections, that's already dealt with well by nodequeue module (for nodes, anyway), if nodes were supported as a type, then it doesn't seem like a big step to then support adding to and removing from nodequeues via the same ui.
participants (6)
-
Bevan Rudge -
catch -
Derek Wright -
Jerad Bitner -
Karoly Negyesi -
Philippe Jadin