Re: [Zope-dev] Replaceable types?
Ivo van der Wijk wrote: Secondly, can someone give me an example of a Replaceable object? Any object that doesn't represent a service-kind-of-thing. The term replaceable is used in the context of acquisition. Making things non-replaceable is a way of providing a particular service (say, a MailHost), and ensuring that this service will not be inadvertantly shadowed by something else (a DMTL Method perhaps) in a higher-up folder. The concept of replaceable isn't needed in Zope 3, as services are kept separate from content. -- Steve Alexander ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] HTTP Traceback Style
* Dieter Maurer [EMAIL PROTECTED] [020316 21:50]: Chris Withers writes: The fact is that the tracebacks should _never_ be appended by some process outside standard_error_message. The tracebacks are very helpful in debug mode. I would like they stay as default in this mode. Dieter Yes. Actually this is absolutely not question. My only intention was, to be able to hide the tracebacks from my users/customers in production mode. Christian -- Christian Theune - [EMAIL PROTECTED] gocept gmbh co.kg - schalaunische strasse 6 - 06366 koethen/anhalt tel.+49 3496 3099112 - fax.+49 3496 3099118 mob. - 0178 48 33 981 reduce(lambda x,y:x+y,[chr(ord(x)^42) for x in 'zS^BED\nX_FOY\x0b']) ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] manage frame change
seb bacon wrote: anyone object to changing the text at in the top ZMI frame to Logged in as user on machine? Or is there a better place to put that info? I find it useful when I've got several windows open to different servers. Would the title bar be a better place (title/title) ? Then you don't even have to dig the body of the window up :-) In fact, how about machine - user, that way you should even be able to get the context from whatever taskbar you have, without even having to resort to finding the window... cheers, Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] HTTP Traceback Style
Dieter Maurer wrote: Chris Withers writes: The fact is that the tracebacks should _never_ be appended by some process outside standard_error_message. The tracebacks are very helpful in debug mode. I would like they stay as default in this mode. As I said, the default (and built in) standard_error_message objects should behave exactly as they did. All I'm saying is that there shouldn't be some external process completely outside an application programmers control (or controllable using some nasty hacky environment variable) that defines this behaviour. We have a wonderful templating language now, and w eshould use it for solving these kinds of problems ;-) cheers, Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Replaceable types?
Ivo van der Wijk wrote: First of all, is allow_dup ever set to true? Probably Does zope support duplicate id's in an ObjectManager anywhere at all? Definitely Secondly, can someone give me an example of a Replaceable object? If a class defines a PUT_factory method, this may be set as replaceable so that someone can override it by dropping a Python Script or External Method called 'PUT_Factory' into the ObjectManager. This is the case for the CVS version of the Skins tool in CMF... cheers, Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] manage frame change
anyone object to changing the text at in the top ZMI frame to Logged in as user on machine? Or is there a better place to put that info? I find it useful when I've got several windows open to different servers. Would the title bar be a better place (title/title) ? Then you don't even have to dig the body of the window up :-) In fact, how about machine - user, that way you should even be able to get the context from whatever taskbar you have, without even having to resort to finding the window... In that vein, how about having the main frame with a title resembling getId: tabname, that's useful if you open lots of those in their separate windows. Florent -- Florent Guillaume, Nuxeo (Paris, France) +33 1 40 33 79 10 http://nuxeo.com mailto:[EMAIL PROTECTED] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Replaceable types?
The current object manager code allows for three kinds of subobjects: unique -- prevents the creation of an object with the same name as one that is in the current object manager or one that is acquired. This is what Steve was talking about. It's signified by the acquired object having a __replaceable__ = Globals.UNIQUE value. not replaceable -- the default. if you ask an object manager to store a subobject of the same name as one it already contains, and the existing object has no __replaceable__ attribute or has a __replaceable__ attribute that == Globals.NOT_REPACEABLE, the object manager raises a BadRequestError. replaceable -- if you ask an object manager to store a subobject of the same name as one it already contains, and the existing contained object's __replaceable__ attribute is set to Globals.REPLACEABLE, the call will succeed and the new object will replace the old one. - C Chris Withers wrote: Ivo van der Wijk wrote: First of all, is allow_dup ever set to true? Probably Does zope support duplicate id's in an ObjectManager anywhere at all? Definitely Secondly, can someone give me an example of a Replaceable object? If a class defines a PUT_factory method, this may be set as replaceable so that someone can override it by dropping a Python Script or External Method called 'PUT_Factory' into the ObjectManager. This is the case for the CVS version of the Skins tool in CMF... cheers, Chris ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) -- Chris McDonoughZope Corporation http://www.zope.org http://www.zope.com Killing hundreds of birds with thousands of stones ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.6 planning - call for contributors!
Are you planning to up the python version to 2.2? Because in that case I'd be happy to put in Authentication support in MailHost. Smtplib.py in 2.1.2 doesn't support authentication. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] ZMI: IE6 TextArea width bug: fix on tap for 2.6?
I was wondering if there was any consensus on how best to fix or compensate for the unfortunate behaviour of IE6 with regards to the width calculation of textarea boxes. For anyone who hasn't seen it, the full-width texareas that are everywhere in the ZMI suddenly started pushing the width out in IE6, causing the horizontal scrollbar to become active, and generally making ZMI editing life miserable. Would it be possible to include in 2.6 (or 2.5.1, even better) a user preference, sitewide configuration setting, or other means of suppressing a few pixels/percent of that default width? I'm loathe to apply a massive search-replace to put 95% in my local ZMI source, and IE6 must be a common enough platform for Zope users to warrant a workaround. I wouldn't hold my breath that MS would fix IE or anything sensible like that. It would be a shame to slow the whole thing down with browser detection logic for this one bug, unless that opened up the door for some of the Javascript/DHTML editors as a per-user preference for editing certain metatypes. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
[Zope-dev] Impact of additional protocols handled by Zope?
I'm curious what the impact on overall performance would be if products eventually came into existence that extended Zope to directly handle additional protocols and their data requirements, primarily intended for low-volume workgroup kind of traffic. Jabber, IMAP and LDAP are the ones that come to mind immediately, since you'd be that much closer to having Zope fulfill a role that MS Exchange really doesn't; inexpensive, easily maintained groupware for small organizations that need custom workflow app development. Is it practical to consider that Zope might extend into other protocols this way, and can it be done with modular products, or does integration require deep Zope modifications (beyond adding a few lines to Z2.py?) Just a hypothetical, I guess. FWIW, it would be really cool to see a general, host-a-protocol-here hook for plugin products as Zope3 takes shape, configuration in the ZMI if the product writer goes that far. Something that would define a standard interface for Zope3 events to respond to signals the protocol handler might generate, and vice-versa. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] manage frame change
seb bacon wrote anyone object to changing the text at in the top ZMI frame to Logged in as user on machine? Or is there a better place to put that info? I find it useful when I've got several windows open to different servers. What does machine mean? The host running the ZEO server? The host running the ZEO client? What about those of us who run multiple ZEO clients on the same machine (multi-cpu, test instances, whatever)... Anthony -- Anthony Baxter [EMAIL PROTECTED] It's never to late to have a happy childhood. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Impact of additional protocols handled by Zope?
Yeah, this is something I'd be very interested in knowing, too. In fact, this particular ability could make or break a community project I'm going to be developing with Zope in the near future. Do you mean like the pluggable access that ZServer provides? I imagine there would also have to be some kind of pass-through backend storage to the actual service layer (like IMAP, for instance). This is definately something I've been thinking about. Getting my gears turning, Eron On Sun, 2002-03-17 at 16:53, Jeff Kowalczyk wrote: I'm curious what the impact on overall performance would be if products eventually came into existence that extended Zope to directly handle additional protocols and their data requirements, primarily intended for low-volume workgroup kind of traffic. Jabber, IMAP and LDAP are the ones that come to mind immediately, since you'd be that much closer to having Zope fulfill a role that MS Exchange really doesn't; inexpensive, easily maintained groupware for small organizations that need custom workflow app development. Is it practical to consider that Zope might extend into other protocols this way, and can it be done with modular products, or does integration require deep Zope modifications (beyond adding a few lines to Z2.py?) Just a hypothetical, I guess. FWIW, it would be really cool to see a general, host-a-protocol-here hook for plugin products as Zope3 takes shape, configuration in the ZMI if the product writer goes that far. Something that would define a standard interface for Zope3 events to respond to signals the protocol handler might generate, and vice-versa. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope ) --- [This E-mail scanned for viruses by Declude Virus] --- [This E-mail scanned for viruses by Declude Virus] ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Impact of additional protocols handled by Zope?
[Eron] Yeah, this is something I'd be very interested in knowing, too. In fact, this particular ability could make or break a community project I'm going to be developing with Zope in the near future. Do you mean like the pluggable access that ZServer provides? I imagine there would also have to be some kind of pass-through backend storage to the actual service layer (like IMAP, for instance). This is definitely something I've been thinking about. [Eron] Getting my gears turning, Eron My thinking is that the protocol(s) that people might develop would be action-interfaces to Zope objects and methods. The canon example is IMAP, I guess. Someone might finish up something like http://www.zope.org/Members/michel/MyWiki/IMAPServer , and access/create/control Zope objects persisted directly in ZODB, using variations on the classes people already have for the various Zope Email Clients. Add Binari's IMAP Plug-In to the ubiquitous Outlook, and you've got a poor-man's Exchange Server*. To get public folder workflow, you'd need to use CMF (or Openflow), but that should change by the time Zope3 takes shape, workflow will apparently be native to Zope. (Can't wait) Jabber (or IRC, etc.) would be a slightly different use case. Jabber.py's maturation might mean that you could have a small number of users conferences authenticated against Zope's users. The users would use normal Jabber clients, but this should make web-chat interfaces very doable, too. A Zope Jabber protocol server might implement active conversations in session memory, and persist to Zope objects in response to a Jabber command. Jabber's logging idioms produce XML documents in the jabber.org implementation, ours would be Zope objects or whatever was needed by the developer. The back-end would be all Zope's turf. As for LDAP, existing LDAP products connect to external LDAP servers. But wouldn't it be useful if Zope's user database, and other folderish resources could be exposed as LDAP, with Zope as the server? A Dynamic DNS protocol handler could pump authenticated user's IP info into the LDAP tree, and so on. I'm probably getting ahead of myself here, its not like python implementations of these sophisticated protocols grow on trees. But they do seem to get started in the python community from time to time, and if Zope offered an easy way to hook a budding protocol implementation in to a mature application server, there might be a lot of can-do attitude to getting them beyond alpha stage. The key would be if the developer could add/delete/configure protocol products as easily as content products. As I said, It wouldn't take much for Zope to be a great Exchange drop-in replacement in your typical small business. It wouldn't really matter that much if python implementations of these protocols didn't have the scalability of their C-based brethren, lots of small Zopes doing big-server work would be a nice thing to develop against. * Better than Exchange, IMHO, because you'd have to be nuts to deploy Exchange or Small Business Manager in a real small business with no on-site IS Manager to handle backups or Active Directory admin duties. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://lists.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://lists.zope.org/mailman/listinfo/zope-announce http://lists.zope.org/mailman/listinfo/zope )
