Welcome Guest, Not a member yet? Register   Sign In
Is this ideal CodeIgniter DRY App Architecting?
#1

[eluser]Unknown[/eluser]
Noob. I have a pretty good handle on using models to make database calls and handing the data off to...
I understand views and ideal usage. My general thoughts are to create the following for each section (for the most part):

PEOPLE
- controller
- model
- view(s) add/edit/etc
- library (specific logic and output)

then when I want to access people related data; Say from my BORROWER controller I'll call the people library function and load the appropriate people view into the BORROWER controller and into its view. AND, same naturally for PEOPLE logic. DRY.

Is this ideal?




Theme © iAndrew 2016 - Forum software by © MyBB