Explore >> Select a destination
|
You are here 
|
codefol.io | ||
| | | | |
www.integralist.co.uk
|
|
| | | | | Introduction Model View Controller Mixed definitions God Controller Problems Skinny Controller Presenters? What problem are Presenters trying to solve? How do they work? Code Example Controller View Presenter Conclusion Introduction Model, View, Controller (MVC). This is a pretty standard architectural pattern and has been in use when developing software since the early 1970's. The basic principle of the pattern is to separate the different areas of logic from your application into distinct compartments. | |
| | | | |
konradreiche.com
|
|
| | | | | Ruby on Rails applications are modelled around active record yet what if your application is based on a domain which needs to be provided in a programmatic way? In other words, your application, controller and views stand on a fixed set of Ruby classes yielding the context. In a manual fashion one would implement this by creating controller and views for each specific class. Assuming that the classes of this domain share the same interface this approach would introduce a lot of redundancy. With meta-programming this amount can be cut down. | |
| | | | |
postmodern.github.io
|
|
| | | | | ||
| | | | |
akashgoswami.dev
|
|
| | | How I've setup and installed PostgreSQL on my Macbook | ||
