- Zope - Zope lists

Re: [Zope] - How to register an object?
by Amos Latteier 14 Jan '99

14 Jan '99

At 04:57 PM 1/13/99 -0500, Peter J Ulintz wrote: >Hi. >Could you take a minute and help me out? Sure, but I'm taking the liberty of ccing the Zope list so that hopefully others will profit. I hope you don't mind. >So I'm trying to publish an object in the Zope framework. >Here's the object > >person.py: >----------------------------------------------------------- >import DocumentTemplate > >class Person: > "A simple person" > def __init__(self, name): > self.name = name > > index_html=DocumentTemplate.HTMLFile("my_template.dtml") >------------------------------------------------------------ > >The "my_template.dtml" file is exactly the same as in the "Techical >Introduction to Object Publishing" document. Now, I want to publish the >object in the Zope heirarchy using an External Method. I used... > >import_person.py: >----------------------------------------------------------- >import person > >def add_person(self, name = 'John Doe'): > """This method is called by a folder to add a person""" > person=person.Person(name) > if not hasattr(self, name): > setattr(self, name, person) > return "Person added to folder" >----------------------------------------------------------- In general what you are doing is right--creating an objects and installing it in the object hierarchy. Unfortunately, there is a subtle problems with this. The problem is that your person object cannot be stored in the object database since the External Method machinery makes the Person class hard to unpickle. If you were creating Zope objects, or if the Person class existed somewhere else, like in the Shared module, this approach would work. I believe this limitation is mentioned in the External Method documentation. >So, I create an External Method-- ID: addPerson Title: Add Person >Function Name: add_person Python module file: import_person >This creates an external method object in my Zope folder called >"addPerson". If I now go to the browser and type(I'm using the >ZopeHTTPServer)... > >http://141.214.57.234:9673/addPerson?name="Geddy" OK, here's another problem. No need for quotes around Geddy. In fact those quotes are going to cause you problems. >...I get the response, "Person added to folder". But I'm not sure what's >SUPPOSED to happen here. Is the object supposed to magically appear in >the folder? What am I doing wrong? Just typing: >http://141.214.57.234:9673/addPerson >works, but typing >http://141.214.57.234:9673/addPerson?data="bullocks" >gives the same "Person added to folder" message. OK, Zope is doing exactly what you are telling it to do. It is creating an object, installing it in a folder and returning a message. I'm not sure what else you want ;-) If you want a Zope object to appear in the management interface after this, you need to install a Zope object, not just a random object. For an object to be manageable through the web with Zope's interface it must support the Zope Product API. Also installing a Zope Product in a Folder should in general be accomplished with the '_setObject' method, not a plain old 'setattr'. >How do I publish an actual "Geddy" person object, that I can call the >index_html attribute on? Oh, following your suggestion (and the one in >the External Methods documentation on the site), creating a file OK, the essential functioning of the Zope ORB is to allow you to use URLs to traverse the object hierarchy. So if you call myFolder/addperson?data=duke Then your External Method will add an attribute named 'duke' to 'myFolder'. Therefore you should now be able to access this attribute like so myFolder/duke Make sense? To publish an object you point your browser at its URL. >import_person2.py: >-------------------------------------------------------------- > >import person > >def addPerson(self, name='Dufus'): > "return person" > return person.Person(name) >------------------------------------------------------------- > >Trying the same thing gives a "Sorry, th requested document does not >exist" error. The page source doesn't really tell me much there. Ouch! My bad! This method does not *publish* a Person instance, it *returns* a Person instance as a response. So Zope tries to understand the instance as a string and decides that it is not a valid response. (Actually viewing the source of the error page should give you some information about what went wrong. That's how I discovered my mistake.) To actually publish an object, it must be part of the object hierarchy so that Zope can traverse it. Let me give a good example here: The first thing we'll do is create a module to hold our publishable classes. Lets create our own package inside the Shared package. Create a directory inside lib/python/Shared named PeeWee (or use your own name). Next create an empty file __init__.py inside the PeeWee directory. This lets Python know that PeeWee is a package. Now let's create a Python file, PlayHouse.py inside the PeeWee directory. class PlayHouse: "Play house" def index_html(self,game='tag'): "publish the playhouse" return "In the play house we play %s." % game OK, now we have a publishable class that is Zope accessible. Now we need to get an instance of that class into the object hierarchy. Let's use an external method. Create a Python file in Extensions named peewee_utils.py from Shared.PeeWee.PlayHouse import PlayHouse def addPlayHouse(self,id): "Add a playhouse to the current folder" if not hasattr(self,id): setattr(self,id,PlayHouse()) return "playhouse added with id %s" % id else: return "id %s already in use" % id Now create an External Method object to give us access to the addPlayHouse method. Suppose we give our External Method the id 'addPlayHouse', and tell it to use the 'addPlayHouse' method of the 'peewee_utils' module. OK, now we can call our method and install a publishable object in the Zope object hierarchy. myFolder/addPlayHouse?id=myHouse This should return "playhouse added with id myHouse". What the method did was create a PlayHouse instance and make it an attribute of the myFolder object. Now we can access the PlayHouse like this: myFolder/myHouse?game=hide+and+seek Which should return "In the play house we play hide and seek." Note that you will not see any PlayHouse object in the management screen. This is because it is not a Zope Product. However, you can indirectly sense that it is there--if you try to create a Document with id 'myHouse' you will be told that 'myHouse' is already in use. I hope this helps. (I'll update the docs on the Zope site.) >Lastly, trying your External Objects product, and importing the "Person" >object from the person.py, creates on External Object in the Zope folder. >Directing my browser to that brings up the folder's index_html page, no >matter what I put as an arguement. How do I use that? The External Object Product is a container for externally defined publishable objects. You need to tell the External Objects Product the names of the objects you want to publish and the module they reside in. So for example if you define an object 'person' in a module 'Person' in the Extensions directory you need to let External Objects know these facts. Once you have configured your External Object object, access the external objects as sub-objects of the External Objects object like so: myExternalObjects/myObject Note: your published objects may contain further sub-objects. Hope this helps. Object publishing takes a little while to grasp. Don't give up! -Amos P.S. A final note of advice. If you are just learning object publishing--I would advise not trying to plug your objects into the Zope framework right away. Try publishing your own modules with ZopeHTTPServer.py. Get a feel for how to composite objects and how they map to URLs. Then figuring out how to get your objects to play in the Zope framework will make more sense.

2 1

RE: [Zope] - Can we get the docs in FrameMaker format?
by Paul Everitt 14 Jan '99

14 Jan '99

Brad wrote: > So, if I could get the docs in frame .mif, .fm, or .doc > format (I have > FrameMaker 5.5) I'd be a happy person 'cause I could then just print > directly from Frame through clickbook to 4-up sheets. Since we check our Frame files into our CVS repository, when we get a public repository, people will have access to the Frame files. --Paul

1 0

Re: [Zope] - Web On CD stand alone
by Robert OConnor 14 Jan '99

14 Jan '99

I have a number of documents that I plan to convert to HTML and put on CD.. Static docs that don't change much but are searchable. ZOPE might be a good product to ship on CD for WinDoz machines to access documents on the CD with a Browser. ZOPE could allow protection of certain documents to those with THE password. In other words, for example, back issues sold on a per issue basis. The Zope WIN install could be improved so that the ZopeHTTPServer gets installed more automatically and run just by CD insertion. Comments anyone? -bobo connor

4 3

RE: [Zope] - Zope Install Linux (Untar)
by Doug Stanfield 14 Jan '99

14 Jan '99

The Linux download is a tar.gz file. To look at what files exist (a good practice to check directory structure and as a security precaution): 'tar -tvzf Zope-1.9.0-linux2-x86.tar.gz' To uncompress and extract the files: 'tar -xvzf Zope-1.9.0-linux2-x86.tar.gz' do a 'man tar' for more info -Doug- > -----Original Message----- > From: Robert OConnor [mailto:rocon@pivot.net] > Sent: Thursday, January 14, 1999 6:49 AM > To: Zope > Subject: [Zope] - Zope Install Linux (Untar) > > > I've successfully installed ZOPE on windows > Great! > > Now I want to install on my RedHat 5.2 Linux > box. But RH didn't come with 'untar' It > does have /bin/tar but not untar. > > Can some one attach/mail me a copy > at rocon(a)pivot.net? > > Or am I missing something, perhaps > an alternative to untar? > > A consideration: will ZOPE be distributed > in the RPM format in the future? > > Thank you. > > -bobo connor > > >

1 0

- How was www.zope.org created?
by Brad Clements 14 Jan '99

14 Jan '99

The layout of www.zope.org is just what I need. How is it done? I mean, the left-hand side with "news items" list below the menu list above, and the right-hand side with top level menu. The "DHTML Source" button only shows the right-hand-side of the page. Sad but true, I'm a newbie. But frankly, seeing what can be done with Zope/Python I've almost wet my pants with excitement. I just need a hook to get started on. I won't admit to having been a huge proponent of TCL (boo, hiss), or that my only experience with html is MS FrontPage... Thanks for any tips.. Brad Clements, bkc(a)murkworks.com (315)268-1000 http://www.murkworks.com (315)268-9812 Fax netmeeting: ils://ils.murkworks.com ICQ: 14856937 We must come down from our heights, and leave our straight paths, for the byways and low places of life, if we would learn truths by strong contrasts; and in hovels, in forecastles, and among our own outcasts in foreign lands, see what has been wrought upon our fellow-creatures by accident, hardship, or vice. - Richard Henry Dana, Jr. 1836

1 0

- Zope Install Linux (Untar)
by Robert OConnor 14 Jan '99

14 Jan '99

I've successfully installed ZOPE on windows Great! Now I want to install on my RedHat 5.2 Linux box. But RH didn't come with 'untar' It does have /bin/tar but not untar. Can some one attach/mail me a copy at rocon(a)pivot.net? Or am I missing something, perhaps an alternative to untar? A consideration: will ZOPE be distributed in the RPM format in the future? Thank you. -bobo connor

1 0

- Guest Book Example Product....
by Andy Smith 14 Jan '99

14 Jan '99

Hi All, I've just uploaded a sample product to the contributed code page. It implements a guest book where people can leave simple one line messages along with their name and email address. It's main purpose is to be an example of how to create a 'Folderish' product. Each guestbook contains two document objects which may be edited by the user to change the 'look and feel' of the Guestbook. The messages that have been posted are also 'Items' with their own URL and management screens. Similarities in places to Jim's 'sample' product are purely coincidental ;) Cheers, Andy.

1 0

RE: [Zope] - gadfly/zope site example
by Paul Everitt 14 Jan '99

14 Jan '99

Check the permissions on the Gadfly directory in the Zope var directory. --Paul > -----Original Message----- > From: chalaouxf(a)synbio.tpgnet.net [mailto:chalaouxf@synbio.tpgnet.net] > Sent: Wednesday, January 13, 1999 9:21 AM > To: zope(a)zope.org > Subject: [Zope] - gadfly/zope site example > > > Hi All, > > Trying the example from > "http://www.zope.org/Documentation/HowTo/SampleGadfly" I > obtained the following error : > > =============================================== > <!doctype html public "-//w3c//dtd html 4.0 transitional//en"> > <html> > <head> > <meta http-equiv="Content-Type" content="text/html; > charset=iso-8859-1"> > <meta name="GENERATOR" content="Mozilla/4.5 [fr] (WinNT; I) > [Netscape]"> > <title>seminairecreate_table</title> > </head> > <body bgcolor="#FFFFFF" link="#000099" vlink="#555555"> > > <table BORDER=0 CELLSPACING=0 CELLPADDING=2 > WIDTH="100%" > > <tr> > <td ALIGN=LEFT VALIGN=TOP><b>Z SQL Method at > /seminaire </b></td> > </tr> > </table> > > <hr><b>Error, <i>exceptions.IOError</i>:</b> (13, 'Permission > denied')  > <hr><b>SQL used:</b> > <pre>create table zopista (col_a integer, col_b integer)</pre> > > <hr> > </body> >  > </html> > =============================================== > > Bye, FR. > > François-Régis Chalaoux > Bioinformatics Group > Synthélabo Biomoléculaire > 67080 Strasbourg Cedex > FRANCE > Tél : 03 88 60 87 14 > Fax : 03 88 45 90 70 > >

2 1

RE: [Zope] - How was www.zope.org created?
by Paul Everitt 14 Jan '99

14 Jan '99

Brad writes: > The layout of www.zope.org is just what I need. > > How is it done? Every page on the Zope site has three sections: header, body, footer. The header is generated from standard_html_header, which is defined once in the top level folder. The standard_html_header document sets up the HEAD then does the table layout for the left-hand side and the right-hand side, where the left-hand side is the "siderbar". To put in the sidebar, which is logically the context sensitive menu, we merely say  where we want it. This allows each folder to define its own sidebar. In general, though, we don't do that. Rather, we have automated it and just used one sidebar Document in the top folder. How did we automate it? We told it to get the items in the menu from a property of the current folder. The property, sidebar_contents, is of "lines" type, with each item being the definition of the entry in the menu. Warning, hack ahead. Each sidebar item has three pieces of information: the label, the URL, and whether it should be indented. Since the folder property shamefully only allows lines of strings, these pieces of information are separated by a vertical bar | symbol, then a (gag) string.split is done on them. The sidebar document also looks at the PATH_INFO to see if the current URL is on the menu item. Now that TinyTables has been released by Grand Master Flash and the Furious Funk (Ty Sarna with inspiration provided by Kent Polk), there is a much better way to do it. In summary: 1) Have a sidebar that formats the context sensitive menu. 2) Have each folder define the data for the menu. --Paul

2 1

Re: [Zope] - HTMLFile-like class that heeds DTML mod time
by Robin Dunn 14 Jan '99

14 Jan '99

Cool! I was fiddling around last night trying to do the same thing, but none of my attempts were this simple. Thanks! -- Robin Dunn robin(a)AllDunn.com http://AllDunn.com/robin/ Try http://AllDunn.com/laughworks/ for a good laugh. -----Original Message----- From: skip(a)calendar.com <skip(a)calendar.com> To: zope(a)zope.org <zope(a)zope.org> Date: Wednesday, January 13, 1999 6:18 PM Subject: [Zope] - HTMLFile-like class that heeds DTML mod time > >I got tired of having to restart my ZopeHTTPServer every time I twiddled a >DTML file used by a published object, so I wrote the following simple class >that checks the mod time of the DTML file when it's called, and recreates >its HTMLFile instance if necessary. I instantiate it instead of HTMLFile. > > class Template: > def __init__(self, file): > self.file = file > self.template = DocumentTemplate.HTMLFile(self.file) > self.ftime = os.stat(self.file)[stat.ST_MTIME] > > def __call__(self, *args, **kargs): > ftime = os.stat(self.file)[stat.ST_MTIME] > if self.ftime < ftime: > self.ftime = ftime > self.template = DocumentTemplate.HTMLFile(self.file) > return apply(self.template.__call__, args, kargs) > >I'm sure there's probably a simple way to integrate this into >DocumentTemplate.HTMLFile directly, but this seemed easier to me, what with >the mixins and such that are used in DocumentTemplates, and all I really >need are __init__ and __call__ methods. > >Consider this a feature request (I also submitted it to the Zope web site.) > >Skip Montanaro | Mojam: "Uniting the World of Music" http://www.mojam.com/ >skip(a)calendar.com | Musi-Cal: http://concerts.calendar.com/ >518-372-5583 > > > >

1 0