[Zope-dev] REQUEST considered a string

2000-07-28 Thread Rob Miller
The following DTML method works in Zope 2.1.6, but not in 2.2.0: ("testfs" is a LocalFS product installed in the method's folder) dtml-var standard_html_header dtml-call "REQUEST.set('spec', '*')" dtml-call "REQUEST.set('num_dir_columns', 3)" table dtml-call

[Zope-dev] Re: [Zope-PTK] PROPOSAL: Splitting ZPatterns into two products

2000-07-28 Thread Steve Alexander
"Phillip J. Eby" wrote: Many people have suggested splitting out the PlugIns part of ZPatterns as a seperate product for general Zope use. In addition to this, it is becoming clearer to me as I work on docs, etc., that there really is only one thing left in ZPatterns after you take out

Re: [Zope-dev] Re: [Zope-PTK] PROPOSAL: Splitting ZPatterns into two products

2000-07-28 Thread Chris Withers
Steve Alexander wrote: "Phillip J. Eby" wrote: So, I am thinking perhaps I should split ZPatterns into two products: PlugIns and DataSkins. If 'PlugIns' includes plugins, plugin groups and plugin containers, then that's a pretty good name :-) (If I've missed bits out and the like, please

[Zope-dev] patches to make ZServer's http_request subclassable

2000-07-28 Thread Brian Takashi Hooper
Hi all - I made a couple of patches to ZServer (medusa, actually) to make medusa'a http_request objects subclassable... the motivation is to make customizing medusa / ZServer's logging easier to do just overriding http_request's log() method in a subclass. Patches are attached to this message,

Re: [Zope-dev] Re: [Zope-PTK] PROPOSAL: Splitting ZPatterns into two products

2000-07-28 Thread Steve Alexander
Chris Withers wrote: 'DataSkins' doesn't mean a lot to me as a name :S What components would go into this product? An object that has DataSkin as a base class allows a DataManager to look after its data storage requirements. The DataManager stores all the propertysheets and attributes, and

Re: [Zope-dev] Re: [Zope-PTK] PROPOSAL: Splitting ZPatterns into two products

2000-07-28 Thread Phillip J. Eby
At 09:51 AM 7/28/00 +0100, Chris Withers wrote: Steve Alexander wrote: "Phillip J. Eby" wrote: So, I am thinking perhaps I should split ZPatterns into two products: PlugIns and DataSkins. If 'PlugIns' includes plugins, plugin groups and plugin containers, then that's a pretty good name

Re: [Zope-dev] Re: [Zope-PTK] PROPOSAL: Splitting ZPatternsinto two products

2000-07-28 Thread Chris Withers
"Phillip J. Eby" wrote: DataSkins themselves, Okay, I'm being dumb again, but could someone explain to me how the name DataSkin came about and how it relates to what these objects do? :S That might be, but the PlugIns part isn't really where it should be before it could even be proposed to

RE: [Zope-dev] Stuff hanging off user not in cookies

2000-07-28 Thread R. David Murray
On Tue, 25 Jul 2000, Brian Lloyd wrote: I'm thinking of the dimensions/etc of the edit boxes and the like. I do a lot of work through virtual domains and it's a real pain having to resize that edit box every time I log in through a different domain or on a different computer... Have

Re: [Zope-dev] Re: [Zope-PTK] PROPOSAL: Splitting ZPatterns into two products

2000-07-28 Thread Chris Withers
Steve Alexander wrote: An object that has DataSkin as a base class allows a DataManager to look after its data storage requirements. The DataManager stores all the propertysheets and attributes, and works out what to do and who to notify when things change. Okay, makes sense... There are

Re: [Zope-dev] PROPOSAL: Splitting ZPatterns into two products

2000-07-28 Thread Phillip J. Eby
At 10:22 PM 7/28/00 +0100, Chris Withers wrote: Steve Alexander wrote: There are various types of DataManager in ZPatterns, and the important ones take plug-ins so that you can greatly modify their behaviour. I thought there were only two right now? Technically, there are three - Specialist,

[Zope-dev] New Client.py bug(?) in 2.2.0 affects ZScheduler

2000-07-28 Thread Loren Stafford
In Zope version 2.2.0b3 Client.py calls connect in httplib (in two different places) like this: sock.connect(self.host,self.port) In Zope version 2.2.0 (final) it's like this: sock.connect((self.host,self.port)) In the latter case, Python complains:

[Zope-dev] [Re: [Zope-dev] ZPatterns Documentation]

2000-07-28 Thread Chris Withers
"Phillip J. Eby" wrote: Despite the implications of the bait-and-switch subject line, I have not yet written any substantial amounts of documentation. I have, however, written this: http://www.zope.org/Members/pje/Wikis/ZPatterns/DataSkinsOverview Which was actually exceptionally useful,

Re: [Zope-dev] New Client.py bug(?) in 2.2.0 affects ZScheduler

2000-07-28 Thread Chris Withers
Loren Stafford wrote: Does anyone know what was the motivation for the change in the syntax for the call to connect? To make it Python 2 compatible, but this shouldn't cause these errors since connect is supposed to be able to takea tuple now. Confusedly, Chris

Re: [Zope-dev] [Re: [Zope-dev] ZPatterns Documentation]

2000-07-28 Thread Bill Anderson
Chris Withers wrote: I can't help thinking that a _really_ simple example that _only just_ uses the available features would help to make it real for people like me... Well, I have made a 'News Article' toy from ZPatterns, more so to get a feel for the mechanics than for any 'advantage'

[Zope-dev] Client.py prevents ZScheduler with SSL? (was: Zope.org feedback)

2000-07-28 Thread Loren Stafford
Moving this to zope-dev and changing title... From: "Jim Sanford" [EMAIL PROTECTED] We have no http access to our site. It is a corporate Client Relationship Management, Job Tracking and Order Processing, Production and Tracking system that is accessed from all over the world. I will

[Zope-dev] Membership 0.6.1 available

2000-07-28 Thread Bill Anderson
OK, I have an updated Membership product avalable at http://www.zope.org/Members/Bill/Products/Membership Basically, it fixes the keyword parameter problem, and I've started adding the hooks to eventuall plant a user management interface onto. I just need one crucial piece of the puzzle ... I