[Seaside] Re: Component granularity & numbers
Yanni Chiu
yanni at rogers.com
Sat Jan 5 06:39:13 UTC 2008
itsme213 wrote:
> Is it reasonable to have one component for every appearance of any domain
> model object on the page (could be hundreds, many of them being presented
> just as very summarized names without their details) plus one component for
> every control (menu etc.)?
It depends on your model. If "domain model object" means an application
UI model that interacts with an underlying business model, then the
answer is yes. If the model objects are the underlying business objects
themselves, then the answer is maybe. It'll work well if your UI is
mostly CRUD-like (i.e. create/retrieve/update/delete). The approach will
start to break down when the underlying business objects have more
specialized behaviour. You'll know you've reached the tipping point when
you have to keep extending your generic framework code to accomodate
your business model. Hope that helps.
--
Yanni Chiu
More information about the seaside
mailing list