Sorry, maybe I do not fully understand what you want to do but why won't you
update the state of the server once a div is dropped.
I have my own components that use drag and drop (e.g. tables with
draggable/dropable columns) and what I do at the JavaScript side is
something like:
XXX.onDrop() {
var url = this.url+ '&sourceId=' + parseInt(td.style.width) +
'&targetId=resize' + '&number=' + this.number
wicketAjaxGet(url);
}
and this URL is the URL to certain AjaxBehaviour on the server. Then I just
read those parameters on the server side, so that UI is in synchrony the
server.
Just take a look at YUI and Scriptaculous integration projects for
inspiration.
Best,
Ernesto
On Fri, Oct 17, 2008 at 11:28 AM, Neil McT <[EMAIL PROTECTED]>wrote:
>
> Ok, so I had a look at the Palette component. Its very nice, but I don't
> think it really helps me as it uses a select box (i.e. a pre-existing
> wicket
> component) as a 'bin' for the droppables. This really abstracts out the
> main
> part of my problem - how to bind and manipulate a bunch of divs with a
> custom component.
>
> To explain further: what I will end up with is a droppable 'bin' (a div)
> which the user has been happily dragging stuff (other divs) onto - and
> possibly sorting etc. The hole in my knowledge here is how to associate
> these inner divs (the things that have been dropped) with some Wicket
> component on the server side. I can associated the 'bin' div with a
> MarkupContainer or something but I'm not sure how to dynamically keep track
> of its inner divs once the user has submitted.
>
> I've tried a solution using a ListView nested within a form but I'm not
> entirely happy with it. For example, the number of 'slots' to drag things
> onto has to be known at construction time - i.e. the user can not drag on
> 11
> things if only 10 slots (say, nested textfields) have been created at
> construction time (also I would prefer not to have pre-determined 'slots' -
> just an area onto which many divs can be dragged). I would like to use
> Jquery to do all the fancy front-end stuff (creating new 'slots' on the
> fly,
> sorting etc) and just bind the results (all the dragged-on divs) to some
> component in Wicket.
>
> I've been playing about with wicket for about a month and this question
> actually reflects an area of the Framework that I am not really getting so
> far - how markup is bound to components at the lower level. I've read many
> examples and the excellent Wicket in Action book but, understandably, they
> seem to focus on how to use existing components and only briefly touch on
> how to create your own components and how to really 'get at' the underlying
> markup.
>
> Any help, hints or pointers to further reading would be much appreciated
> as,
> my current problem aside, I feel this is an area I need to crack before I
> go
> any further.
>
> Thanks - Neil.
>
>
>
> Serkan Camurcuoglu wrote:
> >
> > it seems like you're talking about the DnD version of the Palette
> > component in wicket extensions.. See its source code, maybe it will give
> > you some idea..
> >
>
> --
> View this message in context:
> http://www.nabble.com/DHTML-DnD-best-practice--tp20010633p20029961.html
> Sent from the Wicket - User mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>