Two substantive comments, and some editorial ones.
You write that you are thinking of different schemes for generating
paths and ids. I suggest one of the things you consider is whether
your scheme will work if someone cuts the ZWikiZC and pastes it
somewhere else in the tree.
I'm not sufficien
> ZCatalog would be easier to use if it had a recatalog_object method:
>
> def recatalog_object(self, obj, uid):
> """Adds object to the catalog if not already present.
> Removes old entry first, if already in present."""
> self.uncatalog_object(uid)
> self.cat
Phillip J. Eby wrote:
>
> Would it be an undue hardship to copy these into all the relevant racks or
> customizers, until there is a feature to allow inclusion from another rack
> or customizer?
Not at all. :-)
> Now, I can provide *unfiltered* linkage by direct delegation, but this
> would me
Hello,
I'm trying to do the following:
- documents containing a tree navigation are created dynamically using standard_header
and footer.
- the navigation tree is NOT located in a frame but in a table cell which is reloaded
together with the rest of the page each time a link in that navigation
At 11:04 AM 8/27/00 +0100, Steve Alexander wrote:
>
>I have been putting CatalogTriggers as DataManagers directly in
>Specialists.
>
And this *works*??? None of the "Acquired ... Provider" classes supported
forwarding to an acquired trigger, as far as I can recall. The fact that
it's so bloody
At 10:22 AM 8/27/00 +0100, Steve Alexander wrote:
>
>I've fixed this by adding a test to the start of __set_attr__ of
>DataSkins.py:
>
>def __set_attr__(self,name,val,_v_dm_=_v_dm_):
>+ if name=='id' and val==self.__dict__['id']:
>+ return
>dm = self.__dict__[_v_dm_]
T
OK.. I think I've found a way to do what I want with propertysheets.
I just add a generic attribute provider, or skin script to grab
the attributes out of the propertysheet...
SkinScript to get property from particular property sheet:
WITH self.propertysheets.get('ShopperData') COMPUTE email=g
Steve Alexander wrote:
> Shane Hathaway wrote:
>
> >
> > I was suspicious of the entire method so I wrote a replacement which is
> > based on a new interface available in Zope. I *think* it's correct,
> > but it's a drastic change so it's only in the new PTK and nowhere
> > else. (This is sli
ZCatalog would be easier to use if it had a recatalog_object method:
def recatalog_object(self, obj, uid):
"""Adds object to the catalog if not already present.
Removes old entry first, if already in present."""
self.uncatalog_object(uid)
self.catalog_object(ob
Shane Hathaway wrote:
>
> I was suspicious of the entire method so I wrote a replacement which is
> based on a new interface available in Zope. I *think* it's correct,
> but it's a drastic change so it's only in the new PTK and nowhere
> else. (This is slightly modified from PTK CVS.)
>
>
Zope 2.2.1, lib/python/Products/ZCatalog/Catalog.py
When there is an error uncataloging an object, uncatalogObject()
attempts to log the fact with this line:
LOG('Catalog', ERROR, ('uncatalogObject unsuccessfully '
'attempted to uncatalog an object
Thanks Phillip!
OK. that helped a lot. The problem is that when things don't work
as I expect.. I guess (usually with a high degree of success)
that I am off base. Now I've just been experimenting with
this in a simpler 'dtml-only' way just to clarify how it's
supposed to work.
I created a sim
Phillip Eby wrote:
>
> * We would like to drop support for Specialists directly containing data
> plug-ins. This feature was intended to allow for acquiring shared data
> plug-ins from within Racks, so that common attribute or sheet providers
> could be shared among Racks without copying. In pr
[Phillip J Eby]
>> def retreiveItem(self, name):
>> self.f.write('Creating object for %s\n' % name)
>> return USER(name)
> Your retrieveItem isn't checking to see if the user exists. Also, you
> spelled it "retreive" when the correct spelling is "retrieve".
Yep, as soon as I noticed th
I have a trigger that is a datamanager-plugin for a Customizer folder.
The trigger listens to ADD events.
If the trigger rasies an exception as it is notified that a new DataSkin
object is being added beneath the customizer folder, I get a ZODB error:
2000-08-27T09:25:38 ERROR(200) ZODB Couldn't
Zope 2.2.1, ZPatterns 0-4-1snap1
I can't add a Dataskin-derived ZClass beneath a Customizer Folder any
more.
I think the order of something in the initialization of ZClasses has
changed
in Zope. It appears that the DataSkin's datamanager isn't being found
before __set_attr__ is called for the fi
16 matches
Mail list logo
