[TYPO3-ect] T3N Article

[JoH]

>> You can count me in for creation and/or reviews of TypoScript setups
>> for the different fields.
>> I am very familiar with the three step concept of the current
>> fe_admin and I guess much better with "TypoScripting" than with PHP
>> coding.
>> It would be cool to have something like a "standard" TypoScript
>> solution that will work without additional parameters just with
>> snippets based on current TSref.
>> For the API developers this means that at least stdWrap should be
>> implemented wherever it might be useful.
>>
>
> Michael Scharkow wrote 15.01.2006  13:18 CET in
> t.p.content-rendering, that he already has started a TS std lib but
> didn't get any support from others. Now he is looking for a
> successor. Maybe you could have a look at this. Is it interesting for
> you? Maybe he would support your team.
>
> Than let us fix it that you organize a "standard" TypoScript
> solution. If I see it right it has following aspects:
>
> a) idea and conept
> b) the necessary templates
> c) best practice guideline for ext developers API
> d) docs for template users
>
> Is this right so far?

Not exactly.

> Should it be one extension or a modular set of extensions?

None of these.

> Could it be used a a common base for the out-of-the-box installations?

yes and no.

I think you got me wrong in some points.
What I wanted to offer is just TSref based TypoScript snippets for the
different projects and extensions.
Just to avoid things like myExtensionsFirstParemeterStdWrap on the one hand
and hardcoded values in PHP on the other hand.
You can find still find them in extensions like i.e. tt_news.

It should be possible to do things like this by default:

myExtension {
    firstParameter {
        field = whatever
        wrap = <xyz>|</xyz>
    }
}

or even

myExtension {
    firstParameter {
        cObject = WHATEVER
        cObject {
            some cObject parameters here
        }
        wrap = <xyz>|</xyz>
    }
}


In most cases people don't use stdWrap properties in their extensions and
this is what we should do better to make them as flexible as possible.
To avoid a waste of precious developing time I wanted to offer creation of
TypoScript and the technical part of the HTML output (maybe even dynamical
CSS), while others can concentrate on PHP coding and real design.
The only thing the PHP coders must do to make this possible is to give us
the names of the parameters containing the stdWrap properties. Could be seen
as kind of a "hook" for TS injection.

What I don't want to do at the moment is to reinvent CSS-styled-content.
This is something which is already the goal of the content rendering group.

Joey

-- 
Wenn man keine Ahnung hat: Einfach mal Fresse halten!
(If you have no clues: simply shut your knob sometimes!)
Dieter Nuhr, German comedian
http://www.cybercraft.de