[TYPO3-dev] TCA modification API

Ernesto Baschny [cron IT] ernst at cron-it.de
Fri Nov 19 09:40:09 CET 2010


Bjoern Pedersen schrieb am 18.11.2010 13:13:

> just some thoughts about the TCA manipulation API:
> Currently we mainly hav adding-functions, which only work on the types
> field. The refactoring of the backend results in most items being moved
> to palettes.
> This results in the need to adapt e.g. most DAM-connector extensions.
> Currently this means lots of strreplace calls in ext-tables.
> 
> 
> So my question:
> Would it make sense to have functions to also manipulate the palettes?
> 
> So e.g. AddToPalette
> 	ReplaceInPalette
> 	AddPalette
> 	AddPlatteToTypes
> 	ReplaceInTypes

The idea would be that existing installations still work if they add a
field after/before a field which is now in a palette. The decision in
the core should be made *where* to place the field. Options for "after"
(similar for before) are:

a) after the palette where the field appears
b) after the field inside the palette
   b.1) either by adding a --linebreak-- before and after the new field
   b.1) just as-is, but with the risk of breaking the "layout"

To illustrate the problem of b): e.g. in tt_content we now have "image"
and "imagecaption" side by side, which allows a better matching of the
image and caption (on a row-by-row basis). If an extension adds a field
"after image", this would somehow break the layout.

So I am currently for "a)" but still giving developers the chance to add
stuff to existing palettes as an add-on to more precisely do what needs
to be done (like you suggested!).

Cheers,
Ernesto




More information about the TYPO3-dev mailing list