[TYPO3-ect] ECT library

[Elmar Hinz]

Franz Koch schrieb:
> I allready got something like your flexible interface-renderer - well it
> goes in that direction and needs more work on it. I think I allready
> wrote that somewhere a view days ago.
> 

Great, it's ECT's primary target to coordinate not to reinvent. :-) So
if you want to do a joint development with your code you are welcome.
We need a platform for joint development of extensions.

I like the combination of subversion and trac very much:
Example: http://svn.webempoweredchurch.org:3000/misc/


> Currently I use for my extensions a basic structure and the most work I
> have to do for a new 'basic' extension is only to define some shortcuts
> I like to use for my markers, the name of the database table and
> possible related tables for my query-builder function (could also be
> fetched from TCA) and create the template and LLL-labels.
> Besides of some small addons most configuration is done in the flexform,
> in which I can control certian aspects of the queries (like a field as
> exclude-criteria for list-view and of course what criteria/value must be
> given to be excluded - like 'only show record if field birthday, treated
> as date, compared by day and month, is 5 days older or younger than
> current day').
> This extension could be extended by a table-selector in the flexform andRi
> then it would be able to provide most of your mentioned display-forms
> dynamicly for any table visible to TCA.
> 

Sounds like a nice little framework for a standard kind of extension.
I assume the shortcuts you mention could be set during a kickstarter
process?

As soon as we have modularized the tools of pi_base into small objects
we don't need to inherit from the one and only controller class any
more. We can use different systems. The framework you propose could be
one of them.

To prevent chaos we should workout some usibility guidlines at the
same time. Standards of a cohesive usage of extensions, that should be
implemented independent of the used model of implementation.

As important is the definition of interfaces between the applications.


Could you go more into details of your framework? Are model and view
separetd. Could you give an example how the controller brings them
together then?


> 
> It would be nice if this ECT-'subframework' would have some kind of
> rights-management for FE-users and groups - like:
> - visible extension-fields
> - usable functions/actions (upload,listview,search)
> 

If we follow Davids track we will not necessarily distinguish between
frontend and backend users in future. We still can do. But we gain the
possibility to use the same tools for the administration of all users
in the same or in different tables. We wouldn't need to build an extra
rights-management for FE-users then. We wouldn't need to learn 2
different tools and systems for rights management.


Regards

Elmar