[Seaside] Brush or Component?
ssastre at seaswork.com
Wed Jan 30 17:07:24 UTC 2008
Thanks for sharing. I can tell that I'm as much component centric for web
elements as object centric for smalltalk,
> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> de Esteban A. Maringolo
> Enviado el: Miércoles, 30 de Enero de 2008 15:00
> Para: Seaside - general discussion
> Asunto: Re: [Seaside] Brush or Component?
> By now, the brush approach is fine. I subclassed WACompound
> and it's working.
> But if I want to add event handlers (onChange/onClick/etc.),
> I can't do it, because it's only defined in WATagBrush.
> My compound has only one element, and fits better to be a
> compound than a tag (which in fact it isn't).
> I can add the required handlers to be passed to one of the
> compound children, or even make a common superclass for all
> the brushes sharing this behavior and structure, but I'm
> sharing this here, to know if somebody had the same situation
> or found a better solution.
> Best regards,
> Esteban A. Maringolo
> eMaringolo at gmail.com
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside