[TYPO3-dev] Features for the List Module

[Bernhard Kraft]

Georg Ringer schrieb:

>> 2. Make kb_modlist_actions a sysext "modlist_actions" but do not install it
>> by default.
> 
> or just include it in core and there is one sysext less which is
> installed everywhere.

Well. Of course you could include it, with the cost of only one function
call and a check if some TS-Config is set. But using a hook requires almost
the same execution time.

What I like very much about TYPO3 is its modularity. It is not an absolute
piece of code but very extensible, etc. In the Linux kernel for example,
you have a lot of options which you can compile in either statically or as
dynamically loadable modules - which is a very popular approach. I just do
not like it to put every little feature into the core without giving an
admin the chance to remove it.

For example you could create an configuration interface, where an admin can
set which buttons in the List-Module would be visible to a group/user.
Well. I just came to the conclusion that this discussion wont lead to an
end. It is just a matter of preferences.

Do their exist any guidelines how to cope with new features for TYPO3???
Wheter to include them into the core or as sysext? AFAIR Kasper tried to
move everything into a sysext - which is the reason why also the FE
(EXT:cms) and a bunch of other essential parts of TYPO3 are extensions and
not part of the core. I guess the core could be defined as the BE itself
including the list module, extension manager, TCA and the bunch of classes
in t3lib/



greets,
Bernhard