Zope-Dev October 1999

zope-dev@zope.dev

78 participants
141 discussions

help me ZCatalog - searchResults
by sergey2b 26 Oct '99

26 Oct '99

Dear All. Your help in the decision of one problem is necessary to me. What types of inquiries supports searchResults? I know only variant searchResults (name of a field = a required word) If look at def searchResults (self, REQUEST=None, used=None, query_map = {type (regex.compile (")): Query. Regex, type ([]): orify, type ("": Query. String, }, ** kw): There are inquiries type (regex.compile (")): Query. Regex and type ([]): orify. If probably, give me an example how to use these types of inquiries. Whether a way of search ' tes * ' where * any symbol. If it is possible - how can I do it?. How to use inquiry type (regex.compile (")): Query. Regex from dtml? Please, give me an example, what type inquiries supports searchResults And what type of inquiries with use regex can I set Thank to you in advance, Sergay.

2 1

RE: [Zope-dev] Re: Renderable Base ZClass
by Michel Pelletier 25 Oct '99

25 Oct '99

> -----Original Message----- > From: Lalo Martins [mailto:lalo@webcom.com] > Sent: Sunday, October 24, 1999 3:29 PM > To: Dave Wood > Cc: zope-dev(a)zope.org > Subject: [Zope-dev] Re: Renderable Base ZClass > > > On Sun, Oct 24, 1999 at 11:40:05AM -0300, Dave Wood wrote: > > Hi, > > > > More technical view, if anyone cares: > > What Renderable does is basically define a __str__ method, so > that we can control what is displayed when we do <dtml-var obj> > (and obj is of a class derived from Renderable). > > But __str__ is a pure-python feature, so it doesn't get a > context (REQUEST etc). As you've discovered, you cannot pass arguments to __str__, therefore you can't pass REQUEST. You can, however, try to acquire a context by checking yourself for REQUEST: def __str__(self): try: url = self.REQUEST['URL'] except: raise 'No Context', 'I cant acquire!!' This works becuase the instance of your ZClass is an Acquisition.Implicit acquirer. -Michel

1 0

Re: Renderable Base ZClass
by Lalo Martins 24 Oct '99

24 Oct '99

On Sun, Oct 24, 1999 at 11:40:05AM -0300, Dave Wood wrote: > Hi, > > I wrote the ZOPE mailing list with the following: > > ...we have been banging out bugs with the Renderable Base ZClass Product, > but are stuck on one point. We don't know how to pass/initialize a valid > REQUEST object in the class. How is this done?... > > but noone seems to know. I've also tried the #zope IRC channel but no one > seems to use it! > > Have you had any luck with the ZOPE-dev list? Haven't tried yet :-) but you give a good enought definition of the problem, so I'm forwarding this to there. More technical view, if anyone cares: What Renderable does is basically define a __str__ method, so that we can control what is displayed when we do <dtml-var obj> (and obj is of a class derived from Renderable). But __str__ is a pure-python feature, so it doesn't get a context (REQUEST etc). Namely, we would really appreciate to be able to tell the name (url) of the object we're a method of :-) []s, |alo +---- -- I am Lalo of deB-org. You will be freed. Resistance is futile. http://www.webcom.com/lalo mailto:lalo@webcom.com pgp key in the web page Debian GNU/Linux --- http://www.debian.org Brazil of Darkness - http://www.webcom.com/lalo/BroDar

2 1

RE: [Zope-dev] PTK Model
by Michel Pelletier 23 Oct '99

23 Oct '99

> -----Original Message----- > From: Kevin Dangoor [mailto:kid@kendermedia.com] > Sent: Saturday, October 23, 1999 12:45 PM > To: Michel Pelletier; zope-dev(a)zope.org > Subject: Re: [Zope-dev] PTK Model > > > Hi, Michel > > This model does provide some good info about some of the basic PTK > object types and their relationships... I do have a few > questions about > this: > > - Does MFI exist now, or are you going to redo the objects > that exist on the > current zope.org site so that they utilizes the MFI? This looks like two questions in one sentence, so I'll answer them seperately. MFI exists as a skelatal prototype, the current model is much more advanced then the one you see now, in fact MFI has a whole model unto itself. I will post it on Monday. The objects that PTK come with are stock objects, most of which will be 'ports' of the existing zope site objects. They will change in minor ways, ie, they will use MFI, their interfaces will be more consistent, and their behavior will be analyzed (hopefully by all of you!) to see if they can be made more useful. A familiar rhythm I'm looking for is 1) release an alpha, 2) someone points out a problem, 3) that person, using the model, describes exactly how they think it should work. This doesn't mean you have to be a modeler, but you should be able to look at UML and at least be able to say "Class such-and-such defines this method, I think the method should return X". In fact, this doesn't even need UML, you can do this from the source. The model is to make it easer for us all the grasp the big picture. > - Please tell me that the Membership System and Topics are > still planned... > these are really important. Yes they are planned. I didn't include them in this early model. > > - Does the original model file include information about the > attributes you > plan for each of the object types? (I didn't see it in the > HTML version > anywhere) Other than MFI, I have not reached down to that level of detail yet. -Michel

