[Seaside] Re: Draggable problems

Lukas Renggli renggli at gmail.com
Sat Dec 8 19:13:16 UTC 2007

> Would it make sense in this case for #passenger to check pre-existing #id,
> and call a new method like:
> WARenderingContext>>storePassenger:atId:
> storePassenger: anObject at: anId
>     (callbacks includesKey: anId) ifTrue: [self error].
>     callbacks at: anId put: anObject
>     ^ anId

No, script.aculo.us needs to have the drag & drop IDs to have a
special form. It is not possible to use your own ID.

> > 1. Wrap your DOM element with your own ID into one where Seaside is
> > able to choose its own ID.
> It seems that might work, though I usually prefer not to do too much such
> wrapping.

Me too.

> > 2. Avoid using an ID (in my opinion this is not a good practice
> > anyway). Use a class instead.
> I would if this was for CSS styling, but it is for direct Ajax editing of
> specific elements among multiple similar css-classed ones.

Assign the passenger first and then use this ID to enable Ajax editing.


Lukas Renggli

More information about the seaside mailing list