[z3-five] Re: Using Zope2 page templates with Five

[Martijn Faassen]

Philipp von Weitershausen wrote:
> Martijn Faassen wrote:
> 
>> Philipp von Weitershausen wrote:
>> [snip]
>>
>>> I certainly would like to have Zope 3 ZPTs in Five, as would probably 
>>> others. If people really have the use case of needing Zope 2 ZPTs, 
>>> how about the following:
>>>
>>> <browser:page> and all the configuration directives known from Zope 3 
>>> make regular Zope 3 ZPT pages, while <five:page> and corresponding 
>>> directives make Zope 2 ZPT pages. Or, maybe in a more intuitive 
>>> manner, <zope2:page>?
>>
>> I don't really like that. I'd rather reduce the number of bewildering 
>> options, as two ways to create pages would only reduce Zope 3 
>> compatibility in the wrong run. five: directives should only be there 
>> in *addition* to Zope 3 directives, to do some extra setup to make it 
>> work in Zope 2, or something like that; they shouldn't replace Zope 3 
>> directives.
> 
> My point :). The five: or cmf: directives would be add-ons, they could 
> even be defined in a third party product like CMFonFive.

The second option to do the same thing differently doesn't go away if 
you put it in an add-on. Anyone working with Five and CMF needs this. 
You're also likely to need this if you *don't* work with CMF and want to 
use Five, as in the case of Silva, where I'd like to integrate with Zope 
2 page templates too. I'd therefore like to have this in Five, as it 
doesn't have much to do with the CMF as far as I can see.

>> What are the concrete use cases of having Zope 3 ZPTs in Five? What is 
>> missing in Zope 2 ZPTs?
> 
> Well, as Fred said, the ZPT implementation of the future is the one from 
> Zope 3. The Zope 2 will even be replaced with that one at some point in 
> the future.  So, first of all, it sounds like the better bet for the
> future. 

Five is about being able to use Zope 3 in Zope 2 now; if in the future 
it'll be easier to use Zope 3 page templates, then that's good. Perhaps 
Fred can even figure it out for us now. That'd be great! But if not, I'd 
like to go ahead and make it work now.

> Second, the Zope 3 ZPT implementation has received improvements 
> that haven't made it back to the Zope 2 flavour (I know that for a fact, 
> just nobody remembers which changes those are).

I think I can make a fairly solid case that we do not care about 
improvements nobody can remember. :)

> Anyway, I'm really the only one without a hard use case here. Both 
> Lennart and you have one, so I'm not too strong on this. All I was 
> trying to point out that there is a way to support both without them 
> interfering and possibly with both benefits.

I'd really prefer to have one obvious way to do it instead of two 
options here. The drawbacks are fairly minimal if indeed Lennart has 
things working correctly with Zope 2 page templates.

Regards,

Martijn