[Seaside] Another refactoring question : Where to put the 'view' or
'edit' logic for data classes?
rickf at ca-flower.com
Sat Aug 21 04:31:57 UTC 2010
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?
More information about the seaside