1 0

Re: [Zope-dev] PTK Model
by Kevin Dangoor 23 Oct '99

23 Oct '99

Hi, Michel This model does provide some good info about some of the basic PTK object types and their relationships... I do have a few questions about this: - Does MFI exist now, or are you going to redo the objects that exist on the current zope.org site so that they utilizes the MFI? - Please tell me that the Membership System and Topics are still planned... these are really important. - Does the original model file include information about the attributes you plan for each of the object types? (I didn't see it in the HTML version anywhere) Kevin

1 0

help ZCatalog searchResults
by mk 23 Oct '99

23 Oct '99

1 0

load_site.py patch2 final
by Oleg Broytmann 23 Oct '99

23 Oct '99

Hello! Attached is gzipped source for heavily modified load_site.py. In this latest patch I added capability to parse HTML files the following way: 1) <HEAD></HEAD> parsed and completely stripped off; 2) <TITLE></TITLE> parsed and stored 3) all other tags inside HEAD are stored separately in a long string; 4) <BODY> stripped off and replaced with  5) </BODY> stripped off and replaced with  6) </HTML> stripped off. On uploading to Zope, saved title used as document's title, other saved tags (from HEAD) stored as "loadsite-head" text (multiline) property. To restore the property, you just need to add new (or modify existing) standard_html_header. Add the following between <HEAD> and </HEAD>:  Hey, DigiCool! Would you like to include new version into standard distribution? If no, I'll publish it on my member page, along with short HOW-TO. Oleg. ---- Oleg Broytmann National Research Surgery Centre http://sun.med.ru/~phd/ Programmers don't die, they just GOSUB without RETURN.

1 0

RE: [Zope-dev] Attribute Error
by Rob Page 23 Oct '99

23 Oct '99

> I'm using: > > <INPUT TYPE=FILE NAME=file> Check the FORM tag, does it include: ENCTYPE="multipart/form-data" --Rob

1 0

XMLDocument patch feedback
by Anthony Pfrunder 23 Oct '99

23 Oct '99

