[Seaside] Grid of components
Sebastian Sastre
ssastre at seaswork.com
Wed Oct 3 12:15:49 UTC 2007
I'm using a presenter superclass that answers #children for all it's
subclasses. The subclasses has to have some method (#initialize for
instance) in which you add children to the component in a way it can answer
them. I'm making like this ala Dolphin:
SomePresenter>>createComponents
super createComponents.
self
at: #date put: MVPDatePresenter new;
at: #subject put: MVPInputTextPresenter new;
at: #budget put: MVPBudgetPresenter new;
yourself
the superclass MVPPresenter is the only one that implements
#children and it's trivial:
MVPPresenter>>children
^ self components values
#components is a dictionary in an instVar at that MVPPresenter
may this give you ideas,
Sebastian Sastre
> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre
> de Keith Hodges
> Enviado el: Miércoles, 03 de Octubre de 2007 05:42
> Para: sea >> "The Squeak Enterprise Aubergines Server -
> general discussion."
> Asunto: [Seaside] Grid of components
>
> If I have a grid component which is formed of subcomponents
> this could be a lot of components it seems that it is
> necessary to return #children for subcomponents
>
> Does this mean building up and keeping an array of perhaps
> several hundred components in children or is there another/better way?
>
> Keith
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
More information about the Seaside
mailing list