[TYPO3-ect] Struts of a Roadmap

[Elmar Hinz]

Hello Jan-Hendrik, hello all,


My Proposals for a Roadmap (only the focus of FE plugins):


1.) Leaving pi_base:

I think our primary milestone should be to give up the dependancy of
extensions from pi_base and show a working example of an alternative
solution.

To make this step easier we need to provide the services of pi_base in
a better, easier, more flexible way. With lib_link I did an important
first step on this way and hope that you follow me and design objects
replacing other parts of pi_base.

2.) Learning MVC (or OOP in general):

We gain a lot of flexibility and freedom of implementation now. We
will discover typical patterns how extensions can be organized more
flexible. But in the end we will find a MVC structure in every
solution, because every FE plugin has a view by nature.

3.) Implementing the kickstarter to generate MVC:

We should be able to automatically generate an application that does
the typical insert, select, update, delete stuff for one table.

4.) Scaffolding extends kickstarter:

We should be able to generate skeleton applications classes by
scaffolding whithin a given extension. That includes to produce a
skeleton of $TCA settings.

5.) Definition of PHP5 Interfaces, Abstracts and TYPO3 Services:

Meanwhile we will have found a bunch of usefull patterns. To make the
interactions and communications of our extensions easy and flexible we
will need standard interfaces and services. This will come with PHP5
within TYPO3 5.0.


This was my proposal for a plan.

It doesn't speak a lot of libraries we need, but we should have the
necessary libraries done or selected from the existing ones in the end.

It doesn't speak of BE plugins, but the overall plan would go in
parallel. We should be able to use our libraries in both places.

It doesn't speak of the organization of ECT, but we need to set up
some structures and need to settle who is responsible for what.


With this proposal I give the moderation back to Jan-Hendrick.


Regards

Elmar