best proceed classify php category hierarchy


i've got rather obsolete horizon i've controlling many projects, nonetheless whole settlement emanate came mind i haven't means work out yet. given application, should i removed application-specific category structure framework's structure, building tip horizon such bad thing?



for example, contend i horizon bottom controller category extended given biased application. arrangement creates many sense, why?



class structure a:




  • intuitive, easy source files debugging.

  • file naming/directory structure mirrors category heirarchy.




- framework_control "framework\control.php"
- framework_control_index "framework\control\index.php"
- framework_control_home "framework\control\home.php"
- framework_control_contact "framework\control\contact.php"
- framework_control_about "framework\control\about.php"


class structure b:




  • keeps horizon modular simply replace/update.

  • adds complexity office structure, directory/file controlling longer follows category heirarchy time.




- framework_control "framework\control.php"
- application_control_index "application\control\index.php"
- application_control_home "application\control\home.php"
- application_control_contact "application\control\contact.php"
- application_control_about "application\control\about.php"


i know altogether it's going down personal preference, nonetheless i wish certain i import out pros cons before i endorse proceed go. unequivocally comes down category controlling office structure tangible hierarchy sojourn same presumably case.



Comments

Popular posts from this blog

list macos calm editors formula editors

how hibernate @any-related annotations?

why does floated <input> control floated component slip over too distant right ie7, nonetheless firefox?