[TYPO3-ect] ECT library

[Elmar Hinz]

Good morning typoniks,

a few weeks ago somebody proposed to use the prefix ect for extensions
 organized by the ECT team. I have now registered the extension key
ect itself for a basic library organized by the ECT. My vision is to
provide an alternative to the pi_base class with it, but going a
little further.

1.) The typical functions of pi_base would by organized in a more
modularized way. ECT would serve a a basis for frontend plugins and BE
modules in the same time to keep the code base to maintain and the
learning curve as low as possible.

2.) The library includes enough stuff to build a rudamentary
search-list-details application with an adopted kickstarter.

3.) It is prepared to become a rails similar rapid prototyping system.

Please give further criteria! What should a basic extension library
contain?


Here are my first proposals:

* MVC: The alternative to the pi_base class as object structure

A very small basic framework, maybe only a controller class to extend,
similar to that Michael Scharkow has proposed. Models i.e. tcaObjects
and views i.e. cObjects, tcaForms would go to their own extensions to
be flexible exchangable.

* Link Object: A class to easily make typolinks

It is an object orientated access to the typolink function in
tslib_content. It's the alternative to the cryptic link functions in
pi_base. This will be my personal first contribution to the library.

* Interface: Resultlist renderer and result browser

This are rather interfaces to services, so that implementations can be
 exchanged. We need one default implementation.

* Interfaces: details renderer, search form, search query, details query

Analoguous.

* Translation Object?

Do we need this? PiBase tried to simplify translations with the
pi_getLL function.

* Class with other little helpers from pi_base.

Regards

Elmar