Zope January 1999

zope@zope.dev

139 participants
394 discussions

passing REQUEST.form to frames
by Hannu Krosing 09 Dec '99

09 Dec '99

What is the correct syntax for passing form data to child frames of a frameset ? I would like to pass form fields that is submitted to frameset to child frames. Is there any alternative built-in syntax to using an ugly construct like this : =& ------------------ Hannu

2 1

- FYI: Zope Roadmap for next two months
by Paul Everitt 23 Jun '99

23 Jun '99

Howdy all. I've attached below a quick snapshot of things happening for Digital Creations and Zope. The roadmap finally allows me to answer some of the questions coming up here in the Zope community. --Paul Paul Everitt Digital Creations paul(a)digicool.com 540.371.6909 Zope Roadmap For about two months I have made attempts to write down a roadmap that described future directions for Zope. I could never find the right format for detailing the items, though. No one likes to go on record making promises. I settled on the following format as a good compromise that allows me plenty of wiggle room. Each of the items below has a number between one and three in front of it. A one means we are quite likely to do it in the next two months. A three means we have done some work on it and are likely to do more work on it, but don't expect too much progress. The easiest way to get us to change priorities, of course, is through consulting. Many of the items in the list are in support of existing consulting projects. I'll start with Digital Creations, as some of the items we are looking at impact the Zope community. o (1) Hire seven more folks. I expect us to have concluded employment contracts with another seven people by the end of February 1999. We are pretty busy on consulting contracts right now and, as you can see, have quite a backlog of Zope work to do. o (1) Get ten case studies online. Just about everybody new to Zope and/or Python wants to see something done with it. We *have* done interesting work, we just need to package it up to make the case studies and testimonials visible. By the way, giving us some good words to put on the website about Zope really, really helps us convince newcomers to try it out, so pitch in! o (1) Relocate offices. By the end of January we will have switched offices as we need a lot more space. Needless to say we have a disruption facing us but we are doing a good job of managing it so far. o (1) Business plan for 1999. There are a couple of trends that are emerging on the scene in 1999, most notably the mainstreaming of open source. We would like to position ourselves to capitalize on these trends. Thus we are reviewing our business plan and having a board vote first week of February. o (1) Start a Zope Hosting Provider program. I have a page mostly finished for a signup and have two companies that have indicated serious interest. The following is a list of initiatives in the Zope area that are on our radar, though some rely on continued funding from consulting projects, which can be tough to predict: o (1) Tabula and indexing structures. We are going to begin a slow process of moving pieces of Tabula into Zope. The Zope 1.10 release will put the BTrees, integer sets, and indexing machinery into Zope. Tabula itself will be available just afterwards for a small audience of those willing to work with us on it. Over time this will mean Zope will scale up much, much more. In the nearterm it allows the Zopespot project to get kicked off. o (1) Start Zopespot. We have been planting seeds for a while to do a "Slashdot" in Zope. I have been working on a requirements document off-and-on for the last two weeks. More importantly, Ken Manheimer was hired to be the shepherd for this project. More to follow in a separate post. o (1) Release overhauled versions of the four main documentation artifacts. We hope to have by the end of this week new, overhauled versions of the Zope Manager's Guide, the DTML guide, and the SQL Methods (formerly Aqueduct) guide. When Tabula makes it out we will publish its documentation. o (1) Zope 1.10 released. Zope 1.10 will include: - BTrees and integer sets - The SearchIndex package which has a number of indexing classes, including classes for field indexes and text indexes. - Property management broken out into a separate mixin - Properties DTML Documents, Images, and Files - Image patches provided by Ty Syrna to allow size attributes - New absolute URL feature to allow images to referred to from different folders more easily - Bug fixes, plus anything else I've forgotten o (1) Relocate zope.org. Starting this week we are relocating the website which has a big fat pipe to the Internet, as well as people more talented than us to look at it. We'll make a separate announcement about this. o (1) Public CVS server. When Ken gets here I imagine he'll move pretty quickly to getting a public repository available using CVS or Perforce. o (2) Confera released. When the machinery from Tabula goes back into Zope we can brush up Confera and release it. Confera provides threaded discussions that include moderation, full-text searching, and more. Documentation was also written for it so we'll brush that off as well. o (1) WebDAV. Brian Lloyd has made quite a bit of progress on WebDAV. Our goal is to get Zope's hat in the ring for WebDAV as soon as realistically possible. o (1) Zope/Medusa with FTP. As you may have seen on Friday, Amos and Jim have worked with Sam to iron out an architecture document for Zope/Medusa. We should have an alpha release this month of Zope/Medusa with PCGI, HTTP, and FTP implemented as Medusa handlers. o (2) A formal Zope query language. Adding a standard query language, such as OQL or XQL, has recently become pretty important. I hope that we will show some progress on this over the next month or two. o (2) Zope2 beta with full concurrency. It is very important that we make progress on the architecture described by Jim's "BoboPOS3alpha1" paper. o (2) XML. Zope is a great fit for XML, even better with the machinery from Tabula going in. We also see XML becoming the basis for other initiatives, such as WebDAV and RDF. However, we just can't squeeze out the time to dive in deep. Rather, we'd love to see more community progress like that which popped up this weekend. o (3) Offer Collector. A good number of people have asked about contracting with us to get the Collector software for tracking bugs reports, feature requests, and more. Thus we might have a Zope-based solution available and packaged that our customers can drop into their sites. o (3) Replication. Being able to copy the contents of a main site to a local site, make changes while offline, then replicate them back up is a compelling opportunity for Zope. And it isn't that unrealistic, as some of the machinery is there already in the undocumented manage_exportHack operation. However, until it pops up on a consulting gig I doubt Digital Creations will return to it. o (3) Progress on "Python Interfaces", http://www.foretec.com/python/workshops/1998-11/dd-fulton-sum.html. Many of the initiatives we start around here seem to cross territory where we wish we had interfaces. Of course I might have forgotten a thing or two here or there. I'm sure you folks will let me know if I have. :^)

2 1

- ZAP for Win32?
by Michael Bernstein 13 May '99

13 May '99

Will there be a ZAP (Zope Apache) package for win32 on the zope site anytime soon? Michael Bernstein.

4 4

- PostgreSQL DA Release
by Maurice Davis 28 Feb '99

28 Feb '99

I've posted a Zope PostgreSQL Database Adapter to the Contrib area of the Zope site. It uses the PyGreSQL-2.2 extension module. Source for the module and sample data are included in the tar file. Please send me any suggested improvements and bug reports. Maury

3 4

- OO paradigm
by Michael Bernstein 09 Feb '99

09 Feb '99

I've been examining Zope with quite a bit of interest for a while now, and I have a question about the basic architecture: The object hierarchy seems to be 'exact', that is, strictly exclusive. No object can appear in more than one branch of the tree. However, In many cases, user oriented design requires several alternative navigation hierarchies, which would require objects to inherit from more than one branch. An example would be an event calendar, where events can be organized chronologicaly ( Years>Months>Days) but also according to an event category heirarchy (All events>entertainment>music>concerts). These heirarchies only intersect at the leaf node of an individual event. Most product catalogs can be profitably organized using multiple heirarchies as well. So how would you do this in Zope? you could of course represent the alternative heirarchies by branching off the bottom of the primary, or as folder properties, but that doesn't seem as elegant or maintainable. perhaps the answer is some sort of 'pseudo heirarchy' object that could be placed at or near the top of the object tree. What do you all think? Michael Bernstein.

7 12

- Authentication - users don't work at all!
by Ross J. Reedstrom 09 Feb '99

09 Feb '99

