#18: Prototype -------------------------+-------------------------------------------------- Reporter: david | Owner: chris Type: task | Status: accepted Priority: medium | Milestone: Construction Phase 1 Component: Project | Keywords: Prototype with usable GUI, implementing 30% of use cases Blocks: | Dependencies: Due_assign: 2009/02/27 | Due_close: 2009/03/18 Complete: 0 | -------------------------+-------------------------------------------------- Changes (by chris): * cc: chris (removed) Comment: I'm not sure I understand what you're asking, but... CodeIgniter has it's own structure, the key folders to know are: vths\system\application\views vths\system\application\controllers vths\system\application\models The folder names are fairly self-explanatory: they relate to the MVC architecture within the views folder, individual components related to each view are stored in folders, with the main view file and shared files in the main directory. For example: vths\system\application\views\header.php vths\system\application\views\footer.php vths\system\application\views\login.php vths\system\application\views\login\loginform.php vths\system\application\views\login\loginerror.php Additional resources are: vths\css - stylesheets vths\images - all the images used, shamelessly stolen from the existing site I've now got a frontpage up on the prototype, which hopefully should serve as a decent example of how the system will work with regards to assembling views out of "jigsaw pieces" and what should go in a view and what gets separated out into parts of the system. You may also want to look at the different controllers to see what is going on there and how the logic controls what views are loaded. (took myself off the CC list as I get the updates via the mailing list) -- Ticket URL: <www.redweasel.co.uk/projects/co2015/ticket/18#comment:8> co2015 <http://www.redweasel.co.uk/projects/co2015/> co2015 group project