- Zope-Dev - Zope lists

PropertySheets.
by Erik Enge 03 Aug '01

03 Aug '01

Hi, why can't I do this, on an instance of a ZClass: self.__class__.propertysheets.get('common').properties.propertyItems() Any hints highly appretiated! :)

1 2

make_request
by Erik Enge 03 Aug '01

03 Aug '01

Hi, a couple of months ago, Chris McDonough tipsed me about a script called make_request.py that set up a fake request. I need this now to be able to write unit tests for CMF applications (which isn't trivial, me don't think - maybe a quasi-framework would be cool?). Does any one know where I can find this script?

3 5

GlobbingLexicon and Support for single-letter terms
by sean.upton＠uniontrib.com 02 Aug '01

02 Aug '01

I figured I would post this to this list, for whoever it might be useful for... I needed to have ZCatalog searches support single letter words in Globbing text indexes in an online classified ad system. I had a need to do searches like 'C programmer' which would need to have the letter C indexed. I had to edit Splitter.c to support this without treating them as stop-words (in addition to supporting numbers, by changing isalpha to isalnum). On top of that, though, I had to make a change to GlobbingLexicon.get() as well. If you try to search on a single letter word, it tries to create a second digram that uses an index of i+1, which doesn't exist, and an 'index out of range' exception occurs. If you have compiled Splitter.c to support words of a length of 1, the following change to GlobbingLexicon.py will actually allow you to search without error. My line number is based upon source from the 2.3.2 source release and may not reflect current source in current releases and/or CVS: Previously line 224 is: digrams.append((pattern[i] + pattern[i+1])) Replacing line 224 with: if (len(pattern) != 1): digrams.append((pattern[i] + pattern[i+1])) Also, if anyone is interested, I parse and extend queries to auto-add wildcards before passing the query to Catalog. This allows me to add wildcards to the end of words appropriately according to their length. I want 'tech' to match 'biotechnology' but I don't want 'C' (as in programmer) to match every word with the letter C in it or even every word with the letter C as it's first character, so I have to be careful about the length. I have it set up so that: - terms with len > 3 --> *[term]* - terms with len of 2 or 3 --> [term]? - terms with len of 1 --> [term] (don't get re-written) def queryExtender(self, query): """ Takes, as input, query for Text index of ZCatalog, and makes it more intelligent by parsing it and rewriting it to include wildcards at the end of words so that we can search sub-words; in other words, a search for something like "engineer" should yield results for "engineer*" so that terms like "engineers" and "engineering" also are Obviously, we have to be careful not to incorrectly parse the query, and we don't want to mess with words that already have wildcards at the end, because you don't want to end up with something like "engineer**" """ ### Define Character Patterns to Strip Out and Split Upon everythingButSearchTerms = '[^A-Za-z0-9*]+' #Regex Pattern ### Create the word list result = re.split(everythingButSearchTerms, query) ### Get rid of empty string elements in the word list try: for i in range(result.count('')): result.remove('') except: pass ### Get rid of boolean operators i=0 #count variable, used for indexing for item in result: if re.search(booleanops, item): result.pop(i) i = i + 1 ### Now, result is a list of just the words that are ### meaningful to the search, but we need to eliminate ### any entries that have wildcards in them, because ### they are likely more specific than our rewrite here asteriskinterm = '(^[*])|([*]$)$' #asterisk at start or end of term i=0 #count variable, used for indexing for item in result: if re.search(asteriskinterm, item): result.pop(i) i = i + 1 ### Now, the list of words in the query we need to modify is ### final, so we can start modifying the queries, one word ### at a time... for item in result: #query = re.sub(item, '*'+item+'*', query, count=1) if (len(item) > 3): query = re.sub(item, item+'*', query, count=1) else: if (len(item) != 1): query = re.sub(item, item+'?', query, count=1) return query Sean ========================= Sean Upton Senior Programmer/Analyst SignOnSanDiego.com The San Diego Union-Tribune 619.718.5241 sean.upton(a)uniontrib.com =========================

