I agree with you there on droppablecontext!!! We would have saved 20 emails and 20 hours! The draggable is a component and it's easy for my novice eyes to see it's @Parameter.
The droppable though is a mixin for a Zone. I thought about trying to add my own droppable context, but at this stage it's in the too hard basket - given I'd also have to screw around with the AJAX-y part. I did however get my old custom jquery code to work with standard @ImportJQueryUI stuff. The previous week I was doing it this way but had a problem because jquery.ui.mouse was not in the import statement and then was in the wrong order - which led me to the template based way of doing it because there was no drag-age or drop-age :( - but this is working now :) Going back has helped me do my things the way I had sussed out last year with jquery. At least the steps for going down my own AJAX component seem easier going by the "look at the auto complete component source code" as suggested at the bottom of this page - https://tapestry.apache.org/ajax-and-zones.html I can do that I think. I took the afternoon to fix some real world things around the joint :) The most of the examples from jqueryui.com I tested work @ImportJQueryUI with custom js - i.e. effects, accordion, dragndrop On 14/04/2012, at 6:06 PM, Lance Java wrote: > If the URL is the same then the zone id is the same. Im guessing that your > droppables are defined in a loop too? (I'm talking t:id not client id) > > I think that the droppable mixin needs to accept a droppablecontext in a > similar way to draggablecontext and the serverside event should have both > contexts passed to it > > My 2p --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org For additional commands, e-mail: users-h...@tapestry.apache.org
