[TYPO3-dev] ext_typoscript_setup.txt

[Elmar Hinz]

Ernesto Baschny [cron IT] wrote:
> 
> Hm, I am not sure what you mean with "core hack"? I don't think anything
> has changed, and still everything works "as usual" (meaning all
> extensions are still working as they were in previous versions).
> 

I try to relocate the "core hack". If everything works like usual this
means IMHO that you can't replace css_styled_content with another rendering
setup like you imagine, because it would have the wrong id. All extensions
work.  But they only work with css_styled_content or "content (default)",
but with nothing else.

> If I take a look at "article", you have hardcoded the interface to the
> content rendering in your TypoScript:
> 
> tt_content.list.20.articles_edit       =< plugin.tx_articles_edit
> 
[...]
> It works fine because of the hardcoded reference to a place in TS where
> the content rendering expects it to be. But I think this is neither
> documented or bound to be supported forever (but probably will for
> "backwards compatibility reasons").
> 

You have yourself defined it as the api 2 postings before :-)

This "inteface" include defining and using the following
TS branches:

includeLibs.*
plugin.*
tt_content.list.20.*
tt_content.menu.20.*
tt_content.splash.*
lib.stdheader.10.*


> So your idea would be to use those defined places in the TS-tree to put
> in your information? If this is the interface to use (a naming
> convention instead of a PHP interface), we must document and make sure
> all content renderers adhere to this conventions.

But you are right. Best if only one of them would be defined as THE api.
Either a PHP function or this TS tree.

I bet you agree that it is unlikely that this tree will be altered within
the 4.x Branch.

It could change and probably will change with 5.x. With 5.x so much will
change, that it is difficult to plan for it yet. I am sure that there also
will be no function with the name addPItoST43.


Regards

Elmar