1 0

ANNOUNCE: Component architecture chat with Jim and project details
by Brian Lloyd 02 Aug '01

02 Aug '01

Hello all, As some of you know, over the past few months some folks within Zope Corp. have been working on a new Zope component architecture. The new component architecture seeks to make developing for Zope easier by clarifying and simplifying the task of extending Zope. Enough of the preliminary thinking on the new architecture has now been written down to start sharing those ideas and soliciting the input of the community. You can find the materials for this project at: http://dev.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/FrontPage Specifically, the following pages of the project wiki are key to understanding what is being contemplated: - VisionStatement - ComponentArchitectureApproach - ComponentArchitectureOverview - Glossary We are very excited about the possibilities of this approach, but to consider changing Zope development in such a fundamental way we absolutely need meaningful feedback and input from the Zope developer community on this. If you are a Zope developer, please check out the project above and let us know what you think. Additionally, Jim Fulton will be hosting an IRC chat on Friday, August 3rd at 12:00pm EST on the #zope channel of irc.openprojects.net to answer your questions on the proposed component architecture (please be sure to have read the above pages first!). We hope to see many of you there! Brian Lloyd brian(a)zope.com Zope Corporation www.zope.com

1 0

are the print statements in zdaemon.py wise??
by Chris Keyes 02 Aug '01

02 Aug '01

Hi Guys Been looking through zdaemon.py zope_base/lib/python/zdaemon.py There are some print statements left in here and I just thought I would ask if these need reporting or not? Cheers Chris K

3 2

Re: [ZODB-Dev] More CVS shifting
by Ken Manheimer 02 Aug '01

02 Aug '01

This is a followup on a message i originally posted to zope-announce and zodb-dev. I'm transferring the discussion to zope-dev and zodb-dev, since zope-announce is not for discussion, and i expect there are many repository users who subscribe to one of zodb-dev or zope-dev but not both. On Thu, 2 Aug 2001, Jim Fulton wrote: > > new scheme, it will mean having to once again do new checkouts - old > > checkouts will not update. > > Old checkouts will certainly update, but they won't reflect module > changes, because modules *only* affect checkouts. Yes - that's what i meant to say. > > - Modules enable a bit more recipe reuse. For instance, if you > > wanted two different versions of Zope, one with CMF included and > > one without, you could reuse a core Zope module in a ZopePlusCMF > > module. We will be able to compensate, perhaps better, with > > distribution front-ends. > > Please elaborate how symlinks hinder this. If we need distribution > front ends, then we might as well provide distribution front ends to > overcome the module problem. Someone else asked this question in a private conversation, and i came to realize this is an important issue, which i addressed in some detail: First off, i may have been unclear. Symlinks should enable the fundamental goal where you're able to project various elements from the repository into other directories. I know i've used them for this before, just want to verify my recollection and check the edges, as i describe above. There's a limit to how far we can go with this, relative to modules, without some elaboration. It has to do with reusing directories that are populated using symlinks. Using symlinks, the directories getting shared elements actually contain the links to the elements, so in the simplest approach they must have the same populations in any recipe where they're used. (I think we can address that with another layer of indirection using relative symlinks - see below.) The module scheme directly offers some more freedom, here - the weaving is a virtual thing, so that directories populated using modules can be populated differently in different recipes. For example: In the current setup, the Zope-specific parts of the Zope module are woven in from Releases/Zope - i'd call this the skeleton. Various products and packages are projected into that skeleton with further module elaboration. It could be that we'd have a ZopePlusCMF module that wove in the Zope module and then additionally projected the CMF products. With the symlink scheme we would have to have a separate skeleton. In describing the situation i came to realize that we can use relative symlinks to achieve this kind of reuse, with a bit of elaboration: The idea is to have relative-link stubs in the skeletons, which indirect to directories that vary across recipes. For example, the Zope skeleton would have a link for lib/python/Products that points to ../../Products. Then, a few Zope variants would look like so:: Zope/ ==> link to Zope skeleton Products/ ... various products specific to the plain Zope packaging ZopeWithCMF/ ==> link to Zope skeleton Products/ ... various products specific to the Zope + CMF packaging In both cases, the Products link in the Zope skeleton would indirect to the recipe-specific Products dir. Viola. By "distribution front-end" i was (lazily and hazily) referring to some kind of installation mechanism by which people would select the overlays they want to add to their base-line installation - eg, they'd checkout Zope and then checkout the CMF package, in the right place. I'm not sure which of these two approaches is more suitable for which occasions, but i think between them they should be sufficient to our purposes. I can't tell how difficult it is to track my descriptions here - let me know if i can clarify, and if you see pitfalls. Ken klm(a)zope.com

