[Typo3-dev] You are the Programmer - System extensions

[Patrick Gaumond]

My toughts about System Extensions (SE)

SE rules! It gives to the whole project a feeling of "completeness". It
always bother me that only core work would increase release numbers but with
the new concept of SE, I get the impression that TYPO3 will be more
attractive from a marketing point of view.

I'm with Kasper on all Inlcude/Enable choice already made except for "Meta
tags extended" that should be a SE.

The DEV package looks like a bunch of SE to me maybe because we're so use to
have the TS Object Browser at hand...

That raise the question on how the package will be managed ? Are we going to
have the possibility to get the DEV package in a single transfer ?

Are packages going to be treated with the same care as the SE ?

Are we aiming at having other theme packages like a PORTAL package ? Six
months ago lots of people ask for pseudo *Nuke functionality.

As for the popular or so useful that they should be declare SE I can think
of :

CleanDB : to really delete marked records, maybe should be integrated into
DBint and be DBAL aware ?
Page PHP Content
(http://typo3.org/extensions/repository/list/page_php_content/) can be a
real timesaver. Maybe dangerous?
Meta tags extended :  Already mentioned, should be a SE.

And well... "Old school CMS" is quite a negative name for a package.  ; )

Patrick