[TYPO3-team-core-v5] Templating Engine

[Robert Lemke]

Hi Sebastian,

just a note: can you move the Template Engine thread over to the v5  
general list?
We'll soon need the core list for release planning etc. and we should  
then mainly
use it for discussions / organisation within the core team.

Thx,
robert

On 22.10.2008, at 08:05, Sebastian Kurfürst wrote:

> Hey Sebastian,
>
>> to be honest at first I was not very happy to read about a new
>> template
>> engine, because it's one more thing on the big list of "What you
>> have to
>> learn to get from traditional TYPO3 Extensions to FLOW3 Packages".
>> But reading the reasons it appeared ok to me.
> It's no final decision yet, but we are seriously thinking about
> including the templating engine in TYPO3 4.4 as well - so people can
> get used to it, before they migrate. Besides, I think there will be
> people writing Smarty or PHPTal connectors for v5 - so you'd be free
> to use these as well.
> Does this sound reasonable to you? :-)
>
>> I have a suggestion for improving the overall syntax which makes it
>> also
>> easier to implement arrays.
>> Why don't you nest parameters as tags into the containing tag:
>>
>> <f3:link:to>
>> 	<f3:param name="controller">posts</f3:param>
>> 	<f3:param name="action">editPost</f3:param>
>> 	<f3:array name="requestParameters>
>> 		<f3:index name="postId>{post.id}</f3:index>
>> 	</f3:array>
>> 	<f3:content>Edit post</f3:content>
>> </f3:link:to>
>>
>> I think this does not fit well into your concept, but it does not  
>> have
>> to be exactly like this. Maybe this can be an inspiration to you.
> I've been thinking about it, and I think it could work with the
> current concept as well.
> However, I think that the above syntax is too verbose for my taste -
> It is 8 lines, just to print a single link with some parameters? My
> gut feeling is that this would be worse than it is now...
> Why do you feel the above syntax is better than the one described by
> me? I'm interested to hear your opinion :-)
>
>> By the way: Is BEER3 someting like a development name or are you
>> serious
>> with that? Is there a deeper meaning behind that or is it just beer?
> Beer3 means: Best Ever templateEngine Replacement - but it is no
> serious name :-)
> So we are still looking for good names.
>
> Thanks for your comments,
>
> Greets from Dresden,
> Sebastian
> _______________________________________________
> TYPO3-team-core-v5 mailing list
> TYPO3-team-core-v5 at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-team-core- 
> v5

-------------- next part --------------
A non-text attachment was scrubbed...
Name: PGP.sig
Type: application/pgp-signature
Size: 186 bytes
Desc: This is a digitally signed message part
Url : http://lists.netfielders.de/pipermail/typo3-team-core-v5/attachments/20081022/1512d647/attachment.pgp