Amos / Martijn, I applied your patches to the XML Document product but it didn't appear to fix the problem within VisualZope / XMLWidgets. Below is a traceback and associated information. Products/VisualZope/VZManager.py contains one class (VZmanager) which inherits from: * Products.XMLDocument.XMLDocument and * Products.XMLWidgets.XMLWidgetManager.XMLWidgetManagerBase VZmanager implements the following additional methods: * dorender * prender VZmanager is the superclass for the Form ZClass. This ZClass, when "viewed" (ie via URL or index_html) calls a ZClass method "view" which calls the inherited "dorender" method. When the Form instance is "viewed" the following occurs: ************************** Edited Extract of HTML Error Page ********************************** [snip] Zope has encountered an error while publishing this resource. [snip] Error Type: AttributeError Error Value: _id [snip] Traceback (innermost last): [Viewing a VZ Form instance] File C:\TEMP\Zope\lib\python\ZPublisher\Publish.py, line 214, in publish_module File C:\TEMP\Zope\lib\python\ZPublisher\Publish.py, line 179, in publish File C:\TEMP\Zope\lib\python\Zope\__init__.py, line 201, in zpublisher_exception_hook (Object: ElementWithAttributes) File C:\TEMP\Zope\lib\python\ZPublisher\Publish.py, line 165, in publish File C:\TEMP\Zope\lib\python\ZPublisher\mapply.py, line 160, in mapply (Object: XMLWidgetManagerBase) [call intercepted by VZManager superclass and redirected to Form instance.view()] File C:\TEMP\Zope\lib\python\ZPublisher\Publish.py, line 102, in call_object (Object: XMLWidgetManagerBase) File C:\TEMP\Zope\lib\python\Products\VisualZope\vzManager.py, line 65, in __call__ (Object: XMLWidgetManagerBase) File C:\TEMP\Zope\lib\python\OFS\DTMLMethod.py, line 145, in __call__ (Object: view) [Executing "view" Python Method within Form ZClass] File C:\TEMP\Zope\lib\python\DocumentTemplate\DT_String.py, line 502, in __call__ (Object: view) File C:\TEMP\Zope\lib\python\DocumentTemplate\DT_Util.py, line 321, in eval (Object: dorender(getDocumentElement(), REQUEST)) [Calling inherited "dorender" method located in VZmanager] File <string>, line 0, in ? File C:\TEMP\Zope\lib\python\Products\VisualZope\vzManager.py, line 77, in dorender (Object: XMLWidgetManagerBase) File C:\TEMP\Zope\lib\python\Products\VisualZope\vzManager.py, line 91, in prender (Object: XMLWidgetManagerBase) File C:\TEMP\Zope\lib\python\Products\VisualZope\vzManager.py, line 91, in prender (Object: XMLWidgetManagerBase) File C:\TEMP\Zope\lib\python\Products\VisualZope\vzManager.py, line 93, in prender (Object: XMLWidgetManagerBase) File C:\TEMP\Zope\lib\python\Products\VisualZope\vz.py, line 43, in prender File C:\TEMP\Zope\lib\python\Products\PythonMethod\PythonMethod.py, line 168, in __call__ (Object: prender) (Info: [snip]) [calling Python Method which performs a DOM operation on the data within VZmanager] File <string>, line 15, in prender (Object: ElementWithAttributes) File C:\TEMP\Zope\lib\python\Products\XMLDocument\Node.py, line 429, in appendChild (Object: Manageable) File C:\TEMP\Zope\lib\python\Products\XMLDocument\Node.py, line 396, in removeChild (Object: XMLWidgetManagerBase) AttributeError: (see above) The code for the prender Python Method is: Parameters: self = the widget, manager = the Form instance, node = tag within Form instance, REQUEST # This method renders this widget node by modifying a clone of # the current Form XML tree which contains the widget tag body = REQUEST['clone'].getElementsByTagName('body')[0] head = REQUEST['clone'].getElementsByTagName('head')[0] REQUEST.set('name', node.getAttribute('name')) REQUEST.set('type', self.id) REQUEST.set('widget', self) # Include javascript library for this widget tmp = manager.createElement('script') tmp.setAttribute('src', self.absolute_url()+'/implementation?name='+REQUEST['name']) tmp.setAttribute('language', 'javascript') tmp.appendChild(manager.createTextNode('')) head.appendChild(tmp) ^^^^*********************** head: This object has NO id attribute ******************* [snip] If I change XMLDocument back to the wrapped version (adds aq_* attributes) it works fine. Do you think there is a problem related to the DTML id problem somewhere? Cheers, Anthony Pfrunder

1 0

ZCatalog and indexing DTML methods
by Stuart 'Zen' Bishop 23 Oct '99

23 Oct '99

Greetings. I need to use ZCatalog to index computed values of my ZClass. It seems that ZCatalog will happily call DTML methods and index their output, but the DTML methods are not called with any arguments so cannot do very much. At the moment, I'm having to shadow the output of my DTML methods (eg. return the Id of PARENTS[1] type stuff) in property sheets to achieve the required functionality, but this is ugly. Is this sort of thing possible with ZClasses, or is this where it is worth switching to Python classes? Would it be possible to modify Catalog to do this? I think the necessary section to modify would be recordify in Catalog.py. The first argument to a DTML Method call would just be the object passed to recordify. I'm unsure how to fake up the REQUEST attribute though. Is this the right way to proceed? ___ // Zen (alias Stuart Bishop) Work: zen(a)cs.rmit.edu.au // E N Senior Systems Alchemist Play: zen(a)shangri-la.dropbear.id.au //__ Computer Science, RMIT WWW: http://www.cs.rmit.edu.au/~zen

2 2

← Newer
1
2
3
4
5
6
7
...
15
Older →

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

2000

1999

1998

Zope-Dev October 1999