[TYPO3-ect] Invitation for the initial team of the "BETA" branch

[Elmar Hinz]

Hi Jörg,

> 
> ok, I will do my best ;-) Actually, my manager gave me the time to
> invest my major work-time in this project, for now!!

That's great. Many thanks for him and for you.

> 
> So, how will we proceed?
> 
> As I saw in some other posts there are actually some differences how to
> go further.
> 
> Which Coding Guideline should we use? T3 4 or T3 5? (mainly the naming)

That's the difficult point. We need to hear differnt voices and finally make
a good decision.

A stress to targets of lib/div:

1.) Closing the technological gap between v4 and v5
2.) Building a migration path to v5.

So my voice is to go as far in direction of v5 as possible. 

> Should we use the registry-pattern, or not?

I think we should replace the concept of access to the different
configurations via $controller->configurations etc. by static configuration
access. 

a) It's less to type. 
b) It is easier to explain. 
c) It is easier to understand.
d) The code is easier to read.

http://wiki.typo3.org/index.php/MVC_Framework/lib_div_Beta_Branch?wikitypo3orgdb1_session=d550c7bc1f99c816e2fa33e69e654e80

My suggestions (using Roberts style):

tx_Lib_Register                      (general purpose register)

tx_Lib_Abstracts_ConfigurationAccess (parent of the following classes)

tx_Lib_FlexForm              (flexform values)
tx_Lib_Setup                 (configuration (TS) comming in via the main())
tx_Lib_SetupPlus             (TS < FF overwrite)    
tx_Lib_Request               (request parameters)
tx_Lib_TSTree                (full TS tree via TSFE)
tx_Lib_TCA                   (TCA data)
tx_Lib_TCAPlus               (TCA < TS < FF overwrite)

Some of this need a mechanism (stack?) to keep configurations of parent and
child plugins apart. This is required for tx_Lib_Setup and tx_Lib_Request. 
tx_Lib_SetupPlus and tx_Lib_TCAPlus don't need an own stack. They can be
evaluated dynamically using the tx_Lib_Setup stack.

I will help you with this. I can't explain the full background of
considerations here. 

> Directory structure?


Abstracts/        (all abstract classes)
Controllers/      (different types of controllers)
Helpers/          (all other classes)
Interfaces/       (all interfaces)
Processors/       (all processors of the action pipe)
Services/         (services, but we still need to define a concept for this)

If the plural is not in conflict with the coding guidelines.

http://wiki.typo3.org/index.php/MVC_Framework/lib_div_Beta_Branch?wikitypo3orgdb1_session=d550c7bc1f99c816e2fa33e69e654e

That's my suggestion. The classnames need modifications. See above. Please
suggest modifications.

Regards

Elmar