QUICK NOTES -

Developpement with TYPO3 5.0
R.lemke

- 1rst FE plugin for 5.0
- http://5-0.dev.typo3.org : doc available

- What happened so far ?
-- meetings / brainstorming for 2006
-- as Robert moved to Berlin, real coding started
-- new layering mechanisms (TS 2.0 is in place)
-- 2 for free (CMS 5.0 + framework 1.0)
-- Results
--- General design decision, directory layout, coding guideline
-- Results : tsting package (phpunit teest runner)
--- dropped java implementation
--- support JSR-283
--- TS package with new syntax, object orientated, self-documenting
--- CMS contains TS objects & StdWraps

- Sys overview -----------------
-- Getting started : php6 (NO java)
-- SVN checkout with download t3 installer


EXAMPLE : php6
-- Mac Ports
-- installing Typo3.5.0 : get installer install-typo3.php
-- drop on server
-- launch (design not so ok : doesn't display anything
-- Endup in BE


File STRUCTURE
-- 1 dir / packages (extensions) but improved
-- classes dir : all php classes lay
-- will have a ressource manager blocking acess from the next, except the index.php file.
-- COmponents : re-usable, properly encapsuled objects / life of component is managed by component manager (user b.e to instantiate a class)
--- classes are automatically registred as components if declared
--- package manager (no user interface) : scans packages, register classes, connect to the TER (T3PQA). File package : zip, will provide access via web / CLI and offer webservices (soap services)
--- concentrating many version together, with batch upgrade on many servers at a time


- Domain Driven Design-----------------
--domain is a business domain of user
--DDD is about :
* focussing on the domain logic
* accurately mapping the domain concepts the software
* forming ubiquitous language (common language) with the custommer. (babel tower).
* common vocabulary is important for sucessful collaboration
* use same words in the community of users
* see phonebook example...
* Layered architecture : Prestentation / domain / data source
** Domain application logic => Domain Model

- Model View Controller Voodoo-----------------
-- framework package handle requests, provides a Front Controller and a dispatcher whitch dispatches request to the actions controller (with bootstrap on index.php)

- DDD in 5.0 :
* create a package
** new directory
** inside of this dir : new dir : "classes"
** Follows a live demo of "package creation"
*** create a class file
*** classname strictly following naming convention
*** initialize the "entries"
*** methods for setting, getting entries
*** Same goes for the phone book entry class
*** no security checks on entries removal

* domaine model in place : phone book update, delete... contains & knows everything we need
- no about data but more about domain logic (php file with class)

* action controller : can handle requests for taking actions - show entries, create ones
- another php file containing class
- DefaultAction called in case of no action mentioned. Need a new view to displays entry
- this controller must have access to all the methods of the domain through views ??
- can do the render only after setting views (FE output) - presence of a rendering fonction $html (html elements)... of course can use a template file ;-)

* view / widgets : render requested output by using model
- file with class : this whole structure is rendered y the directory / files structure
- based on html with ###MARKERS###


FLEXIBLE RECIPIES : sames but with widgets.
- Use o fwidgets : reusable composite of : presentation model, a widget views, presentation controller (all reusable elements as part of user interface)
- use of adaptors for rendering (the adapter is a table model) : set table model for the widget (or any adaptor) : it's combination
- in the url, you can use short class name (looks like REALURL)

- COmmand LIne access by just calling the index.php or the url IN CMD.
- very interesting for the future ajax BE/ FE : use of widgets

WIDGETS
- adv : consistent look&feel is important (fe/ be)
- adv : centralized templating , oveeridable in special cases
- adv : automatic support for different request / response type
- adv : so easy.

Action controller
- recieve a request, takes action
- can handle web-cli request

REQUEST/RESPONSE (behind the scenes)
=> request => Resquest handler resolver (soap; ttk; cli) => web request handler (build a new request) => web request builder (get all the arguments together in the request object) => web request => dispatcher (get request and response) => action controller (modifiy and resend back again)
* no more UID/PID logic : can work in parallel of the CMS controller (easy for SOAP request : less cache, gets straight to the soap controller).


Presentation controller :
- Configured with a model, prepare presentation and returns rendered
- can render a widget
- render()


- Got Arguments ?-----------------
* GET & POST argument are the N°1 source for attack : can't be accessed directly, but only through the controller request
* 5.0 takes special Care of security

Properties & data type :
* work in progress
* used instead of string : xhtml object
* propertiy objects can be combined (xhtml + text object)
* "property editors" are used to transform properties depending on the context.
* validation is included inte this concept (work in progress) => more details this winter


- Components : play lego-----------------
* Playing with building blocks
** combine of components (orchestration)
** the less components know about each other the easier it is to reuse them in a variety of contexts
** create yur own LEGO set by creating cleanly separated, decoupled componenets !

* Component dependencies
** components seldomly come alone
** cascading dependencies
=> problem = component explicitely refer to other

* dependency injection
** component doesn't ask for the instance of another components, but gets it injected
** "hollywood principle"
** enforce loose coupling and high cohesion
** makes you a better programmer
** completely transparent for your classes, limits configuration. Must be pure php
** can instantiate a class one time and once. works for multi instantiation through iwrapping the class in a larger class ???


- Aspects orientated programming-----------------
** AOP : programmation paradigm
** Security and loggin layer
** use regular expression

- Aspects in action -----------------
*error handling messages

- Timming issues -----------------
* road map => country map : no more linear approach
* points of interest locate in, and thus explorated and updated more easily.
* NEXT STEPS :
** Speed to be iplemented
** See P.Gaumont

=> books : domaine driven design (evans)