php - CodeIgniter CRUD structure -


i'm using codeigniter flesh out pretty large project (especially n00b). 1 issue i'm having how organise files , methods. i've broken project down features - app task management software have basic features such "task", "project", "user" etc.

the way intend creating controllers each , following crud methodology in each. example in task have following methods:

create() read() update() delete() 

this makes sense in head. in terms of views, should have multiple views, or should combine create , update same form? also, non-view functionality go, such setting cookies etc?

this quite specific question if has more holistic guides on general structure convention codeigniter projects i'd grateful.

i'd got right. do.

i tend use same view create , update, keep dry (don't repeat yourself) if can.

non-view related stuff not handle business-related goes in call helper-classes. if it's business related, put logic services, can unit-test them without being dependant of framework (not sure how new @ this, oh :) ).


Comments

Popular posts from this blog

How to remove text and logo OR add Overflow on Android ActionBar using AppCompat on API 8? -

html - How to style widget with post count different than without post count -

url rewriting - How to redirect a http POST with urlrewritefilter -