I'm not so sure about pluggable component means but sounds like composition to
me. If so, its pluggability most surely will be affected by state anyway.
An interesting question you can make on this is "state of what" will decide
things.
You can make the application model state to decide that or the domain model to
decide that. Both should be evaluated.
cheers,
Sebastian
> -----Mensaje original-----
> De:
[hidden email]
> [mailto:
[hidden email]] En nombre
> de Bill Schwab
> Enviado el: Jueves, 10 de Julio de 2008 09:06
> Para:
[hidden email]
> Asunto: [Seaside] Design question
>
> Sebastian,
>
> That sounds like an answer. Alternatives would include emphasizing
> pluggable components vs. state-dependent ones. There is probably an
> inheritance vs. composition argument in there too. All that aside, it
> seems like a useful trick in this case, and the whole thing can be
> rewritten some day when I have a better grasp of the framework.
>
> Thanks,
>
> Bill
>
>
>
>
>
> Sebastian Sastre ssastre at seaswork.com wrote:
>
> Hi Bill,
>
> I didn't get your example but I don't see why rendering
> subcomponents
> conditioned to model state could be a problem. Do you?
>
> cheers,
>
> Sebastian
>
>
>
> Wilhelm K. Schwab, Ph.D.
> University of Florida
> Department of Anesthesiology
> PO Box 100254
> Gainesville, FL 32610-0254
>
> Email:
[hidden email]
> Tel: (352) 846-1285
> FAX: (352) 392-7029
>
> _______________________________________________
> seaside mailing list
>
[hidden email]
>
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
Locked
