Hey,

Really like the look of this. :) Good work.

At the moment, you can drag children out from there parents, and move
them up a level. But you can't drag nodes into other nodes as children,
unless it already has children. If that makes sense. 

Example: I can make 3-2 a child of 1-2, by dropping it just above 1-2-1.
But I can't make 3-2 a child of 'option 4'.

For a tree - not only do you need droppable areas in-between each node,
but also ON each node. Say, when i drag over 'option 4', its background
color could change, and when I drop, the dropped node will then become a
child of 'option 4'.

Basically, being able to do what this backbase example does - along with
the reordering you've already come up with:
http://www.backbase.com/demos/explorer/#examples/drag-treelist.xml[5]

What do you think? Would something like this be fairly easy to do with
the way it has been built?

I'll have a play with the code over the next few days because this would
be really useful to me. I'll let you know how I get on.

Regards,
James

On Mon, 2006-10-23 at 22:44 +0300, Stefan Petre wrote:
> Hi there,
> 
> Me and Paul are thinking to change the way sortables are working right 
> now. So I had an idea that turned to be quite nice because of 2 reasons:
> - works faster
> - you can sort nested list
> 
> But also has some drawbacks: you ca not have fancy affects.
> 
> Please take a look at this draft 
> http://interface.eyecon.ro/demos/test_sort.html and tell me if this kind 
> of behavior on sortables fits you and if it is working on Safari or 
> Linux environment. I tested on Windows, IE6, FF 1.5 and OP9
> 
> Check out the code. Simple and easy to implement. It is so easy to love 
> jQuery.
> 
> 
> _______________________________________________
> jQuery mailing list
> [email protected]
> http://jquery.com/discuss/

_______________________________________________
jQuery mailing list
[email protected]
http://jquery.com/discuss/

Reply via email to