Remerciez-le!

Remerciez @Admin pour avoir partagé cet document gratuitement, de la manière la plus simple, en partageant sur les réseaux sociaux.

Developer guide 4 A Project - GIT Repository - https git code sf net p phpscheduleit source - To contribute and submit your code please contact Nick Korbel nick twinkletoessoftware com - Programming paradigm toward object oriented PHP - Please include the

A Project - GIT Repository - https git code sf net p phpscheduleit source - To contribute and submit your code please contact Nick Korbel nick twinkletoessoftware com - Programming paradigm toward object oriented PHP - Please include the GPL header on every new source ?le with your name and year If you are altering an existing ?le just add your name and year B Requirements - Web server Apache IIS - PHP or greater - MySQL or greater C Getting the development branch running Set con ?guration values Update con ?g con ?g php with your local settings If you have phing and are on Windows Run build bat setup db If you do not have phing Create the database and user run databaseschema create- db sql run databaseschema create-user sql Open http localhost booked Web install D Development branch technical information Application structure con ?g Application con ?guration Controls All reusable page control objects database schema Base and upgrade sql scripts Domain Domain speci ?c entities repositories services etc Access Domain repository objects db abstraction layer Events Domain events Values Value objects Jobs All tasks that run on a schedule cron tasks for example lang Translations lib All application supporting objects Application Most of the subdirectories are self- explanatory Admin Application administration logic Attributes Custom attributes Authentication Authentication login Authorization Authorization access Reporting Logic for generating and running reports Reservation Noti ?cation Post-reservation logic Persistence Creating updating deleting reservation information Validation Pre-reservation logic Schedule Schedule population User Common Non-speci ?c shared objects localization dates smarty etc Con ?g Con ?guration read write CAPI Database Database access and abstractions Email Email abstractions and services external Third party libraries FileSystem Filesystem I O object Graphics Creating and manipulating images Server Web server abstractions sessions cookies etc WebService Objects for creating and invoking web services the Pages phing-tasks plugins Presenters tests tpl tpl c uploads Web scripts WebServices Page binding and work ow logic Custom build tasks that hook into phing Contains subdirectories for each type of plugin Application logic page population All unit tests All Smarty page and control templates Default Smarty template cache directory Default ?le upload directory All user facing pages All application related javascript ?les The Booked API Design philosophy The Model-View-Presenter MVP pattern is used to keep a clear separation between application logic and presentation logic Page objects act as thin abstraction to the template engine and typically have no other logic Presenter objects orchestrate interactions between underlying application logic objects and the page This typically includes fetching and transforming data and minimal application logic page php should - de ?ne ROOT DIR - include Pages page Page php - construct page Page and call PageLoad Each page should have at least one corresponding template in tpl Each page should have a corresponding class in Pages Each Page class should have a corresponding presenter class in Presenters Logically related code should be grouped in a directory with a namespace php ?le which requires all ?les in