Hello,
I have been working with hurry.workflow in a project and had some
questions about making hurry.workflow work with different work flows.
For this project each class can have a different work flow with it's own
set of states and transitions. All of the instances of a given class
share
Hi,
2009/6/23 Michael Shaw ms...@nunatak.com.au:
Hello,
Does anyone have any thoughts about how this implementation could be
improved, it doesn't feel like I'm taking the best advantage of the
component model? If I could come up with a set of patches, would the
change to a class based work
Summary of messages to the zope-tests list.
Period Mon Jun 22 12:00:00 2009 UTC to Tue Jun 23 12:00:00 2009 UTC.
There were no messages.
___
Zope-Dev maillist - Zope-Dev@zope.org
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or
Hi,
On Mon, 2009-06-08 at 09:49 +0200, Christian Theune wrote:
Hi,
On Tue, 2009-05-26 at 12:42 +0200, Martijn Faassen wrote:
Hi there,
(in particular Christian Theune)
What's the status of the 'import location' notification functionality in
zope.testrunner?
What's the
On Jun 22, 2009, at 2:51 PM, Martijn Faassen wrote:
Jim Fulton wrote:
[snip[
I made it possible to override proxying by overriding the proxy
method. At this point, I think zope.app.publication provides a
pretty
reasonable base class for custom publication implementations,
although
Jim Fulton wrote:
They wouldn't. They don't use the URL traversal code. Non-URL
traversal code would move to zope.tales. zope.container would depend
on zope.tales rather than on zope.traversing.
For my own education, I would like to understand why it makes sense for
zope.container to
On Jun 23, 2009, at 2:36 PM, Shane Hathaway wrote:
Jim Fulton wrote:
They wouldn't. They don't use the URL traversal code. Non-URL
traversal code would move to zope.tales. zope.container would
depend on zope.tales rather than on zope.traversing.
For my own education, I would like to
Jim Fulton wrote:
On Jun 23, 2009, at 2:36 PM, Shane Hathaway wrote:
Jim Fulton wrote:
They wouldn't. They don't use the URL traversal code. Non-URL
traversal code would move to zope.tales. zope.container would depend
on zope.tales rather than on zope.traversing.
For my own
On Jun 23, 2009, at 3:02 PM, Shane Hathaway wrote:
Jim Fulton wrote:
On Jun 23, 2009, at 2:36 PM, Shane Hathaway wrote:
Jim Fulton wrote:
They wouldn't. They don't use the URL traversal code. Non-URL
traversal code would move to zope.tales. zope.container would
depend on zope.tales
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Fabio Tranchitella wrote:
Zope 2 and Plone
Zope 2 and Plone are obviously related, so the future of one of the two
influences the other one.
The main problem for Zope2 is that the current stable upstream branch
(2.12) still
On Tue, 23 Jun 2009 16:15:12 +0200, Fabio Tranchitella wrote:
Hello all!
In the last couple of weeks Brian Sutherland, Matthias Klose and I
worked together to improve the Zope packaging for Debian and Ubuntu.
This e-mail summarizes the problems we faced, the decisions that have
been taken
Hello,
* 2009-06-24 07:30, Balazs Ree wrote:
What's the reason for the removal of python2.4? Is there a technological
reason, or is this a policy decision? Don't forget that Plone users, who
are also the biggest consumer group of Zope / ZTK, still will be users of
2.4 for a while. The unified
12 matches
Mail list logo