At 11:54 AM 6/20/00 +0300, Itamar Shtull-Trauring wrote:
"Phillip J. Eby" wrote:
* The missing _objectChanged() message - it was very hard to track down,
because everything appeared to be working right, except for the fact that
it wasn't working. Turns out that _v_status_ (th
At 08:58 PM 6/19/00 +0800, mike wrote:
http://www.zope.org/Members/RainDog/ZSession/ZSession-0.0.2.tar.gz/view
Comments?
Now that I've had a chance to really look at this (while tracking down one
of the bugs you found), I do have a few comments.
First, nice job... It's a good adaptation use
At 10:25 PM 6/20/00 +0800, mike wrote:
"Phillip J. Eby" wrote:
Huh? Oh, %#()@%... I fixed that in my working copy, but didn't check it
into CVS before building a release .tgz yesterday... Argh. Line 137 of
DataSkins.py *should* read:
if self._v_status_ is not Cha
At 10:51 PM 6/20/00 +0800, mike wrote:
"Phillip J. Eby" wrote:
example. Think of someone creating a Session subclass called "Shopping
Cart", with methods for viewing, checking out, adding/deleting items, etc.
Or, if they have many subsystems which want to share the s
At 05:49 PM 6/20/00 +0300, Itamar Shtull-Trauring wrote:
Huh? Oh, %#()@%... I fixed that in my working copy, but didn't check it
into CVS before building a release .tgz yesterday... Argh. Line 137 of
DataSkins.py *should* read:
Great, it works!
Tell me, were you able to use
At 11:33 AM 6/19/00 +0300, Itamar Shtull-Trauring wrote:
As far as I can tell, the first time an object is changed, an Agent's
_objectChanged() will be called, but as long as the object is still in the
memory cache, _objectChanged() will not be called again.
_objectChanged is a once per object
At 08:44 PM 6/19/00 +0800, mike wrote:
Fix for www/storageForm.dtml
$ diff storageForm.dtml.orig storageForm.dtml
7c7
FORM METHOD="POST" ACTION="manage_setStorage"
---
FORM METHOD="POST" ACTION="."
56c56
brINPUT TYPE="SUBMIT" value=" Change Storage Settings"
---
brINPUT
At 08:12 PM 6/19/00 +0800, mike wrote:
Another bug I found (file Rack.py):
def createItem(self,key):
# Create a new object, identified by key
item = self.getItem(key)
# XXX What if all items potentially exist?
if item is not None:
raise
0.4.0a2 is out, to fix the bugs reported by Itamar and Mike. I have not
yet reproduced all the bugs Mike has reported, but here's what's fixed in
alpha 2:
* The missing _objectChanged() message - it was very hard to track down,
because everything appeared to be working right, except for the
At 12:42 PM 6/15/00 -0400, Shane Hathaway wrote:
Agreed; I see this as by far the best approach. It's a tried and true
pattern.
Not only that, but it gives you extremely fine-grained control over what
you do and don't log. And, if the other events like adds and deletes on
folders are in
At 01:40 PM 6/15/00 -0700, Loren Stafford wrote:
Where is Observer-Observable in the development plan? ZPatterns 0.4?
-- Loren
No. 0.4 is targeted for 2.1.6 compatibility, and Observable will require
Zope 2.2's new Traverse features. Also, 0.4 is due out tomorrow and I'm
way behind on
At 01:58 PM 6/15/00 +1000, Stuart 'Zen' Bishop wrote:
Its not a problem with ZScheduler, it a problem that no one has written
a plug-in logging system that is good enough for what you are trying to
do. The existing zLOG API is fine (well - it could be better), but just
needs someone to write the
At 12:06 PM 6/13/00 -0600, ethan mindlace fremen wrote:
Ok, lighter grey less blue bars. Also simply asking for more products will
hide the DC products, as opposed to having to sort (which still works)
Whitespace between entries, please, and an indent of the description would
be nice. It's
At 04:22 PM 6/11/00 -0400, Kevin Dangoor wrote:
What will be the right way to subclass ObjectManager? CatalogAware won't
really be necessary, because you can use the events stuff to catalog
things... but, I make a lot of things ObjectManagers...
All that's required is that manage_afterAdd call
At 06:31 PM 6/10/00 +0800, Mike wrote:
Maybe the best way is to put a 'thumb' data source into Customers
instead of native one. This thumb should translate all messages to
SkyDivers' data source.
Yes, a "Delegation Rack" is certainly possible. It would make it really
easy to merge data from
At 01:40 PM 6/2/00 +0800, Mike wrote:
As I'm reading ZPatterns source code more and more I'm finding there are
good things just hidden in unclean or bad defined interfaces. Just a
suggestion: define interfaces as abstract classes first, then implement
them (as AbstractRack, DefaultRack and
At 01:51 AM 6/2/00 -0600, Bill Anderson wrote:
"Phillip J. Eby" wrote:
[...]
LM 0.8.6 also works with Zope 2.2 as far as being able to be added,
although I'm not sure it interoperates properly with the new security API.
It will still be backward compatible with Zope 2.1.6 either w
At 12:53 PM 5/30/00 +0300, Itamar Shtull-Trauring wrote:
I've been playing around with ZPatterns, and I must say it's very cool -
finally you can mix ZCatalog and SQL storage. CatalogAwareness is slightly
different than regular Zope objects in that you have to find the ZCatalog in
the Rack's
At 06:14 PM 5/26/00 -0400, Evan Simpson wrote:
D'oh! How 'bout if REQUEST.close() were to always do a
self.__dict__.clear()?
Are you absolutely positively sure that REQUEST.response is never accessed
following REQUEST.close()? In my cursory examination of the code paths, I
wasn't sure that
At 03:05 PM 5/26/00 -0400, Evan Simpson wrote:
- Original Message -
From: Phillip J. Eby [EMAIL PROTECTED]
Been there, done that. Yours doesn't work either, btw. Well, actually,
it
does, it's just that it causes a memory leak because it leaves an
unintended circular reference. We've
At 01:56 PM 5/25/00 +0400, Jephte CLAIN wrote:
When I don't wrap items like this, I get strange unauthorized errors.
Only the super user can use the items. All the other users (Managers or
not) can't.
In normal usage, one only accesses a rack from or in a Specialist.
Specialists wrap the
At 12:45 AM 5/25/00 -0400, Tres Seaver wrote:
Ah, ok -- I was planning simply to leverage the ZODB's facilities for
maintaining persistent references in the DefaultObservable mix-in; more
elaborate schemes would be possible (for instance to support
rack-mounted observers?)
Actually, just using
At 10:03 AM 5/26/00 +1000, Anthony Baxter wrote:
"Phillip J. Eby" wrote
I would suggest that it ask for an interface, rather than a meta_type.
Otherwise, you've hardwired yourself into a single object type with no
extensibility. For example, an SQL method wants the nearest SQL
At 05:33 PM 5/24/00 +0400, Jephte CLAIN wrote:
Hello,
I believe items got from a rack have to be wrapped in context of the
rack. I've been bitten by this (and it hurts!). When I try to use items
from DTML, only the superuser can use it, even managers can't access the
objects. When I wrap the
At 05:24 PM 5/24/00 +0300, Itamar Shtull-Trauring wrote:
"Phillip J. Eby" wrote:
Make your root acl_users a LoginManager, with the loginForm there.
LoginManager will only allow "Anonymous" to log in if it is the root
acl_users. This is how standard user folders behave, a
At 07:19 PM 5/24/00 -0400, Tres Seaver wrote:
I have started a page for an implementation of the GangOfFour Observer
pattern within Zope:
URL
http://www.zope.org/Members/michel/Projects/Interfaces/ObserverAndNotificat
ion
Please comment, either here or in the wiki.
Is this only for events
At 03:51 PM 5/21/00 -0400, Tres Seaver wrote:
This is really just the classic Observer pattern, a la GoF Design
Patterns. "ObjectAdded" and "ObjectRemoved" are events a
"RackObserver" would register for; "AfterCreate", "Changed",
and "BeforeDestroy" are events of the "hosted" object itself.
At 04:04 PM 5/18/00 -0400, Dan L. Pierson wrote:
The portal now gets created, but I can't login to the initial account.
I also can't display the members roster by clicking on Members
(AttributeError for getUsers), but can write a DTML method in the
UserSource that lists all one user. The code
201 - 228 of 228 matches
Mail list logo
