mplate defines where form
actions and buttons should go, and I definitely wanted to keep this
detail in the view class rather than moving it elsewhere.
What's the pattern to achieve what I've outlined with views? Has anyone
else tried to do this? Am I trying to solve this problem
tuesday_pt = ZopeTwoPageTemplateFile('tuesday.pt')
def __call__(self):
if self.isTuesday():
return self.tuesday_pt()
return self.index()
Thanks for this, it captures exactly what I wanted to do! It also means
that the ZCML provides a clear picture of what t
not available, by calling python scripts or whatever.
And the templates have remained in the skins folder rather than moving
somewhere new. Is this the general approach?
Thanks,
pete
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.
().
But what's the best way to do this with a view: I don't want users to be
able to access the templates directly, so I can't redirect between them,
and the two templates are sufficiently different not to be combined
together in an if-else type way.
TIA
pete
___
Jens Vagelpohl wrote:
On 13 Oct 2005, at 09:53, pete wrote:
--
---
From digging in Five/browser/metaconfigure.py the browser:page tag
should have triggered code that inserts the name "inde
Hi,
--
---
From digging in Five/browser/metaconfigure.py the browser:page tag
should have triggered code that inserts the name "index" on the view
class. But apparently it didn't :(
From a fir
Thanks that has made everything much clearer. I'll make sure I label
clearly what conditions I've tested things under in future: I hadn't
fully appreciated that the head might have different dependencies from
the 1.5 branch, though the possibility seems obvious now you've pointed
it out.
J
Hi
I've written the tests now, so hopefully mailhost and cookieauth can be
scratched off the list.
http://www.zope.org/Collectors/CMF/387
Is the collector the best place to put this? If not, let me know and I
can post it elsewhere.
pete
pete wrote:
Hi,
In case it's usef
ence has some ideas?
Anyway, just some thoughts. It would be good to really get the catalog
to be a 'service' with hooks that things can register with in a simple
way, rather than having to do quite so much to wire them in.
Cheers,
pete
whit wrote:
here is a sketch of how a wor
ture so we have a couple of questions
for the list. Is anyone aware of this creating a problem for backwards
compatibility? Is this worth submitting as a feature request? Perhaps it is
already covered by functionality we have not discovered.
Cheers
Pete
-Original Message-
From: Tom Doss
10 matches
Mail list logo
