I guess it could potentially be used for any drag and drop interface? It's such a different way to think of the problem, I'm going to have to try it for something just to wrap my head around it.
Well, that was 8 hours ago - you get anywhere noodling over this?
I'm trying to go through the same thought process - this is neat, how do i translate into more practical applications. It seems like such a powerful paradigm if one can figure out that mapping.
The interesting thing is that drag and drop interfaces are not typically purely directly mapping the drag operation to moving the object selected. There's a lot more going on -- there's hover and activation effects, limits, often animation.
This approach gets rid of the annoying leg work of mapping pointer movement to changes, but I'm not sure how to fit the rest of drag drop UI into it (I do see examples of limits in the doc).
I think it's going to have to be something in the back of my head for awhile, and when I see interesting dragdrop experiences I'll think about how it could be achieved with this approach.
