[Typo3-dev] Less features, more future

[Kasper Skårhøj]

Hi JoH,

Thanks for your suggestions! Here are some comments.

> This brings me to the major issue when it comes to a new concept of  "smart
> content rendering".
> IMHO we should stick to the following rules, while producing the new
> content rendering stuff:
>
> 1. No hardcoded values and tags in the PHP files at all. They should be
> replaced with TypoScript settings to keep backwards compatibility. The
> default setting should be the "correct" behaviour though, while the "old
> school" behaviour can be acchieved by setting something like
> config.backwardsCompatibility = 1

I think we have to align all output from TYPO3 in the frontend according to 
the following objectives:
a) All output must have reasonable defaults that enable quick implementations 
with standard stylesheets providing uniform style to all content.
b) The possibility of completely free templating for those who are required by 
customers to do this.

What methodology is used is not really in question. Personally I believe a 
templating API should be made which enables everyone to choose his/hers 
favourite way, be it TypoScript TEXT cObjects, HTML documents with markers, 
Smarty templates, TemplaVoila mapping or hardcoded HTML in PHP.

> 2. TypoScript should be used as much as possible.

As it is right now, TypoScript has a long history of pissing people off and on 
that basis I can't agree to increase the usage. However, my plans for 
TypoScript might make this irrelevant since a future implementation might be 
completely verifiable and object oriented and fullproff. Only thoughts.


> 3. Every Content Element should get a set of predefined HTML Templates plus
> a flexform to use custom templates (plus the ability to define HTML
> templates to be used via TypoScript)

Hence templating API, yes.

> 4. No inlines styles - they should be generated as dynamic stylesheets
> using a default typeNum. So each time the page is rendered it will create
> classes and ids for the tags _and_ the corresponding stylesheet.

OK

> 5. Users must be able to override 3. and 4. using TypoScript and/or custom
> PHP functions

Yes of course, honoring old frank, "I did it my way"

- kasper


>
> There might be more, but these are the main things I would like to improve.
>
> What do you think?
>
> Joey

-- 
- kasper

-----------------
Think future, not feature