[Seaside] Re: Scriptaculous problem

[Sebastian Sastre]

Because that makes me unable to recall the id of the components at nay time
to wire events between them among other uses.

	regards,

Sebastian Sastre

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Lukas Renggli
> Enviado el: Miércoles, 26 de Septiembre de 2007 13:35
> Para: Seaside - general discussion
> Asunto: Re: [Seaside] Re: Scriptaculous problem
> 
> > All $().fooBar is not a function is js unable to create the element 
> > object for some reason. I also remember happening that to me, and I 
> > solved that using a whole hierarchy of WAComponent 
> subclasses that has 
> > an instVar #id that is guaranteed to be unique (get from a class 
> > variable #Counter in the abstract superclass) per element 
> per page and is set at #initialize time.
> 
> Why not use
> 
>      html nextId
> 
> to generate an unique id?
> 
> Lukas
> 
> --
> Lukas Renggli
> http://www.lukas-renggli.ch
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside