[Seaside] #children problems

[Joseph Blatter]

I'd need my controls to be components because I want
to attach a custom css style to each control. I've
tested your suggestion but I've seen the renderer take
the style from the childrens
(WARenderer>>buildDocRoot), making impossible to get
my custom styles ever called.

So it's still possible to get the #style called being
a control not a children of the page?
thanks


 --- Avi Bryant <avi.bryant at gmail.com> escribió:

> 
> On Oct 18, 2006, at 8:43 AM, Joseph Blatter wrote:
> 
> >
> > Can I configure callbacks in a subcomponent of a
> page
> > (component) without sending #children?
> >
> > My problem is that I have a page with too many
> > subcomponents (controls like ListBox's,
> TextField's,
> > etc) and I've seen in order to set a callback I
> must
> > implement #children in the page (component)
> answering
> > these controls already created. I don't see
> another
> > solution to this problem other than adding all the
> > controls as instance variables which is a solution
> not
> > elegant/convenient/feasible for me.
> 
> Are you sure they need to be components?  Anything
> can implement  
> #renderOn:, but only subclasses of WAComponent need
> to appear in  
> #children.  If you don't need the various methods
> and hooks  
> WAComponent provides (like #call:, #updateRoot:,
> #updateUrl:), then  
> your controls can be simple subclasses of Object
> instead.
> 
> Avi
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
>
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
> 


__________________________________________________
Correo Yahoo!
Espacio para todos tus mensajes, antivirus y antispam ¡gratis! 
Regístrate ya - http://correo.espanol.yahoo.com/