Hey Zopers - (ehw, that doesn't sound good - what should the collective noun for "those who hack Zope" be?) Anyway - I've just installed 1.9.0 on my Linux box, pawed through some of the docs and examples and am very impressed! We're just in the beginning phases of coding up a Cold Fusion based web/database app, and I'm hoping to do some parallel development under Zope, then cut over to that when everyone sees how much cooler^W more maintainable the Zope version is. My problem right now - I can't get anyone except the "Superuser" and the anonymous role to authenticate! Just like Phil Harris's problem with IIS, but I'm using the ZopeHTTPServer directly (I figured that would be the least hassle) What I've done: Connect as the superuser Go to the management screen Open the User Folder object Add users with 'Manager' role (check that password many many times) Shut down browser/restart (aside: anyone know how to get Netscape to forget it's authentication info without shutting down?) Try connecting again as user get password dialog: "Username for 'Main' at server 'wallace:9673':" And if fails: (logs from [Zopedir]var/server.errors): wallace.ece.rice.edu - - [21/Jan/1999 12:32:10] "GET / HTTP/1.0" 200 - wallace.ece.rice.edu - - [21/Jan/1999 12:32:15] "GET /manage HTTP/1.0" 401 - wallace.ece.rice.edu - - [21/Jan/1999 12:33:14] "GET /manage HTTP/1.0" 401 - wallace.ece.rice.edu - - [21/Jan/1999 12:33:26] "GET /manage HTTP/1.0" 401 - wallace.ece.rice.edu - - [21/Jan/1999 12:33:32] "GET /manage HTTP/1.0" 401 - wallace.ece.rice.edu - - [21/Jan/1999 12:33:47] "GET /manage HTTP/1.0" 401 - wallace.ece.rice.edu - - [21/Jan/1999 12:33:57] "GET /manage HTTP/1.0" 401 - Anyone? Anyone? Ross -- Ross J. Reedstrom, Ph.D., <reedstrm(a)rice.edu> NSBRI Research Scientist/Programmer Computer and Information Technology Institute Rice University, 6100 S. Main St., Houston, TX 77005

1 1

RE: [Zope] - RESPONSE.headers Help needed
by Brian Lloyd 03 Feb '99

03 Feb '99

> To return to an old thread....I've been trying to achieve the > equivalent of > the code below in DTML. Since you can't make assignments in > DTML, I've been > trying the following.... > >  >  > > IE4 opens up a window and looks as if it's about to download > a file, but > then the message ... > > 'The downloaded files is not available. This could be due to > Security or > Language settings or because the server was unable to > retrieve the selected > file'. I've tried text/csv as the Content-Type as well and > get the same > error. > > It also says that it's trying to download the name of the document, > 'displayAll' and not the desired filename, 'phoneBook.csv' > > Anyone any ideas? > > Cheers, > > Andy. I seem to remember Paul finding that IE choked on downloads with Content-Disposition headers -- have you tried using Netscape to download this? We never found a way around IE's problem that I know of, though I believe we found that NS handled the situation correctly... Brian Lloyd brian(a)digicool.com Software Engineer 540.371.6909 Digital Creations http://www.digicool.com

2 1

Zope in Virtual Host on ISP
by Chris Larson 31 Jan '99

31 Jan '99

OK. Here's the deal. Can someone tell me what issues I face trying to install Zope in my ISP-hosted virtual Apache. I have no access to root, and have been through much pain and suffering trying to get the thing installed. Ideally, a step-by-step how-to is what I'm looking for, but I'd welcome anything up to and including "ya can't do that." NOTE: This is not an authentication question. I look forward to the day I'm asked to authenticate. <cha-grin> Alternatively, I could prolly ask the admin to install it for me, but to be honest, I'm not even sure what to ask. I'm relatively comfortable in unix, but haven't dealt with Apache much at all, aside from uploading pages and cgis. Here's hoping there's a simple answer. Thanks much, Chris Larson Changeling, Inc

2 1

AW: [Zope] Thoughts on XMLishkindasorta things
by Carsten Oberscheid 31 Jan '99

31 Jan '99

[Christopher Petrilli] > > Yes I'm being vague, lest the XMLnazis breat me up again... ^^^^^ (can we blame _this_ on the wine? :-| ) > > Anyway, so I've MOSTLY got the 'store' feature working, and here's how > I'm trying to do it... > > > * Create new tag 'store', used like this: > > <?ztml store var foo ?> > I'm glad you liked this one (see below) :^) > > * Introduced the concept of a parameter entity into the parser, which > has its own table for management, seperate (for future use! :-) > > For those unfamiliar with XML things, a parameter entity is actually > slightly different than a regular entity (character entity)... it's > formed thusly: > > %ztml; > > Note the use of the '%' character, rather than the '&' character. My > reading of the standard says that this is the correct use, not the > regular character entity (&ztml; was the proposed one). > I'm sorry, you got this wrong. Parameter entities can only be used in the DTD, while character entities are to be used in the document. Using a character entity is the right way to go. Anyway, as Amos said, the "store" construct _is_ a hack. And not only for esthetic reasons I'm not too happy with it myself. But since what you, Chris, are doing is patching the existing DTML rather than a redesigning it, this should be an acceptable workaround for the attribute problem. In the long run, I agree that DTML should evolve to be fully XML compliant. I don't want to comment on Paul Prescod's XSL-syntax proposal until I know more about XSL (and reread the discussion he mentioned). Anyway, the DTML engine _is_ a (pre-)processor, so on first thought it seems quite "natural" to use PI's here (tempting enough, since these are quite rare animals in Joe Tagger's boring life :-). On the other hand, XSL and other rendering engines are processors as well, so... I think I shut up and think about this some more... Best regards, .co. +------------------------------------------------------- daisy bytes! --------+ Carsten Oberscheid co(a)daisybytes.su.uunet.de digital document processing http://www.pweb.de/daisybytes.su electronic publishing

2 1

Re: [Zope] - Re: Name clashes (PIL vs Zope)...
by Fredrik Lundh 31 Jan '99

31 Jan '99

Christopher G. Petrilli wrote: >Actually, I think one thing that would help (no offense /F) is that >everyone should put their code in packages Oh, that's perfectly fine for new stuff (especially if you don't have to support older Python versions). But in PIL's case, it's simply too expensive to change this at this time. Luckily, the package semantics makes it pretty straight-forward to move an existing library into a package without changing any- thing in the library. It's a little bit tricker with PIL, since it scans the python path looking for file codecs. To be on the safe side, Zope users should make sure to explicitly import the necessary codecs. The following note provides some more info on this: http://www.pythonware.com/library/pil/notes/note03.htm Cheers /F fredrik(a)pythonware.com http://www.pythonware.com

1 0

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

1997

Zope January 1999