[TYPO3-mvc] FYI: Progress in implementing support for generic domain models
Jochen Rau
jochen.rau at typoplanet.de
Wed Jul 22 21:35:45 CEST 2009
Hi Matthias.
Mathias Schreiber [wmdb >] wrote:
> Jochen Rau schrieb:
>> I don't think we have a conceptual problem here. The only thing that
>> is configured in the $TCA is the target class name of relations
>> (foreign_class). The mapping of classes <=> table is configured via
>> TypoScript in my currently developed implementation (see below).
>
> I disagree.
> This would require TYPO3 to load the full TCA in FE (I know it does now,
> but this will be changed in order to reduce overhead in FE rendering).
> We're working on reducing the amount of code loaded in the FE
> significantly.
I have read your recent blog post. Great work!
> So this type of setting (BE TCA definition hitting through to the FE)
> should be avoided at any point possible.
>
> Practically, all of TCA the frontend needs are the enablefields.
> If you need special things from TCA, load them manually.
I prefer convention over configuration. And if I can't avoid
configuration, I'd like to avoid duplicated configuration. The TCA holds
all of the necessary information to map database tables on objects. The
only thing I had to add was the "foreign_class" setting.
> If Extbase takes care of loading the TCA for these tables, I'm fine with
> that.
I will check this again. A did some profiling today and one of the
bottlenecks (in Extbase) is the inclusion of files (require_once) as you
have already mentioned in you post).
Any suggestions (by reading the DataMapping part of Extbase)?
Jochen
--
Every nit picked is a bug fixed
More information about the TYPO3-project-typo3v4mvc
mailing list