[TYPO3-mvc] FYI: Progress in implementing support for generic domain models

[Bastian Waidelich]

Christopher Hlubek wrote:

Hi there,

> But I think we have an underlying conceptual problem:
> Generic stuff should not be configured in the TCA!

My absolute favorite would be to use a class with the same name 
(properly camelcased) if nothing else is specified (so, no need to 
define anything in the TCA by default).
And then being able to override the implementing class via TypoScript.

That way you could also hook into other extension without the need of 
xclasses or similar just by having something like:

tt_content.list.20.blogexample_pi1 {
     objects {
         Tx_BlogExample_Domain_Model_Person {
             className = Tx_MyExtension_Domain_Model_Superperson
         }
     }
}

(similar to the Objects.yaml in FLOW3)

I'm not sure whether this could be easily implemented without AOP - But 
as all instances should be created with the object manager it should be 
possible..

And think about the possibilities - you could write your own blog 
controller and set it as default implementation.

 > When thinking about Extbase in the backend (we need that for better
 > backend modules!) TypoScript doesn't seem to be the best idea for me.

Why not?

Bastian