project based pier

[Nick Ager]

>
> > Solution (2) mixes model and view.
>
> I don't see why this mixes model and view?
>
> - Model: PRStructure and subclasses + some external code
> - Controller: PRCommand and subclasses + some external code
> - View: PRViewComponent and subclasses + some external code (Seaside
> mostly)
>
> In you case you would just add your own model classes to your own
> PRStructure subclasses that somehow interoperate with your model.


Thanks for the clarification. If I've understood correctly, the best way to
go is to subclass PRStructure for my model classes so that the model objects
can be used directly by Pier, otherwise I'd end up having a duplicate Pier
structure mirroring my model objects. The disadvantage of this is that the
framework infects my classes; using Java terminology they are no longer
POJOs [1], or have I missed something?

Would the combined approach, I attempted to outline in the previous message
be overly complex to implement? I can image that splitting the url handling,
and model between two structures could require lots of patching before
they interoperate successfully.


[1] http://en.wikipedia.org/wiki/Plain_Old_Java_Object
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.iam.unibe.ch/pipermail/smallwiki/attachments/20100118/b6dcd03e/attachment.html>