Skip to Content
Last modified by Klaus Berkling on 2011/09/06 00:31
From version 46.1
edited by arroz
on 2007/12/16 21:57
Change comment: There is no comment for this version
To version 48.1
edited by arroz
on 2007/12/16 21:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -78,5 +78,3 @@
78 78  Done. Now you're project is linking with your framework. If you think this is overkill, think again when you need to do a maintenance application of a backoffice. You'll love the time you spent separating the model code from the application. Also, this helps you write better code, because model code shouldn't need to know anything about the presentation layer. If you try to do that in your framework, you'll get an error, so you really can't do it! :)
79 79  
80 80  If you don't want to create the model framework now, at least take the advice of keeping the model layer fully independent from the presentation layer. This will make it easier if you decide, in the future, to separate the model code to a framework as described here.
81 -
82 -[[« Previous: Overview>>Best Practices-Overview]] [[Next: Model>>Best Practices-Model »]]