[Zope-dev] Where to send patches?
Hi, All Since the Collector is down, where do we send patches if we are not cvs-authorized? I just discovered a not-too-clever hack to make the Find tab recurse through methods of Z Classes, which the margin of this e-mail is too small to contain. -- Jim Washington ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Where to send patches?
Just post them onto this list... someone from DC will read it. Cheers. -- Andy McKay. - Original Message - From: Jim Washington [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Monday, September 10, 2001 9:16 AM Subject: [Zope-dev] Where to send patches? Hi, All Since the Collector is down, where do we send patches if we are not cvs-authorized? I just discovered a not-too-clever hack to make the Find tab recurse through methods of Z Classes, which the margin of this e-mail is too small to contain. -- Jim Washington ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Where to send patches?
On Mon, 10 Sep 2001 12:16:51 -0400 Jim Washington [EMAIL PROTECTED] wrote: Hi, All Since the Collector is down, where do we send patches if we are not cvs-authorized? I just discovered a not-too-clever hack to make the Find tab recurse through methods of Z Classes, which the margin of this e-mail is too small to contain. Dude, don't jinx yourself. I'm sure you don't want us to refer to this as Jim Washington's last patch. ;) -Michel ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
RE: [Zope-dev] Problems with CatalogAware?
Right now I only call index_object() after an edit, as I was assuming that
after adding things would be automatically taken care fo for me, but
obviously this is not the case. There are, indeed, default values in some
properties within the class __init__ method.
I think what is happening is that I am indexing methods (not properties),
and since my factory method doesn't call an explicit reindex_object() after
some properties are changed (code below) I am having problems. I wonder if
I call self[id].index_object() after self._setObject(id, ad) if that will do
the trick?
Thanks for the reply,
Sean
def manage_addAdItem(self, id, title, REQUEST=None):
Zope managment interface create method for AdItem
ad=AdItem(id)
ad.setId(id)
ad.setTitle(title)
if REQUEST is not None:
ad.setAdBody(REQUEST['adBody'])
if (len(REQUEST['keywords']) 0):
ad.setKeys(REQUEST['keywords'])
ad.setAdDateMulti(=REQUEST['Ad'], mm=REQUEST['Admm'],
dd=REQUEST['Addd'])
ad.setRtDateMulti(=REQUEST['Rt'], mm=REQUEST['Rtmm'],
dd=REQUEST['Rtdd'])
ad.featureURL=REQUEST['featureURL']
self._setObject(id, ad)
if REQUEST is not None:
return self.manage_main(self, REQUEST)
-Original Message-
From: Toby Dickenson [mailto:[EMAIL PROTECTED]]
Sent: Monday, September 10, 2001 6:28 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: [Zope-dev] Problems with CatalogAware?
On Fri, 31 Aug 2001 15:17:27 -0700, [EMAIL PROTECTED] wrote:
I have a python product that has a class derived from CatalogAware and
Folder. I programmatically add instances of these (1000s of them) on an
automated basis every day in the early morning.
My problem is that whenever I do this, the Catalog is updated with some
problems:
1 - Metadata is skewed: DateTime objects are cataloged, and they end up
with
the wrong date ('2001/01/01') instead of today's date, even though the
actual property contains today's date. The index in question is built from
a property.
2 - Text indexes only get a portion of their text stored in the metadata,
not all of it. The index in question is built from a class method in the
product code.
Appologies if you already know this.
CatalogAware will automatically reindex if an object is added,
deleted, or moved. However it does not automatically reindex if
properties are changed.
It sounds like your index might contain the default (initial) values
for these properties. Do you need to add a call to reindex_object()
after changing them from the defaults?
Toby Dickenson
[EMAIL PROTECTED]
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://lists.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://lists.zope.org/mailman/listinfo/zope-announce
http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Where to send patches?
Michel Pelletier wrote: On Mon, 10 Sep 2001 12:16:51 -0400 Jim Washington [EMAIL PROTECTED] wrote: Hi, All Since the Collector is down, where do we send patches if we are not cvs-authorized? I just discovered a not-too-clever hack to make the Find tab recurse through methods of Z Classes, which the margin of this e-mail is too small to contain. Dude, don't jinx yourself. I'm sure you don't want us to refer to this as Jim Washington's last patch. ;) Ack! I deserve that for playing the cleverness card. Fortunately, I am not planning any duels anytime soon :) The requested change does seem to work, and does not seem to break anything. And it is probably bad to admit that Z Classes are somehow different enough to require special treatment in base Zope code. FWIW, my patch (against FindSupport.py in 2.4.1) is attached. Consume at your leisure. -- Jim Washington *** FindSupport.py.orig Mon Sep 10 11:31:20 2001 --- FindSupport.py Mon Sep 10 11:55:19 2001 *** *** 152,168 if hasattr(obj, 'aq_base'): base=obj.aq_base ! if not hasattr(base, 'objectItems'): return result try:items=obj.objectItems() except: return result try: add_result=result.append except: raise AttributeError, `result` for id, ob in items: ! if pre: p=%s/%s % (pre, id) else: p=id dflag=0 --- 152,179 if hasattr(obj, 'aq_base'): base=obj.aq_base ! if not hasattr(base, 'objectItems') and not base.meta_type == 'Z Class': return result + + if hasattr(base, 'objectItems'): try:items=obj.objectItems() except: return result + if base.meta_type == 'Z Class': + try:items=obj.propertysheets.methods.objectItems() + except: return result + + try: add_result=result.append except: raise AttributeError, `result` for id, ob in items: ! if pre: ! if base.meta_type == 'Z Class': ! p = %s/propertysheets/methods/%s % (pre,id) ! else: ! p=%s/%s % (pre, id) else: p=id dflag=0 *** *** 194,201 ): add_result((p, ob)) dflag=0 ! ! if search_sub and hasattr(bs, 'objectItems'): self.ZopeFind(ob, obj_ids, obj_metatypes, obj_searchterm, obj_expr, obj_mtime, obj_mspec, --- 204,211 ): add_result((p, ob)) dflag=0 ! #small edit here to add the or ! if search_sub and (hasattr(bs, 'objectItems') or bs.meta_type == 'Z Class'): self.ZopeFind(ob, obj_ids, obj_metatypes, obj_searchterm, obj_expr, obj_mtime, obj_mspec,
Re: [Zope-dev] Alternative acquisition workarounds
After much reading, ive found the Chameleon Folder Product, which is more or less what i was looking for. But, unfortunately i could not make it work. Has someone used it? Maybe someone can help me to make something similar? Thanx. Em Thursday 06 September 2001 18:46, you wrote: Hello everyone! This is my first posting to this list, so, excuse me if im asking a question that has already been asked by someone. Ok, lets go to the point: I have the following structure at my site: /-- | --/Template1 | --/header --/footer --/images | --/image1.jpg --/image2.jpg --/image3.jpg | --/Section | --/Template 2 | --/images | --/image1.jpg And I tried using Transparent folders to make documents using the Template2 acquire Images and Methods from the Template1, but when i use a DTML document that references images/something, my document uses the images dir from the Templates2 and ignores that from Templates1. Ive seen an example like this in some acquisition tutorial out there, but it just said that this was hard to implement and shows some example in DTML. I was hoping someone implemented anything like this in a Python product, or if someone has an idea of how this could be implemented in Python. Thanx for your patience. -- Sidnei da Silva X3ng Consultoria e Desenvolvimento Ltda. [EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) -- Sidnei da Silva X3ng Consultoria e Desenvolvimento Ltda. [EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Password encryption--calling on the community
Following the Zope 2.5 plan, I have just added to CVS the capability for user passwords to be encrypted in the standard user folder. Please try it out. If it works correctly there should be no outwardly visible differences. I'm also soliciting the assistance of developers and users of custom user folders (like LDAPUserFolder, LoginManager, GUF, etcUserFolder, NTUserFolder, etc.) We need you to test whether the added feature has any bad effects on your user folder. It's much easier to apply a fix now than it will be after a release. Shane ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Password encryption--calling on the community
Following the Zope 2.5 plan, I have just added to CVS the capability for user passwords to be encrypted in the standard user folder. Please try it out. If it works correctly there should be no outwardly visible differences. I'm also soliciting the assistance of developers and users of custom user folders (like LDAPUserFolder, LoginManager, GUF, etcUserFolder, NTUserFolder, etc.) We need you to test whether the added feature has any bad effects on your user folder. It's much easier to apply a fix now than it will be after a release. Shane P.S. I may have inadvertently sent this twice, please excuse. :-) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Declaring interfaces for Products
=?iso-8859-1?Q?Dario=5FLopez-K=E4sten?= writes: I am making a product using the Interface approach described in the ZDG. As I understand it, Interfaces should expose all methods that provide funtionality for my product, with the possible exception of internal methods used as utility methods in the class itself. Is this correct? You could have different interfaces, targeting different audiences: TTW interfaces, scripting interfaces, programming interfaces. Apart from using security declarations, I want to make some of the methods available thru the web (TTW), and some of the methods not publishable TTW. In order to be able to publish a method TTW, they need to have a docstring, right? There is a project proposal to eliminate this DocString abuse Now, in my interface defintion I want to provide doc-strings for all methods that are exposed (the interface), but not all them are to be publishable TTW. Can I achieve this by using docstrings for my methods in the Interface, but not in the Implementation, or do I need to omit the doc-string in both the Interface and the Implementation? It should be enough to omit the doc string from the implementation. Dieter ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Declaring interfaces for Products
In order to be able to publish a method TTW, they need to have a docstring, right? There is a project proposal to eliminate this DocString abuse :-) sounds nice :-) Now, in my interface defintion I want to provide doc-strings for all methods that are exposed (the interface), but not all them are to be publishable TTW. Can I achieve this by using docstrings for my methods in the Interface, but not in the Implementation, or do I need to omit the doc-string in both the Interface and the Implementation? It should be enough to omit the doc string from the implementation. excellent, thank you Dieter. /Dario ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
