[TYPO3-50-general] Beer3, really a good solution?

[Sebastian Kurfürst]

Hi Niels,

> Hm, that's not what I mean. You don't trigger XSLT, the CMS should.  
> You
> don't program the Transform as a template-designer, the
> function-provider (core, extension, ...) does.
Well, as I understood it, you would then want to provide an XSLT  
template rendering the "Template markup" to XHTML (or other outputs).

However I see some issues with extensibility here: It should be really  
easy for people to write new view helpers, and it's a fact that (at  
least in the TYPO3 commmunity) people are most comfortable writing PHP  
code. That's why I think it's a big benefit of having view helpers  
implemented in PHP.

> XSL-T is for XML what the
> View is for MVC, it can Transform your (proprietary) input-template  
> into
> a (standardized) output-result.
I know :-)

> I meant that I prefer to use the existing XSLT Transform-mechanism  
> (as a
> core/extension programmer), instead of having programmers (again)
> program a(nother) Transformation-Logic (again).
I don't think this applies to many extension programmers, in case they  
want to extend the transformation by custom tags/view helpers.
Maybe some other people have comments here, too :-)

> Also templates are not just only about FE web-page output. A select- 
> box
> may be the result of a GUI-element template, tabs, lists, ... IMHO
> everything should tunnel through a template-engine (ever wanted  
> editable
> select-boxes?, ever wanted to turn tabs into sequencial blocks in  
> all of
> your CMS, just with a checkbox?).
Yes, exactly. All HTML output should be rendered by the template  
engine, ideally.

>> And, besides, the language is really verbose - so you sometimes need
>> lots of code for simple things.
>>
> Maybe. I like to basically be able to /program/ a whole GUI in a  
> sandbox
> running in my FireFox without being connected to the internet, instead
> of re-loading a frame-content of the CMS all over again, or if that
> would have impact on data, to repeat all the steps to reproduce the
> test-case that bugged me.
I did not really understand what you mean here and what this means for  
BEER3 / FLOW3 / Templating.
Maybe you can enlighten me :-)

Thanks for your ideas,

Greets,
Sebastian