[TYPO3-dev] stable = documented ?

[steve ryan]

Mechanisms for injecting configuration
*($this->conf)
1 - constants and setup in sys_template records
2 - ext_typoscript_setup.txt and ext_typoscript_constants.txt
3 - static/pi1/setup.txt and static/pi1/constants.txt
4 - fields in tt_content related to specific plugin BAD
5 - flexforms
6 - template constant editor
7 - loading of arbitrary TS style config files (based on other config)
8 - php definitions in ext_localconf.php


Thoughts
* it is desirable that a plugin works out of the box for beginners
* seperation of cascading (TS) or per content (fields/flexforms) 
configuration
* where is configuration loaded/combined - extension rendering, 
extension loading
* removing junk configuration for efficiency ??
* who is setting configuration - users, admin, developer
* seperation of configuration - default(2) , preset 
customisation(3/5/7), arbitrary customisation(1/4/?5)
* interpretation of empty/invalid configuration. User feedback at 
extension rendering.
* known mechanisms/standards - _DEFAULT_CSS, static templates, 
sys_template records, table=, global storage page
* order of inclusion (order of extension installation/template inclusion)

For my money. I set pretty much everything configurable as defaults and 
examples and reference in ext_typoscript_setup.txt and 
ext_typoscript_constants.txt and use flexforms or template records to 
tweak. I have used flexforms for preset style configuration. I guess 
static templates also fill the preset role in a somewhat less intuitive 
but cascading manner.
I don't see the problem with dumping a whole stack of working/example 
config as a default. It's easy enough clean up - plugin.blah > or 
whatever else is an appropriate inclusion method.


Steve Ryan


Elmar Hinz wrote:
> R. van Twisk wrote:
> 
>>As long as I know what the TS is what I can give.
>>(ext_typoscript_setup.txt and ext_typoscript_constants.txt)
>>
>>These two files can help me a lot, even without doc....
>>These two files might be good for the reviews aswell,
>>I mean show if they are included.
>>
> 
> 
> Hi Ries,
> 
> for me the existance of ext_typoscript_setup.txt and
> ext_typoscript_constants.txt are alarm bells for an outdated extensions.
> Modern extensions shouldn't contain TS templates that can't be deselected.
> 
> I want to see:
> 
> pi1/static/setup.txt
> pi1/static/constants.txt
> 
> or
> 
> static/pi1/setup.txt
> static/pi1/constants.txt
> 
> I like best
> 
> configuration/pluginXY/setup.txt
> configuration/pluginXY/constants.txt
> configuration/pluginXY/...
> 
> Where pluginXY is a descriptive name of the plugin like searchForm,
> detailsView, ....
> 
> ext_typoscript_setup.txt and ext_typoscript_constants.txt are as polluting
> as DEFAULT_CSS in TS.
> 
> 
> Regards
> 
> Elmar