Etria Lists

Tim Hicks wrote:
> Reinout van Rees wrote:

>> So... To me, there really have to be really good reasons not to turn
>> them into skin templates. "Speed" is often quoted as a reason, but that
>> might actually sometimes work against it.
> 
> I didn't write things this way with speed in mind, but rather, to make
> reuse of the templates far easier across projects.  I'm pretty happy
> with the results as I have now written two products based on this that
> provide syndication feeds to many more object types
> (PloneboardSyndication and a branch of ATCTSyndication).

For that, it seems to work OK. But wouldn't you be able to get the same
result with a regular skin-based page template plus a view class in
front of it?

I'm not really in favour of doing some apache rewrite rule magic coupled
with my own old home-brewn atom template just to get the caching right.

Anyway, I'm not telling you to rewrite everything. I'm just hoping for a
solution somewhere. I get the feeling though that I've gotten more grief
than goodies from hard-coded zope3 templates. View classes: great. Those
templates: bah.

> It also seemed like the right pattern to follow as it is the new-fangled
> Five/Zope3 way of doing things.  As that is the case, I presume people
> are thinking/working on ways to resolve these caching issues.  Or maybe
> that's just wishful thinking...

At the moment: yes. Mostly because cachefu does some hacky
monkeypatching, using that monkeypatching with zope3's page template
mechanism works, but not for quills' atom feed 'cause that's doing a bit
too much magic acquisition or so. You'd have to ask Rocky Burt to be
sure, though.

Perhaps I'm overlooking something or Rocky is overlooking something.

Reinout

-- 
Reinout van Rees                       r.van.rees @ zestsoftware.nl
http://vanrees.org/weblog/                  http://zestsoftware.nl/
"Military engineers build missiles. Civil engineers build targets."