Re: [Zope-dev] Re: catalogObject changes (Zope-2_6-branch)

2003-10-06 Thread Chris McDonough
OK, I can see your point of view. Option 1: Add an update_metadata flag to the catalogObject method with a default of True on all branches. Option 2: Do nothing, but add the "updateMetadata" method to the ZCatalog interface. Option 1 would only take effect when 2.6.3 was released (if ever

RE: [Zope-dev] Re: [Zope] Using 2.3.2 for Zope 2.7

2003-10-06 Thread Tim Peters
[Fred L. Drake, Jr.] > In Python 2.3.x, when a class is defined the __name__ of the > encompassing module is looked up. I suspect Python Scripts can be > fixed by defining __name__ in the globals dictionary in which the code > is executed. Thanks, Fred! I added this info to the collector entry:

Re: [Zope-dev] Re: [Zope] Using 2.3.2 for Zope 2.7

2003-10-06 Thread Fred L. Drake, Jr.
On Fri, 2003-10-03 at 17:27, Jamie Heilman wrote: > In 2.3 you can no longer declare new classes in a Script object. It > bitches about a lack of __name__ attribute. I haven't really had the > time to look into it closely, but it does effect the examples shipped > with zope, and actually its

[Zope-dev] Re: catalogObject changes (Zope-2_6-branch)

2003-10-06 Thread Yuppie
Hi Chris! Chris McDonough wrote: The system is making the assumption that if you update indexes individually, you know what you're doing. Passing an index name into catalogObject was always meant to do as much or as little work as you specified with respect to the names of the indexes; it was onl

[Zope-dev] Javascript variables Form element values and zope

2003-10-06 Thread Gavin Park
Thanks to Dieter and jcc, I didn't think there was going to be a sneaky way to mix zope scritps and javascript in a live page, but hoped there may have been some neat trick ... Looks like its plan B - submitting the form from one frame to another and using the request doohicky. Gavin __