Conventional wisdom cautions against mixing view and model related code. It seems that the examples I dig into have all the code in the Morph.
- What has been your experience in understandability/testability writing them this way? - Is it just because they are examples? Or would you write production code that way too? - If you had a separate model and view, how would they communicate? Is there something like a change/update or announcements framework? Thanks, Sean ----- Cheers, Sean -- View this message in context: http://forum.world.st/View-Model-Separation-tp4742027.html Sent from the Lively Kernel mailing list archive at Nabble.com. _______________________________________________ lively-kernel mailing list [email protected] http://lists.hpi.uni-potsdam.de/listinfo/lively-kernel
