Am 18.07.2007 um 23:32 schrieb Charlie Clark:
Well, I've now got two classes (EventvCalView has to set different
headers so I can't see an easy way round this in ZCML) and two
different templates. Everything is working fine apart from the
content-type is remaining steadfastly text/html! Co
Am 18.07.2007 um 23:10 schrieb Maurits van Rees:
No, that is the name. That means you can do
tal:define="view context/@@event_iCal_view"
in a template that has an IEvent provider as context.
The class is the EventiCalView class in event.py.
Yes, thanks.
So, let's say I need to turn my
Am 18.07.2007 um 23:03 schrieb Philipp von Weitershausen:
You know, I wrote a whole book for learning how to use this Zope 3
stuffm (and that includes explanations of how to use it in Zope 2
via Five).
No need to be shameless, Mr. Gallagher! I've got the book and am
working my way
Charlie Clark, on 2007-07-18:
> Okay, thanks! I'm nearly there. I think. %-? ;-)
>
> Because I'm only creating essentially a slightly different view of an
> event I've taken the ZCML for the standard view as a lead:
>
>for="Products.CMFCalendar.interfaces.IEvent"
>layer="Produ
Charlie Clark wrote:
I making my first stab at browser views for my iCal support having
finally come up with some templates that seem to produce files that work
with most calendar programs.
I have a couple of questions:
1) should I implement them as BrowserViews calling templates or should I
Am 18.07.2007 um 22:07 schrieb Rob Miller:
while it may be appropriate in some cases to pass values directly
into the template like this, usually the template pulls the values
from the view class. you can make "name" an attribute (or a
property) of the view class, and then use the "view/n
Charlie Clark wrote:
Hi,
I making my first stab at browser views for my iCal support having
finally come up with some templates that seem to produce files that work
with most calendar programs.
I have a couple of questions:
1) should I implement them as BrowserViews calling templates or shou
