TYPO3 Core

I don't like this:

1. it will produce inconsistent behaviour if one of the system extensions gets some options. In that case the one with options must be shown, so some system extension are shown, some not. But you'd need good knowledge to know that there are more system extensions.

2. The user should be able to see all extensions, else he is disempowered, which is not a good idea.

So my preference is to implement a complete filtering mechanism and have a checkbox "show system extensions" in it, which is checked by default. Such a thing would need some planning (esp. which filters to add).

but this aren't really extensions e.g. extbase and fluid are parts of the core, which can't be removed, but they are packed as extensions to get a better sorting :D

I would also not "hide" them, what's the point?

Imagine one have a local "extbase" in typo3conf/ext, what should happen then?

It's just inconsistent and no real gain here, except old-school people wondering "why extbase is not installed" or something. So I would disagree with this change.

i'm ok with the filter, in the 4.4 em, we also had a filter for hidding shy and system extensions :D

Regards
Kay

The definition of "shy" was always a mistery to everybody and thus I would not add this strange "tag" anymore. Who decides what is "shy" and what not? No extension author will ever think his extensions needs to be "shy". :)

Hiding system extensions is indeed very useful to get an overview of "additional extension" a certain site is using.

Additionally in the EM list of installed extensions it should be somehow visualized which are "system" and which are "local" extensions. In previous EM versions there used to be a column with that information (in the 4.5 New EM you could filter on that particular column to get the "hiding" you are needing now).

i would use "required" as filter instead of "shy" :D, i also never understood "shy" as it was just a setting in ext_emconf ...