1 0

Fwd: Re: Probs installing Parsed XML
by m.knobloch＠iwm-kmrc.de 02 Aug '01

02 Aug '01

Hello, after unpacking and installing ParsedXML b1 on SuSe Linux / Zope 2.4 / Python 2.1 i get a warning message during restart of ZOPE Init Ambiguous name for method of products.ParsedXML.ManageableDOM.DOMManageable manage_main != manage_DOMTree. It is possible to import XML-Dokuments but the Tree-View or edit crashes. What did i do wrong? Or ist there a workaround? tia from Knobi Manfred Knobloch Institut für Wissensmedien IWM Universität Tübingen Abteilung Medientechnik Konrad Adenauer Str. 40 D-72072 Tübingen -- Karl Anderson kra(a)monkey.org http://www.monkey.org/~kra/

1 0

RE: are print statements in zdaemon.py wise?
by Chris Keyes 02 Aug '01

02 Aug '01

Should have said that it is Zope 2.4.0 :-( oops Sorry Chris K

1 0

Announce: Medusa Status HowTo
by Mario Valente 02 Aug '01

02 Aug '01

Hi For all interested I've put up a Medusa Status HowTo at http://www.zope.org/Members/mvalente/medusastatus It tells you how to make your ZServer display a Medusa status screen to help with debugging. C U! -- Mario Valente

1 0

Cut/Copy/Paste objects programatically between folders
by vmilitaru＠sympatico.ca 01 Aug '01

01 Aug '01

Hi, Could someone give me a hint or "recipe" (better!) on how to use manage_cutObjects() and such. I am developing a Product which uses the Joust package for UI: I want my Product code to add/edit/move/delete objects programmatically inside the object hierarchy (inside the Joust folder). Is there an easier way than to use Zope's routines? For example, I managed to import some pre-cooked package using Zope's manage_importObject(): --------------- from OFS.ObjectManager import ObjectManager manage_addBarForm = PageTemplateFile("www/Bar_add", globals()) def manage_addBar(self, id, title, REQUEST=None): "Create a Bar folder and add it to its parent's folder." catalogus = Bar(id, title) self._setObject(id,catalogus) base_folder = getattr(self, id) # import entire 'images/' folder in one sweep base_folder.manage_importObject('images.zexp') ------------------ This is very practical: I can edit my objects using the ZMI, then make my Product import everything in one sweep. Also, if I want to add individual objects, I do: ------------------ from my_objects import * base_folder._setObject('SomeObject', DTMLDocument(SomeObject, __name__='SomeObject')) # created an Object inside my base folder or base_folder._setObject('images2', MyFolder(id, title)) # # created a folder inside my base folder then images_folder = getattr(base_folder, 'images2') images_folder._setObject('JPGs', MyFolder(id, title)) # this creates a folder inside a folder inside a folder, a.k.a a hierarchy. ----------------- But now I want to cut/copy/paste/delete objects between my different folders. My guess is that I need to import CopyContainer: ------------------- from OFS.CopySupport import CopyContainer ------------------- But then what? How do I use manage_cutObjects() for example? Let's say, using the previous example, that I want to cut&paste 'SomeObject' from 'base_folder' and paste it into the 'JPGs' folder. Regards - Vio

2 1