[eluser]Peng Kong[/eluser]
ok let's talk about the package file structure today.
in root folder
/css - put css style sheets .css
/img - put your images .jpg, .gif, etc
/js - put your javascripts .js
/uploads - user uploaded files (profile pic, etc)
/system - CORE FILES - DO NOT TOUCH - let CI/ellislab/opensourcecommunity maintain this
/system/cache - has 3 folders to cache the stuff openid needs
/system/logs - you can clear your cache here
/system/application - all our stuff goes here
/system/application/controllers
/system/application/models
/system/application/views - im not really using these as i've used HMVC by wiredesignz therefore a3m is located at
/system/application/library
Controller, Modules and MY_Router is necessary for HMVC to work
MY_Session is a modification i made to allow us to do "remmeber me" and KeepAllSessionFlashData.
/system/application/module/account <-- this is where all the a3m files are kept.
account/controller <-- the naming should be obvious. Each controller should roughly map to one page which the user sees taking care of requests to that page
account/helper <-- ssl_helper is something i created to help us create https a3m systems
account/language <-- all text in views come from language files the naming should be obvious which views use which language files.
account/models <-- models -.- don't need i think explain that
account/library <-- things which you should load from your main application.
a3m should remain in the hmvc module folder... you should code your main application in the /application folder. you should called the a3m libraries by doing a $this->load->library('account/authentication'); look at the /application/controller/home.php file and see how i loaded the a3m authentication and user library
account/plugins <-- external libraries are stored in the 'library' folder in the plugins folder. plugins are used to load the external libraries. DO NOT hack external libraries let their respective open source community manage them. if you hack it report to the respective community so it gets updated in the next version and you can replace the whole library.
account/views <-- your xhtml + css. follows yahoo best practice. css loaded in header. js loaded at the end of body tag. using gs960 grid (which you of cuz can throw away) and use something else.
