[Seaside] Re: Scripaculous toggle

[Esteban Lorenzano]

On Jan 4, 2008 3:38 PM, Esteban A. Maringolo <emaringolo at gmail.com> wrote:

> Answering myself:
>
> On Jan 4, 2008 2:23 PM, Esteban A. Maringolo <emaringolo at gmail.com> wrote:
> > Two questions:
> > 1) What is the way to have 2 SU actions in the onClick event?
> > One being the toggle, an other a XHR callback to the component,
> > notifying about the new layout.
>
> This is pending... yet.
>

Mmm, I'm using "comma", like this:

html anchor
onClick:
(html element id: detailtId; toggle) ,
(html updater id: detailtId;
callback: [:render |
render render: (childs add: (self post asShow part: self) )]),
(html updater id: titleId;
callback: [:render|
self updateMarks.
self renderTitleOn: render ]);
with: self post name.

It's not the best solution, i think (component is updated even when
hidding), but works... :)

>
> > 2) How to set the hidden/visible status of the "toggled" element
> > during the render, but leaving it enabled for a future toggle.
>
> I've had to inline the 'display: none' style of the affected element.
>
>
> ps: I can't write Scriptaculous name right two times in a row. :-) (see
> subject)
>
> --
> Esteban A. Maringolo
> eMaringolo at gmail.com
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>



-- 
"Querer es suscitar las paradojas"
Camus. El míto de Sísifo.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20080104/f1f09deb/attachment.htm