[Seaside] Another refactoring question : Where to put the 'view' or 'edit' logic for data classes?

Sean Allen sean at monkeysnatchbanana.com
Sat Aug 21 14:07:16 UTC 2010

I normally do something like this:

I have different components for different types of html controls. Text
fields, radios etc.
These are then combined into composite components that contain any
model specific
knowledge that is needed.

On Sat, Aug 21, 2010 at 12:31 AM, Rick Flower <rickf at ca-flower.com> wrote:
> Hi all..
> Still working on the refactoring.  For those of you that have Seaside based
> apps, where do you keep the view/edit logic for each data class/object that
> will be viewed or edited by a user?  I was thinking of just putting some
> sort of logic directly in each data class but if I need to do both a view
> and edit operation that limits the flexibility without extra logic..
> Should I just go for separate classes that each do either a view or edit
> function for each needed data class?  Or are there better suggestions out
> there?
> Thx!
> -- Rick
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

More information about the seaside mailing list