[Typo3-dev] Less features, more future

[Michael Scharkow]

Hi *,

inspired by Kasper's new signature, I'd like to take name some features 
I'd like to get rid off until 5.0 because I think the costs of 
maintaining them are far higher than the benefits. I know everyone has 
his pet feature and we've been adding and adding until now. But luckily, 
TYPO3 is not Java and not Perl, so we don't need a thousands of 
rarely-used features and not more TIMTOWTDI. Users are already in awe of 
the featuritis of TYPO3.

And, yes, I *do* know the backwards compatibility guideline ;=)

Things to remove:

1. Pagetypes: Hide in Menu, Advanced, Backend User Section, Spacer, huh? 
Why can't we just have page properties, nicely arranged and collapsable, 
but with the possibility to have any combination of them. Quite a few 
feature requests in the bugtracker go like "I want checkbox X in 
pagetype Y". Since Pagetype is essentially only a filter field, this 
should be trivial to implement even without breaking stuff (as Stucki 
pointed out concerning not-in-menu).

2. Static templates (or at least the old ones), content(default) and 
friends. If there are none, get rid of the static templates select form 
and only use static from extension.

3. Content Elements: search box, login have been superseded by 
index_search and newloginbox (and others). Either replace them or get 
rid of them completely.

4. Fields in content elements: Space after/before, Frame, Align? All 
those can be replaced by *one* CSS-class field in which these properties 
can easily be defined for the wrapping div field.

5. Typoscript properties: I'm sure there's lots more, but here are some:

XHTML-cleaning, disableImgBorderAttr, page.bodytag etc. - these are ugly 
hacks. Instead, let's make it XHTML strict (or trans for the beloved 
target-attribute which also pops up everywhere in TS) and that's it. 
Yes, HTML 4 is not obsolete yet but why would you need to use this (and 
please don't come up with that legacy stuff again.)? If you think: Why 
can't we just leave it in, please see the condition hell when rendering 
stuff, the various places where tags are changed afterwards, and ask the 
content rendering group.

xMENU_LAYERS: This may be a personal issue but the configuration is 
horrible, the resulting html not very nice, and most of all: it can all 
be done with a regular xMENU, some CSS and JS.

cObjects: PHP_SCRIPT_x, CTABLE, OTABLE, HRULER?, CLEARGIF???!


Okay, enough for now. Flame me or add to the list ;)

Greetings,
Michael