Library Vs Model

[eluser]Peng Kong[/eluser]
here's the way i see it.

models do all the database talking (data in and out)... no one else does it.

view contain all the presentation (html, css, js)... no where else contains it.

i think this way of looking at models are views are pretty similar from developer to developer.

controllers functions 'map' to one or more views.
They determines which view to show based on "your logic" which determines on the flow.

"your logic" that is specific to that controller's function stays in the controller.
"your logic" that is 'across the board' (aka reusable) goes into libraries, helpers and plugins.

Libraries, as mentioned, contains "your logic" which is reusable to many parts of your application. Libraries can make use of helpers and plugins.

Helpers are just simple, useful, reusable, standalone functions.

Plugins are many related functions and help achieve a common purpose. They are strictly standalone (no dependency). Plugins have a clearly defined interface for you to call anywhere in "your logic".

---

However, i'm finding that even after doing all that, you will get to a stage where complex applications have too many views, models and controllers.

Things start to get messy and you ask yourself, "How do i group up related views, models and controllers into folders... rather then just ONE folder for ALL the views, ONE folder for ALL the models and ONE folder for ALL the controllers".

There's where Modular Extensions by Wiredesignz comes into play.

After using Modular Extensions, i prefer to put more module logic into controllers and application logic into libraries (for other modules to use).

maybe i don't know better but i feel this is a flexible D.R.Y. approach.