Hi!
Here is an implementation of "compound storages" in CPSSkins (this
concerns the CPSSkins AJAX toolkit only so it also applies to Zope3 in
general, or to any other server that can handle JSON requests and
responses).
First of all, this is a great step towards simplifying the development
On Thursday 12 January 2006 14:11, Gary Poster wrote:
Problem:
We want to perform actions when a user is added to a group, and
possibly when a user is removed from a group. There is no hook point
for this currently in the zope.app.authentication code.
Solution:
Fire events in the
+1 on the proposal for me, though I would think that we could add the new
attribute/method to the interface with a note that it does not have to be
implemented yet. This gets us back to our interface versioning discussion. I
know you just wanted to avoid this by declaring a new interface, but
+1 for this one as well. :-)
Regards,
Stephan
--
Stephan Richter
CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student)
Web2k - Web Software Design, Development and Training
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub:
On Friday 03 February 2006 17:23, Dieter Maurer wrote:
Stephan Richter wrote at 2006-2-3 12:45 -0500:
...
declareSite name=mysite /
site name=mysite /
!-- normal directives here. --
/site
The declareSite looks redundant. I see at the site name='mysite'
element that a site with name
On Friday 13 January 2006 07:35, Gary Poster wrote:
It might be reasonable to add a bit to the IPrincipal interface that
__eq__ is provided and uses id to compare. That seems reasonable to
me, but maybe others have qualms. Care to write a mini-proposal? ;-)
You have my +1 vote.
Regards,
On Tuesday 17 January 2006 13:08, Jeff Shell wrote:
I noticed that modules that begin with an underscore aren't shown in
apidoc in Zope 3.2. I think (but am unsure) that Zope 3.1 showed
these. I'm sure there may have been a good reason for doing this, but
it makes navigating the zope.schema
On Tuesday 17 January 2006 03:27, Markus Leist wrote:
is there any small kind of sourcecode which can do a simple trigger of an
ecm.workflow direct in an object-method?
I have some xmlrpc-methods in which i have to modify the state of
self...workflow.
in my old zope.app.workflow-source it
On Wednesday 11 January 2006 14:10, Gary Poster wrote:
zope.locking: a replacement for zope.app.locking that provides
additional features while learning from the zope.app.locking
strengths and weaknesses.
Could we deprecate zope.app.locking and move the code to zope.locking?
Regards,
Hello,
should I add the enhancement to the homefolder manager to the CHANGELOG or is
it too unimportant to add? (revision 41424)
Florian
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub:
On Sunday 05 February 2006 11:17, Florian Lindner wrote:
should I add the enhancement to the homefolder manager to the CHANGELOG or
is it too unimportant to add? (revision 41424)
Everything should be added. :-) Whether I add it as a change entry in the
release announcement is a different
On Thursday 19 January 2006 04:05, Shaun Cutts wrote:
What is happening is that min (and max) are ValidatedProperties of
Orderable. When a missing_value is supplied, min = None (by default)
is checked and fails validation.
Good analysis.
One solution is to change None into missing_value in
A while ago, we had some discussion on when to make releases and
how long to support deprecated features. The discussion has died down
so I'll summarize what I think the conclusions were:
- We'll move releases up one month to may and November from June and
December. This means that the next
On Tuesday 24 January 2006 12:26, Shaun Cutts wrote:
It would seem that the current default mechanism is poorly suited to
providing default values for non-immutables. For example:
class IBar( Interface ):
a = Object( schema = IFoo, default = Foo() )
Yes, this is even more apparent
On Sunday 05 February 2006 12:11, Jim Fulton wrote:
A while ago, we had some discussion on when to make releases and
how long to support deprecated features. The discussion has died down
so I'll summarize what I think the conclusions were:
- We'll move releases up one month to may and
--On 5. Februar 2006 12:11:08 -0500 Jim Fulton [EMAIL PROTECTED] wrote:
A while ago, we had some discussion on when to make releases and
how long to support deprecated features. The discussion has died down
so I'll summarize what I think the conclusions were:
- We'll move releases up one
On Feb 5, 2006, at 10:41 AM, Stephan Richter wrote:
On Wednesday 11 January 2006 14:10, Gary Poster wrote:
zope.locking: a replacement for zope.app.locking that provides
additional features while learning from the zope.app.locking
strengths and weaknesses.
Could we deprecate
On Feb 5, 2006, at 12:20 PM, Stephan Richter wrote:
On Tuesday 24 January 2006 12:26, Shaun Cutts wrote:
It would seem that the current default mechanism is poorly suited to
providing default values for non-immutables. For example:
class IBar( Interface ):
a = Object( schema = IFoo,
On Sunday 05 February 2006 14:35, Gary Poster wrote:
On Feb 5, 2006, at 10:41 AM, Stephan Richter wrote:
On Wednesday 11 January 2006 14:10, Gary Poster wrote:
zope.locking: a replacement for zope.app.locking that provides
additional features while learning from the zope.app.locking
Hello:
I would like to request a small enhancement to the installation scripts
for Zope 3.
I believe it is easy to do, but not being familiar with the packaging
machinery, I could not figure out how to do it quickly.
Like many Zope3 developers, I download a new Zope3 tarball and do the
Jim Fulton wrote:
A while ago, we had some discussion on when to make releases and
how long to support deprecated features. The discussion has died down
so I'll summarize what I think the conclusions were:
- We'll move releases up one month to may and November from June and
December. This
21 matches
Mail list logo
