[TYPO3-dev] Improve EXT:coreapi [Google Summer of Code project]

[Christian Kuhn]

Hey.

On 02/08/2015 10:15 PM, Helmut Hummel wrote:
> As I needed it myself, I implemented a "remove" in typo3_console.
> The problem one faces here is the lack of TYPO3 API to properly handle
> these tasks (add / remove / change a field in LocalConfiguration would
> work, but the change might be ineffective if you have values set
> AdditionalConfiguration.php)

That's easy to answer: AdditionalConfiguration is *not* under core 
control but purely an admin topic: Whatever is put in there will never 
be handled or maintained by core directly. It is "admin" responsibility 
to keep that clean and to handle side effects introduced by stuff 
written to AdditionalConfiguration. We recently did a text change to the 
install tool to hint people more directly about that.

Core can help here by providing (non-php based) standards like context 
based settings, but that is a mid-term topic to solve.

Actually, LocalConfiguration does have a (core internal) PHP API to 
change settings and it works well. However, you're absolutely on your 
own if AdditionalConfiguration overwrites this stuff again. This 
situation will not change as long as we have a 
php-based-settings-and-configuration-approach in the core.

Splitting localconf.php into LocalConfiguration.php (core control) and 
AdditionalConfiguration.php (admin control) is already a huge benefit. 
But this game is bigger and in the end we'll have to kick out 
ext_autoload.php, ext_tables.php, ext_localconf.php, 
LocalConfiguration.php and AdditionalConfiguration.php altogether and 
substitute it with a full "no-code-logic-possible-here" approach. We're 
following this goal since 6.0 already and had quite some progress 
already. The TCA refactoring to single files was one part of that. If 
fully done, we will end up with a big win when it comes to maintenance, 
upgrade path, smooth migration and bootstrap stabilisation. I'm really 
looking forward to this point in time!


Regards
Christian