[TYPO3-dev] Moving the topic of the discussion alittlebit--Based of thread "Change roadmap..."

JoH info at cybercraft.de
Thu Apr 13 03:19:15 CEST 2006


> Regarding the re-education of designers: Either you have a guy
> designing and then writing TypoScript to put menus in his design. He
> will love to work in Smarty, since it will be much more HTML and very
> simple programming, and much less TSref and optionSpilt voodoo. He
> can suddenly do stuff like putting a horizontal menu in a tablerow
> and figuring out what colspan= to put in the next row.

No problem with TypoScript either.
Example.

temp.whatever = COA
temp.whatever {
    wrap = <table>|</table>
    10 = HMENU
    10 {
        wrap = <tr>|</tr>
        1 = TMENU
        1 {
            NO = 1
            NO {
                after.cObject = LOAD_REGISTER
                after.cObject {
                    saveNumberOfItems.data = register:count_menuObj
                }
            }
        }
    }
    20 = TEXT
    20.value = Some text to put in a colspanned cell
    20.outerWrap.cObject = COA
    20.outerWrap.cObject {
        wrap = <tr>|</tr>
        10 = TEXT
        10.value = |
        10.dataWrap = <td colspan="{register:saveNumberOfItems}">|</td>
    }
}

> Otherwise, you have a guy living in PhotoShop, Illustrator and
> Dreamweaver, who never had a clue what this "HTML" is anyway, and
> then you have a TypoScript guy transforming that work into a template
> - and he will love Smarty as well - for the same reasons..

Fine - so give him smarty as an option but let him decide if he wants to
stick to pure TS.

> But the real demand for Smarty is not in the core, in the
> 'templates'. It is in the extensions. The more complex an extension
> is, the more sure you can be that you will have to edit class-PHP
> (which, by definition, is business logic) to modify exact
> presentation behaviour. And the more design-oriented your design guy
> is, all the more likely it is that he will demand that you do that.

Same thing here - smarty can be an option but should not be the only
rendering engine.
It's not that I don't want to have smarty integrated into TYPO3, maybe I
would even love using it too.
But this is no justification for a replacement of TypoScript.

Joey

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






More information about the TYPO3-dev mailing list