[Zope] Re: ImageFile weirdness? (addendum)
Jürgen Herrmann wrote: btw. i'll learn to formulate my questions better... the actual question way back then should have read (and not more): who (which method) is responsible for delivering an ImageFile instances content when called, as index_html obviously is NOT called? The publisher chooses what method to publish, and it usually chooses index_html. You did something which made the publisher not do that... Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: ImageFile weirdness?
Jürgen Herrmann wrote: to not clutter the zodb-dev list, i'll write you personally... It's what the list is here for, please keep CC'ing it or you're unlikely to get a response in the future... arent't these two code snippets doing the same? class MyClass: myTemplate = PageTemplateFile(...) and: class MyClass: def initTemplates(self): myTemplate = PageTemplateFile(...) setattr(self.__class__, 'myTemplate', myTemplate) # calling initTemplates() once at startup. Almost certainly not. I have no idea where 'self' in your second example comes from, but I'd almost bet it isn't what you expect... i'm actually doing this since long, That doesn't make it right ;-) because i initialize page template files found in a certain directory by calling initTemplates() once on zope startup. this way i don't have to add a line for each template, the code simply iterates over all .pt files in the directory... Interesting, but there are likely to be problems with it. Not least of which: how are you adding security declarations for those new methods? actually i have fixed my initial problem by replacing ImageFile with ExternalFile, which behaves differently and sets the correct content- type headers if it has a content_type property. That doesn't sounds like such a hot idea. My understanding was that ExternalFile was for storing _content_ files on the filesystem... cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] TypeError: unpack non-sequence. RemoteUserFolder?
Hello, I made a copy of a live Zope-instance behind a webserver to my PC for testing purposes. I just copied the files in 'var' and 'Products' and changed the folders in zopectl. I am also running the same Zope version (2.8.0) as on the remote server and with the same structure: Root Folder |_ ... |_ acl_users (User Folder) |_ middelen |_ acl_users (Remote User Folder) |_ ... |_ ... When I try to log in to http://localhost:8080/middelen I get a 'TypeError: unpack non-sequence' instead of a login-prompt. Logging in to http://localhost:8080/manage does work. Below is the entry from the middelen/error_log: Time2006/03/02 13:22:49.932 GMT+1 User Name (User Id) Anonymous User (None) Request URL http://localhost:8080/middelen/index_html Exception Type TypeError Exception Value unpack non-sequence Traceback (innermost last): * Module ZPublisher.Publish, line 104, in publish * Module ZPublisher.BaseRequest, line 445, in traverse * Module Products.RemoteUserFolder.RemoteUserFolder, line 244, in validate TypeError: unpack non-sequence REQUEST form cookies lazy items SESSION bound method SessionDataManager.getSessionData of Products.Sessions.SessionDataManager.SessionDataManager object at 0x412b2f2c other TraversalRequestNameStack [] URL 'http://localhost:8080/middelen/index_html' SERVER_URL 'http://localhost:8080' PUBLISHED OFS.DTMLMethod.DTMLMethod object at 0x414f446c ACTUAL_URL 'http://localhost:8080/middelen' URL0http://localhost:8080/middelen/index_html URL1http://localhost:8080/middelen URL2http://localhost:8080 BASE0 http://localhost:8080 BASE1 http://localhost:8080 BASE2 http://localhost:8080/middelen BASE3 http://localhost:8080/middelen/index_html environ HTTP_ACCEPT 'text/xml,application/xml,application/xhtml+xml,text/html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5' HTTP_ACCEPT_CHARSET 'ISO-8859-1,utf-8;q=0.7,*;q=0.7' HTTP_USER_AGENT 'Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050925 Firefox/1.0.4 (Debian package 1.0.4-2sarge5)' SERVER_NAME '0.0.0.0' GATEWAY_INTERFACE 'CGI/1.1' channel.creation_time 1141302169 SERVER_SOFTWARE 'Zope/(Zope 2.8.0-final, python 2.3.5, linux2) ZServer/1.1' REMOTE_ADDR '127.0.0.1' HTTP_ACCEPT_LANGUAGE'nl,en-us;q=0.7,en;q=0.3' SCRIPT_NAME '' REQUEST_METHOD 'GET' HTTP_HOST 'localhost:8080' HTTP_KEEP_ALIVE '300' SERVER_PORT '8080' SERVER_PROTOCOL 'HTTP/1.1' PATH_TRANSLATED '/middelen' CONNECTION_TYPE 'keep-alive' HTTP_ACCEPT_ENCODING'gzip,deflate' PATH_INFO '/middelen' Does anyone know what the problem might be? Kind regards, Leandros van den Berg The Netherlands ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] How to specify caching for ZSQL methods on file system
I have some ZSQL methods written on the file system using FSDV. In ZMI I can not find the 'Advanced' tab usually available for ZSQL methods in ZODB for specifying the caching properties of the ZSQL method. Can anyone give some clues as how to do this for ZSQL on FSDV? I suppose I might need to write some *.metadata file to specify these properties using FSDV? -- Hong Yuan 大管家网上建材超市 装修装潢建材一站式购物 http://www.homemaster.cn ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] TypeError: unpack non-sequence. RemoteUserFolder?
On 3/2/06, leandros van den berg [EMAIL PROTECTED] wrote: When I try to log in to http://localhost:8080/middelen I get a 'TypeError: unpack non-sequence' instead of a login-prompt. Logging in to http://localhost:8080/manage does work. [...] Traceback (innermost last): * Module ZPublisher.Publish, line 104, in publish * Module ZPublisher.BaseRequest, line 445, in traverse * Module Products.RemoteUserFolder.RemoteUserFolder, line 244, in validate (The above text is the traceback, the other information is not really relevant). The problem appears to be in the RemoteUserFolder product there; perhaps the Product authors can assist you there. look for contact information ith the Products/RemoteUserFolder directory. -- Martijn Pieters ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] How to specify caching for ZSQL methods on file system
On 3/2/06, Yuan HOng [EMAIL PROTECTED] wrote: Can anyone give some clues as how to do this for ZSQL on FSDV? I suppose I might need to write some *.metadata file to specify these properties using FSDV? You must specify the cache settings in the .zsql file itself, using a dtml-comment block at the top. Here is an example: dtml-comment title: Retrieve the per_id of a given uid connection_id: portal_cvix arguments: uid cache_time: 10 /dtml-comment 'cache_time: 10' sets the caching time to 10 seconds. -- Martijn Pieters ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] How to specify caching for ZSQL methods on file system
You are close ;-) The info goes into a dtml-comment block at the start of the file. dtml-comment title: Foo arguments: foo bar max_rows: 1000 max_cache: 100 cache_time: 60 /dtml-comment ... Stefan On 2. Mär 2006, at 15:15, Yuan HOng wrote: I have some ZSQL methods written on the file system using FSDV. In ZMI I can not find the 'Advanced' tab usually available for ZSQL methods in ZODB for specifying the caching properties of the ZSQL method. Can anyone give some clues as how to do this for ZSQL on FSDV? I suppose I might need to write some *.metadata file to specify these properties using FSDV? -- Hong Yuan -- Anything that happens, happens. --Douglas Adams ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Acquisition not working as expected
Hello,
Roman Klesel schrieb:
I can call this method on whatever folder inside the product instance I
want, it will always return the id of the
product and not the id of the product I call it on.
In order to make my problem more obvious I created a minimal product. See
attachmet.
It displays exactly the problem I'm facing:
A method in the base class that returns self.id, returns the id of the base
class on all subfolders it is called.
Code:
__doc__=This is Minimal
__version__='0.1'
from Globals import InitializeClass, Persistent
from Products.PageTemplates.PageTemplateFile import PageTemplateFile
from AccessControl import ClassSecurityInfo
from Acquisition import Implicit
from OFS.ObjectManager import ObjectManager
from OFS.SimpleItem import SimpleItem
import OFS
class minimal(Persistent,Implicit,ObjectManager,SimpleItem):
minimal object
security = ClassSecurityInfo()
meta_type = 'minimal'
def __init__(self, id):
initialise a new instance of Minimal
self.id = id
index_html=PageTemplateFile('zpt/index.html',globals())
security.declarePublic('sayHello')
def sayHello(self):
just says hello
return 'Hello'
def showId(self):
return self.id
def manage_addMinimal(self, REQUEST=None):
Add a Minimal to a folder.
self._setObject('minimal_id', minimal('minimal_id'))
min_obj = getattr(self,'minimal_id')
min_obj.manage_addFolder('tfolder')
if REQUEST is not None:
try:
destURL=self.DestinationURL()
except:
destURL=REQUEST['URL1']
REQUEST.RESPONSE.redirect(destURL+'/manage_main')
return ''
InitializeClass(minimal)
Any ideas anyone?
Greetings Roman
minimal.tar.gz
Description: GNU Zip compressed data
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] (microsoft) webdav and zope 2.8.4
I'm trying to access a zope site via webdav on port 8181. Dreamweaver works ok, but the client in winXP do not want to connect with error: The folder you entered does not seem to be valid. Please choose another. the traceback on zope is: 2006-03-02T15:48:41 ERROR Zope.SiteErrorLog http://www.hf.ntnu.no:8181/_vti_inf.html Traceback (most recent call last): File /var/zope/zope284/lib/python/ZPublisher/Publish.py, line 104, in publish object=request.traverse(path, validated_hook=validated_hook) File /var/zope/zope284/lib/python/ZPublisher/BaseRequest.py, line 316, in traverse else: return response.forbiddenError(entry_name) File /var/zope/zope284/lib/python/ZPublisher/HTTPResponse.py, line 643, in notFoundError Sorry, the requested resource does not exist. + NotFound: (Zope errormessage) -- 2006-03-02T15:48:41 ERROR Zope.SiteErrorLog http://www.hf.ntnu.no:8181/_vti_bin Traceback (most recent call last): File /var/zope/zope284/lib/python/ZPublisher/Publish.py, line 104, in publish object=request.traverse(path, validated_hook=validated_hook) File /var/zope/zope284/lib/python/ZPublisher/BaseRequest.py, line 316, in traverse else: return response.forbiddenError(entry_name) File /var/zope/zope284/lib/python/ZPublisher/HTTPResponse.py, line 643, in notFoundError Sorry, the requested resource does not exist. + NotFound: (zope errormessage) -- -- Einar Næss Jensen http://einar.nidelven-it.no/einarblog http://www.homemade.no tlf: +47 90990249 (\__/) (='.'=)This is Bunny. Copy and paste bunny into your ()_()signature to help him gain world domination. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] (microsoft) webdav and zope 2.8.4
On 2 Mar 2006, at 14:50, Einar Næss Jensen wrote: I'm trying to access a zope site via webdav on port 8181. Dreamweaver works ok, but the client in winXP do not want to connect with error: The folder you entered does not seem to be valid. Please choose another. If you're trying to use the M$ WebFolder-stuff you might as well give up immediately. It simply does not work right. jens ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Re: (microsoft) webdav and zope 2.8.4
On 3/2/06, Einar Næss Jensen [EMAIL PROTECTED] wrote: I'm trying to access a zope site via webdav on port 8181. Dreamweaver works ok, but the client in winXP do not want to connect with error: The folder you entered does not seem to be valid. Please choose another. And the question is: What may I do to enable microsoft client to talk to my zope server? I want to transfer a large amount of images into the zodb, and need an easy way of doing this (from windows). -- Einar Næss Jensen http://einar.nidelven-it.no/einarblog http://www.homemade.no tlf: +47 90990249 (\__/) (='.'=)This is Bunny. Copy and paste bunny into your ()_()signature to help him gain world domination. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Re: (microsoft) webdav and zope 2.8.4
On 3/2/06, Einar Næss Jensen [EMAIL PROTECTED] wrote:
On 3/2/06, Einar Næss Jensen [EMAIL PROTECTED] wrote:
I'm trying to access a zope site via webdav on port 8181. Dreamweaver
works ok, but the client in winXP do not want to connect with error:
The folder you entered does not seem to be valid. Please choose another.
And the question is: What may I do to enable microsoft client to talk
to my zope server?
I want to transfer a large amount of images into the zodb, and need an
easy way of doing this (from windows).
Check this http://www.zope.org/Collectors/Zope/1441
Then apply the following patches to Zope/lib/python/webdav/Resource.py :
diff -c Resource.py Resource.py-patched
*** Resource.py Thu Mar 2 16:37:27 2006
--- Resource.py-patched Thu Mar 2 16:37:25 2006
***
*** 71,76
--- 71,77
if not hasattr(response, '_server_version'):
response.setHeader('Connection', 'close')
response.setHeader('Date', rfc1123_date(), 1)
+ response.setHeader('MS-Author-Via', 'DAV')
# HTTP Range support
if HTTPRangeInterface.isImplementedBy(self):
Then the following to Resource.py :
bash-3.00$ diff -c Resource.py Resource.py-patched
*** Resource.py Thu Mar 2 16:37:27 2006
--- Resource.py-patched Thu Mar 2 16:37:25 2006
***
*** 71,76
--- 71,77
if not hasattr(response, '_server_version'):
response.setHeader('Connection', 'close')
response.setHeader('Date', rfc1123_date(), 1)
+ response.setHeader('MS-Author-Via', 'DAV')
# HTTP Range support
if HTTPRangeInterface.isImplementedBy(self):
Works for me with Office 2003 products.
PS: Just noticed Tres' comment about comming up with a patch which
makes the header
addition configurable. I'll try do that on my next Zope upgrade.
Regards,
Patrick.
___
Zope maillist - Zope@zope.org
http://mail.zope.org/mailman/listinfo/zope
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] (microsoft) webdav and zope 2.8.4
Jens Vagelpohl wrote at 2006-3-2 14:53 +: ... If you're trying to use the M$ WebFolder-stuff you might as well give up immediately. It simply does not work right. We are using it -- quite successfully :-) We had to fix some bugs in Zope's WebDAV support, e.g. properties may not be pure ASCII. Zope did not recode them into UTF-8. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] TypeError: unpack non-sequence. RemoteUserFolder?
leandros van den berg wrote at 2006-3-2 14:13 +0100: ... Below is the entry from the middelen/error_log: Time 2006/03/02 13:22:49.932 GMT+1 User Name (User Id)Anonymous User (None) Request URLhttp://localhost:8080/middelen/index_html Exception Type TypeError Exception Valueunpack non-sequence Traceback (innermost last): * Module ZPublisher.Publish, line 104, in publish * Module ZPublisher.BaseRequest, line 445, in traverse * Module Products.RemoteUserFolder.RemoteUserFolder, line 244, in validate TypeError: unpack non-sequence You look at line 244 of RemoteUserFolder.py where the value comes from that should be a sequence but is not. -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Acquisition not working as expected
Roman Klesel wrote at 2006-3-2 08:13 +0100: ... I can call this method on whatever folder inside the product instance (instance of the base class ZLTMS) I want, it will always return the id of the instace of the base class (where the method is defined) and not the id of the object (Folder object or File object) This is how acquistion works (and should work): When you acquire a method, the self this method is called with is usually *NOT* the object acquisition is applied on. If you think about it, you will recognize that this must be the case: For any method m of class C, its first argument *MUST* be a C instance. If you acquire the method m starting from o, then o may have a completely different class then m. In your case, the method test3 is not defined by Folder but by what you call your product instance (still a wrong term!). Therefore, its self is necessarily an instance of your product (I keep your wrong term). And self.getId() gives (consequently) its (and not the Folder's) id. You cannot do with acquisition what you want to do... -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] (microsoft) webdav and zope 2.8.4
Einar Næss Jensen wrote at 2006-3-2 15:50 +0100: I'm trying to access a zope site via webdav on port 8181. Dreamweaver works ok, but the client in winXP do not want to connect with error: The folder you entered does not seem to be valid. Please choose another. the traceback on zope is: 2006-03-02T15:48:41 ERROR Zope.SiteErrorLog http://www.hf.ntnu.no:8181/_vti_inf.html ... NotFound: (Zope errormessage) Zope will refuse to traverse to any object the id of which starts with _. For some unknown reason, you try to traverse to such an object. The error messages of MS WebDAV are completely horrible: you always get the same error message independently of what goes wrong I had to use different WebDAV clients or even use TCP loggers to analyse such cases. In all cases, Zope was to blame (it failed to recode property values with non ascii content (generating invalid XML) and its URL quoting was wrong) -- but a better error message from MS WebDAV had significantly facilitated the problem analysis... -- Dieter ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] (microsoft) webdav and zope 2.8.4
On 2 Mar 2006, at 18:35, Dieter Maurer wrote: Jens Vagelpohl wrote at 2006-3-2 14:53 +: ... If you're trying to use the M$ WebFolder-stuff you might as well give up immediately. It simply does not work right. We are using it -- quite successfully :-) We had to fix some bugs in Zope's WebDAV support, e.g. properties may not be pure ASCII. Zope did not recode them into UTF-8. Are those fixes available somewhere, maybe as a patch attached to a collector issue? jens ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope] Zed should stand for Zope Extension Distribution
Title: Zed should stand for Zope Extension Distribution Over at the Zope-Dev mailing list, Jim Fulton (the inventor of Zope) is talking about a new line of software called Zed. It would consist of those parts of Zope 3 which can be called independently of the Zope/twisted server. I do not wish to post on the Zope-Dev list because I am not a Zope developer. As an ordinary user of 2.6 (goodbyejim.com) I do wish to comment here. Zed should stand for Zope Extensions Distribution, because it permits Python developers to extend their applications with Zope technologies. That way the brand name of Zope would be protected. Remember when Coke had New Coke and Coke Classic? It was careful to keep the word Coke in both drinks. It would harm Zope if people who used the ZODB, for instance, thought that they were not using Zope. Rather, they should think that they are using Zope, but simply the ZED, Zope Extension Distribution. ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zed should stand for Zope Extension Distribution
Mark, Jonathan (Integic) schrieb: Over at the Zope-Dev mailing list, Jim Fulton (the inventor of Zope) is talking about a new line of software called Zed. It would consist of those parts of Zope 3 which can be called independently of the Zope/twisted server. please be carefull on inventing of brand-like acronyms. I believe Zed has been taken. And not for the good stuff... Regards Tino ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Zed should stand for Zope Extension Distribution
--On 2. März 2006 23:02:13 +0100 Tino Wildenhain [EMAIL PROTECTED] wrote: Mark, Jonathan (Integic) schrieb: Over at the Zope-Dev mailing list, Jim Fulton (the inventor of Zope) is talking about a new line of software called Zed. It would consist of those parts of Zope 3 which can be called independently of the Zope/twisted server. please be carefull on inventing of brand-like acronyms. I believe Zed has been taken. And not for the good stuff... Fixing Zope bugs instead of inventing new names would be a better investment of personal time :-) -aj pgpLjmvdBDAZD.pgp Description: PGP signature ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
Re: [Zope] Acquisition not working as expected
+---[ Roman Klesel ]-- | Hello, | | Roman Klesel schrieb: | I can call this method on whatever folder inside the product instance I want, it will always return the id of the | product and not the id of the product I call it on. | | In order to make my problem more obvious I created a minimal product. See attachmet. | | It displays exactly the problem I'm facing: | | A method in the base class that returns self.id, returns the id of the base class on all subfolders it is called. That's the way acquisition works. I'm not sure why you want this, since everything you're adding has an id already, so there's no need to acquire any method to get the id. Perhaps if you describe the problem you're trying to solve, we can actually help you. -- Andrew Milton [EMAIL PROTECTED] ___ Zope maillist - Zope@zope.org http://mail.zope.org/mailman/listinfo/zope ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope-dev )
[Zope-Checkins] SVN: Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py some cleanup
Log message for revision 65734:
some cleanup
Changed:
U
Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py
-=-
Modified:
Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py
===
---
Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py
2006-03-02 16:03:42 UTC (rev 65733)
+++
Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py
2006-03-02 16:16:06 UTC (rev 65734)
@@ -1,14 +1,18 @@
# Common Engine for Zope3-ZPT-in-Zope-2
+from GlobalTranslationService import getGlobalTranslationService
from zope.tales.tales import ExpressionEngine
from zope.tales.expressions import PathExpr, StringExpr, NotExpr, DeferExpr,
SubPathExpr
from zope.tales.expressions import SimpleModuleImporter, _marker
from zope.tales.pythonexpr import PythonExpr
-from zope.tales.tales import _valid_name, _parse_expr, NAME_RE, Undefined
+from zope.tales.tales import _valid_name, _parse_expr, NAME_RE, Undefined,
Context
+from zope.i18n import translate
+GTS = getGlobalTranslationService()
+
def BoboTraverseAwareSimpleTraverse(object, path_items, econtext):
a slightly modified version of zope.tales.expressions.simpleTraverse()
that interacts correctly with objects implementing bobo_traverse().
@@ -51,21 +55,24 @@
break
add(SubPathExpr(path, traverser, engine)._eval)
-
-from zope.tales.tales import Context
-
-
-from zope.i18n import translate
-
class Context(Context):
def translate(self, msgid, domain=None, mapping=None, default=None):
-# fix that
-return msgid
-#return translate(msgid, domain, mapping,
-# context=context, default=default)
+#import pdb
+#pdb.set_trace()
+return GTS.translate(msgid, domain, mapping,
+ context=self.contexts['context'], default=default)
+def translate(self, domain, msgid, mapping=None,
+ context=None, target_language=None, default=None):
+if context is None:
+context = self.contexts.get('here')
+return getGlobalTranslationService().translate(
+domain, msgid, mapping=mapping,
+context=context,
+default=default,
+target_language=target_language)
class ExpressionEngine(ExpressionEngine):
___
Zope-Checkins maillist - Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py added ZPL
Log message for revision 65738: added ZPL Changed: U Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py -=- Modified: Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py === --- Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py 2006-03-02 16:32:30 UTC (rev 65737) +++ Zope/branches/ajung-final-zpt-integration/lib/python/Products/PageTemplates/Engine.py 2006-03-02 16:46:47 UTC (rev 65738) @@ -1,5 +1,16 @@ +## +# +# Copyright (c) 2002 Zope Corporation and Contributors. All Rights Reserved. +# +# This software is subject to the provisions of the Zope Public License, +# Version 2.1 (ZPL). A copy of the ZPL should accompany this distribution. +# THIS SOFTWARE IS PROVIDED AS IS AND ANY AND ALL EXPRESS OR IMPLIED +# WARRANTIES ARE DISCLAIMED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED +# WARRANTIES OF TITLE, MERCHANTABILITY, AGAINST INFRINGEMENT, AND FITNESS +# FOR A PARTICULAR PURPOSE +# +## -# Common Engine for Zope3-ZPT-in-Zope-2 from GlobalTranslationService import getGlobalTranslationService ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Products.Five/branches/philikon-local-components/ Move site manager adapter and subscriber configuration (IOW, the useful stuff
Log message for revision 65741: Move site manager adapter and subscriber configuration (IOW, the useful stuff in Five.site) to Five.component. Changed: U Products.Five/branches/philikon-local-components/component/__init__.py U Products.Five/branches/philikon-local-components/component/configure.zcml U Products.Five/branches/philikon-local-components/site/configure.zcml U Products.Five/branches/philikon-local-components/site/localsite.py -=- Modified: Products.Five/branches/philikon-local-components/component/__init__.py === --- Products.Five/branches/philikon-local-components/component/__init__.py 2006-03-02 19:04:58 UTC (rev 65740) +++ Products.Five/branches/philikon-local-components/component/__init__.py 2006-03-02 20:42:25 UTC (rev 65741) @@ -30,6 +30,23 @@ import zope.app.component.hooks zope.app.component.hooks.setHooks() +def siteManagerAdapter(ob): +An adapter * - ISiteManager. + +This is registered in place of the one in Zope 3 so that we lookup +using acquisition instead of ILocation. + +current = ob +while True: +if ISite.providedBy(current): +return current.getSiteManager() +current = getattr(current, '__parent__', aq_parent(aq_inner(current))) +if current is None: +# It does not support acquisition or has no parent, so we +# return the global site +return getGlobalSiteManager() + + class LocalSiteHook(ExtensionClass.Base): def __call__(self, container, request): Modified: Products.Five/branches/philikon-local-components/component/configure.zcml === --- Products.Five/branches/philikon-local-components/component/configure.zcml 2006-03-02 19:04:58 UTC (rev 65740) +++ Products.Five/branches/philikon-local-components/component/configure.zcml 2006-03-02 20:42:25 UTC (rev 65741) @@ -1,6 +1,23 @@ configure xmlns=http://namespaces.zope.org/zope; xmlns:browser=http://namespaces.zope.org/browser; + adapter + for=* + provides=zope.component.interfaces.IComponentLookup + factory=.siteManagerAdapter + / + + subscriber + for=zope.app.component.interfaces.ISite + zope.app.publication.interfaces.IBeforeTraverseEvent + handler=zope.app.component.site.threadSiteSubscriber + / + + subscriber + for=zope.app.publication.interfaces.IEndRequestEvent + handler=zope.app.component.site.clearThreadSiteSubscriber + / + browser:page for=OFS.interfaces.IObjectManager name=components.html Modified: Products.Five/branches/philikon-local-components/site/configure.zcml === --- Products.Five/branches/philikon-local-components/site/configure.zcml 2006-03-02 19:04:58 UTC (rev 65740) +++ Products.Five/branches/philikon-local-components/site/configure.zcml 2006-03-02 20:42:25 UTC (rev 65741) @@ -2,28 +2,11 @@ xmlns:browser=http://namespaces.zope.org/browser; adapter - for=* - provides=zope.component.interfaces.ISiteManager - factory=.localsite.siteManagerAdapter - / - - adapter for=zope.app.site.interfaces.ISite provides=.interfaces.IFiveUtilityRegistry factory=.utility.SimpleLocalUtilityRegistry / - subscriber - for=zope.app.component.interfaces.ISite - zope.app.publication.interfaces.IBeforeTraverseEvent - handler=zope.app.component.site.threadSiteSubscriber - / - - subscriber - for=zope.app.publication.interfaces.IEndRequestEvent - handler=zope.app.component.site.clearThreadSiteSubscriber - / - browser:page for=zope.app.component.interfaces.IPossibleSite name=manage_site.html Modified: Products.Five/branches/philikon-local-components/site/localsite.py === --- Products.Five/branches/philikon-local-components/site/localsite.py 2006-03-02 19:04:58 UTC (rev 65740) +++ Products.Five/branches/philikon-local-components/site/localsite.py 2006-03-02 20:42:25 UTC (rev 65741) @@ -23,22 +23,6 @@ from Acquisition import aq_inner, aq_parent from Products.Five.site.interfaces import IFiveSiteManager, IFiveUtilityRegistry -def siteManagerAdapter(ob): -An adapter * - ISiteManager. - -This is registered in place of the one in Zope 3 so that we lookup -using acquisition instead of ILocation. - -current = ob -while True: -if ISite.providedBy(current): -return current.getSiteManager() -current = getattr(current, '__parent__', aq_parent(aq_inner(current))) -if current is None: -# It does not support acquisition or has no parent, so we -# return the global site -return getGlobalSiteManager() - class
[Zope-Checkins] SVN: Products.Five/branches/philikon-local-components/configure.zcml Oh, and yeah, include Five.component config
Log message for revision 65742: Oh, and yeah, include Five.component config Changed: U Products.Five/branches/philikon-local-components/configure.zcml -=- Modified: Products.Five/branches/philikon-local-components/configure.zcml === --- Products.Five/branches/philikon-local-components/configure.zcml 2006-03-02 20:42:25 UTC (rev 65741) +++ Products.Five/branches/philikon-local-components/configure.zcml 2006-03-02 20:42:58 UTC (rev 65742) @@ -6,6 +6,7 @@ include file=i18n.zcml / include file=event.zcml/ include file=deprecated.zcml/ + include package=.component / include package=.site / include package=.browser / include package=.form / ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
[Zope-Checkins] SVN: Products.Five/branches/philikon-local-components/component/ update imports
Log message for revision 65744: update imports use @adapter, @implementer instead of specifying interfaces in ZCML Changed: UU Products.Five/branches/philikon-local-components/component/__init__.py U Products.Five/branches/philikon-local-components/component/configure.zcml -=- Modified: Products.Five/branches/philikon-local-components/component/__init__.py === --- Products.Five/branches/philikon-local-components/component/__init__.py 2006-03-02 20:55:29 UTC (rev 65743) +++ Products.Five/branches/philikon-local-components/component/__init__.py 2006-03-02 20:56:48 UTC (rev 65744) @@ -16,12 +16,15 @@ $Id$ from zope.event import notify +from zope.interface import Interface, implementer from zope.interface import alsoProvides, noLongerProvides +from zope.component import adapter, getGlobalSiteManager +from zope.component.interfaces import IComponentLookup from zope.app.publication.zopepublication import BeforeTraverseEvent from zope.app.component.interfaces import ISite, IPossibleSite import ExtensionClass -from Acquisition import aq_base +from Acquisition import aq_base, aq_inner, aq_parent from Products.SiteAccess.AccessRule import AccessRule from ZPublisher.BeforeTraverse import registerBeforeTraverse from ZPublisher.BeforeTraverse import unregisterBeforeTraverse @@ -30,12 +33,12 @@ import zope.app.component.hooks zope.app.component.hooks.setHooks() [EMAIL PROTECTED](Interface) [EMAIL PROTECTED](IComponentLookup) def siteManagerAdapter(ob): -An adapter * - ISiteManager. - -This is registered in place of the one in Zope 3 so that we lookup -using acquisition instead of ILocation. - +Look-up a site manager/component registry for local component +lookup. This is registered in place of the one in Zope 3 so that +we lookup using acquisition in addition to ILocation. current = ob while True: if ISite.providedBy(current): Property changes on: Products.Five/branches/philikon-local-components/component/__init__.py ___ Name: svn:keywords + Id Modified: Products.Five/branches/philikon-local-components/component/configure.zcml === --- Products.Five/branches/philikon-local-components/component/configure.zcml 2006-03-02 20:55:29 UTC (rev 65743) +++ Products.Five/branches/philikon-local-components/component/configure.zcml 2006-03-02 20:56:48 UTC (rev 65744) @@ -1,11 +1,7 @@ configure xmlns=http://namespaces.zope.org/zope; xmlns:browser=http://namespaces.zope.org/browser; - adapter - for=* - provides=zope.component.interfaces.IComponentLookup - factory=.siteManagerAdapter - / + adapter factory=.siteManagerAdapter / subscriber for=zope.app.component.interfaces.ISite ___ Zope-Checkins maillist - Zope-Checkins@zope.org http://mail.zope.org/mailman/listinfo/zope-checkins
Re: [Zope-dev] Zope 2.9 releases for Windows?
Sidnei da Silva wrote: Run 'inst/WinBuilders/buildout zope'. Ah, you need Inno 5.x too. See inst/WinBuilders/README.txt for the complete instructions. OK, are either you (or anyone else at Enfold) or Tim going to roll the 2.9.1 binary or would you like me to pick it up from now on? cheers, Chris -- Simplistix - Content Management, Zope Python Consulting - http://www.simplistix.co.uk ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Zope 2.9 releases for Windows?
--On 2. März 2006 11:42:09 +0100 Wolfgang Strobl [EMAIL PROTECTED] wrote: In case your file is to be taken as the Zope-2.9.1 windows release i'd need it at the Zope-2.9.1 release folder and not at your member folder. Sure. I've removed it from my member folder. I think one needs to be Manager to upload content to the Products area on zope.org. I would give the new window maintainer a local Manager role in this case...so who is willing to care about the future Windows build? I would like to see a longer commitment for this job. Thanks, Andreas pgpnHwzp7fgXN.pgp Description: PGP signature ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Zope 2.9 releases for Windows?
On Wed, Mar 01, 2006 at 06:43:38PM +, Chris Withers wrote: | Sidnei da Silva wrote: | Run 'inst/WinBuilders/buildout zope'. | | Ah, you need Inno 5.x too. See inst/WinBuilders/README.txt for the | complete instructions. | | OK, are either you (or anyone else at Enfold) or Tim going to roll the | 2.9.1 binary or would you like me to pick it up from now on? Can't promise anything about 2.9.1. It might happen later on though. -- Sidnei da Silva Enfold Systems, LLC. http://enfoldsystems.com ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Two visions
On Tue, 2006-28-02 at 13:21 +0100, Martijn Faassen wrote: Philipp von Weitershausen wrote: [snip] I would vote for spelling out Zed (which would also be a little easier to google but might create trademark problems). The namespace package could either be 'z' or 'zed'. Then again, I really should take Jim's side and stay out of naming decisions. Let's please not have a naming discussion again. I think renaming Zope 3 is really bad marketing myself and naming discussions mostly a waste of time... As I sit here spending sooo much time reading this thread, I've finally decided its time to throw in my own naive point of view as an ex-J2EE developer and a Zope 2 developer that generally builds applications on top of Zope2/CMF/Plone. Let me make a random comments. 1) The Zope 3 name and brand is a marketing disaster (from my perspective) -- to be honest there's really no way I could see this actually getting worse by coming up with a new name. How many times in the #plone channel do we get asked, Does Plone run on Zope 3.1/3.2? or, When will Plone run on Zope 3.2 to which we say no to the first question and dunno to the second question. 2) Today when I build new applications with Plone, the best I can hope for is to use Zope 3 as a framework and Zope 2 as a deployment platform. Although the reality is I still use Zope 2 as a framework fr too much as well. I'm hoping (expecting) that Five will continue to make the requirement to use Zope 2 as a framework diminish more and more. As a developer, I certainly prefer working with Zope 3 the framework over Zope 2 the framework. 3) New developers who are moving in to either learn how to use Zope to develop applications or support existing zope applications of course immediately download the highest number Zope (zope 3 of course). They start using it and (hopefully) enjoy working on it and discover there's a big zope community with lots of developed applications. Then this developer starts googling for a type of plugin/component he needs to make sure he's not reinventing the wheel and discovers there's a HUGE plethora of Zope applications that do not even run on his latest zope platform and won't run on that platform in the foreseeable future. Ok, let me say what I think regarding these things. If we started treating zope 3 as just a framework and put energies back into maintaing/refactoring/beautifying zope2 as an application server that uses that framework at its core (this is essentially what zope 2.8+ is working towards with Five IMHO) then this could help several ways: 1) we stop spending time reproducing zope2 app server functionality in zope3 2) we stop building more into zope2 as a framework (i think this is pretty much already happening) Anyway, this still keeps things very confusing from a naming perspective (mostly for new adopters). So having said all of that, I am actually +1 on Jim's proposal #2. What I see from that (someone correct me if I'm wrong) is the following: 1) rename zope 3 the framework as Z or zopelib or Zed or something sensical that doesn't confuse the early adopter's conquest of trying to figure out which zope to start with 2) Make zope 2 the application server acquire the name zope once again and be the only app server. This could only work (from a new adopter's perspective) if either the application server is given a new name or given a version number higher than 3. Who are we worried aboug confusing here? Existing Zope 3 developers? Zope 2 developers? I don't think so, those people are smart enough to figure it out. So I say lets focus on not confusing new adopters in which case SOMETHING HAS TO BE DONE ABOUT THE CURRENT NAMING SITUATION! Kind Regards, Rocky -- Rocky Burt AdaptiveWave - Consulting, Training, and Content Management as a Service http://www.adaptivewave.com Content Management Made Simple ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Re: Two visions
On Thu, 02 Mar 2006 09:43:03 -0330, Rocky Burt wrote: Anyway, this still keeps things very confusing from a naming perspective (mostly for new adopters). So having said all of that, I am actually +1 on Jim's proposal #2. What I see from that (someone correct me if I'm wrong) is the following: 1) rename zope 3 the framework as Z or zopelib or Zed or something sensical that doesn't confuse the early adopter's conquest of trying to figure out which zope to start with 2) Make zope 2 the application server acquire the name zope once again and be the only app server. This could only work (from a new adopter's perspective) if either the application server is given a new name or given a version number higher than 3. I agree with Rocky's assessment. +1 on Jim's suggestion #2. However, if I am understanding things correctly, it doesn't really sound like door #2 entails a huge deviation from from our current course of bringing Zope 2 and Zope 3 together gradually. I don't really care what the converged product is called, Zope 2.250 or Zope 3.99 or Zope 5. My take is that Jim is not really proposing anything all that different from what Martijn wants -- a gradual convergence of Zope 2 and 3. Rather, it sounds like the biggest changes in Jim's proposal #2 entail 1) a change in how we _talk_ about what we are doing, and 2) an explicit attempt to factor out some of the Zope 3 goodness into a more generic, less-monolithic-app-server framework, Zed. (am I right here, Jim?) I think that the idea of giving Zed its own, distinct identity is great. Zope 3 is a _huge_ overhaul and it needs to be obvious to the world that it is dramatically better than crufty old Zope 2. Zope 3 then becomes the Zed application server; Zope 2 is getting Zed retrofits via Five, and the two will eventually converge into Zope 5. A distinct Zed distribution could bring in developers who are just interested in using the component architecture but not necessarily a big app server stack. It would be cool to see Zed popping up in random python products or perhaps in TurboGears / Django internals. And more than just cool -- the more people we can get using Zed, the more code we will be able to mix in easily to Zope (2/3/5) applications. Geoff ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Two visions?
+1 on Jim's suggestion #2. However, if I am understanding things correctly, it doesn't really sound like door #2 entails a huge deviation from from our current course of bringing Zope 2 and Zope 3 together gradually. I don't really care what the converged product is called, be it Zope 2.250 or Zope 3.99 or Zope 5. My take is that Jim is not really proposing anything all that different from what Martijn wants -- a gradual convergence of Zope 2 and 3. Rather, it sounds like the biggest changes in Jim's proposal #2 entail: 1) a change in how we _talk_ about what we are doing, and 2) an explicit attempt to factor out some of the Zope 3 goodness into a more generic, less-monolithic-app-server framework, Zed (or Z or ZomethingElse). Am I right here, Jim? I think that the idea of giving Zed its own, distinct identity is great. Zope 3 is a _huge_ overhaul and it needs to be obvious to the world that it is dramatically better than crufty old Zope 2. Zope 3 then becomes the Zed application server; Zope 2 is getting Zed retrofits via Five, and the two will eventually converge into Zope 5 (or Zope 2.27 or whatever). A distinct Zed distribution could bring in developers who are just interested in using the component architecture but not necessarily a big app server stack. It would be cool to see Zed popping up in random python products or perhaps even in TurboGears / Django internals. And more than just cool -- the more people we can get using Zed, the more code we will be able to mix in easily to Zope (2/3/5) applications. Geoff ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two visions?
Geoff Davis wrote: I think that the idea of giving Zed its own, distinct identity is great. I think it is stupid. We (Zope Corp + the Zope Community) have spent 8 years building the Zope brand, and you want to restart from scratch ? S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source! ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope3-dev] Re: [Zope-dev] Two visions?
On Thursday 02 March 2006 10:29, Stefane Fermigier wrote: Geoff Davis wrote: I think that the idea of giving Zed its own, distinct identity is great. I think it is stupid. Me too!! Regards, Stephan -- Stephan Richter CBU Physics Chemistry (B.S.) / Tufts Physics (Ph.D. student) Web2k - Web Software Design, Development and Training ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two visions?
Geoff Davis wrote: +1 on Jim's suggestion #2. However, if I am understanding things correctly, it doesn't really sound like door #2 entails a huge deviation from from our current course of bringing Zope 2 and Zope 3 together gradually. I don't really care what the converged product is called, be it Zope 2.250 or Zope 3.99 or Zope 5. My take is that Jim is not really proposing anything all that different from what Martijn wants -- a gradual convergence of Zope 2 and 3. Rather, it sounds like the biggest changes in Jim's proposal #2 entail: 1) a change in how we _talk_ about what we are doing, and 2) an explicit attempt to factor out some of the Zope 3 goodness into a more generic, less-monolithic-app-server framework, Zed (or Z or ZomethingElse). Am I right here, Jim? Yup. Realizing that there are two distinc efforts (the app server and the collection of technologies) and making that distinction clear. I think that the idea of giving Zed its own, distinct identity is great. Zope 3 is a _huge_ overhaul and it needs to be obvious to the world that it is dramatically better than crufty old Zope 2. Zope 3 then becomes the Zed application server; Zope 2 is getting Zed retrofits via Five, and the two will eventually converge into Zope 5 (or Zope 2.27 or whatever). Ooops. OK I guess I was clear as mud. :) My idea for Z, pronounced zed or whatever the naming gods decide is that it was *not* an app server. It is an un-app-server. :) A collection of technologies that are useful by themselves, to support an app server and useful to build non-app-server applications, web or otherwise. I think that Z3 is better than Z2 in a lot of ways. I also think that Z2 is more mature and complete. I really want us to combine those efforts. I think we've achieved enough and learned enough with Zope 3 that we can now bring that to bear and make Zope 2 better, refactoring the cruft away and applying the lessons we've learned with Zope 3. (Note that Zope 3 is not crust free.) I don't really care what this thing ends up being called, except that it *must* be called Zope. A distinct Zed distribution could bring in developers who are just interested in using the component architecture but not necessarily a big app server stack. It would be cool to see Zed popping up in random python products or perhaps even in TurboGears / Django internals. And more than just cool -- the more people we can get using Zed, the more code we will be able to mix in easily to Zope (2/3/5) applications. This paragraph makes me think I was clear. Yes, we need to follow Ian Bicking's advice and release our technology in bite-sized chunks. I'm hopeful that the packaging efforts underway will lead to more of that. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two visions?
On Thu, 02 Mar 2006 10:38:03 -0500, Jim Fulton wrote: I think that the idea of giving Zed its own, distinct identity is great. Zope 3 is a _huge_ overhaul and it needs to be obvious to the world that it is dramatically better than crufty old Zope 2. Zope 3 then becomes the Zed application server; Zope 2 is getting Zed retrofits via Five, and the two will eventually converge into Zope 5 (or Zope 2.27 or whatever). Ooops. OK I guess I was clear as mud. :) My idea for Z, pronounced zed or whatever the naming gods decide is that it was *not* an app server. It is an un-app-server. :) A collection of technologies that are useful by themselves, to support an app server and useful to build non-app-server applications, web or otherwise. No, I think I understood you. I was being sloppy in my use of language. I should have said something more like Zope 3 then becomes an application server built around the Zed library. I think that Z3 is better than Z2 in a lot of ways. I also think that Z2 is more mature and complete. I really want us to combine those efforts. I think we've achieved enough and learned enough with Zope 3 that we can now bring that to bear and make Zope 2 better, refactoring the cruft away and applying the lessons we've learned with Zope 3. (Note that Zope 3 is not crust free.) I don't really care what this thing ends up being called, except that it *must* be called Zope. Yes, I agree. Zope is the app server. I think that is consistent with the past use of the brand. This paragraph makes me think I was clear. Yes, we need to follow Ian Bicking's advice and release our technology in bite-sized chunks. I'm hopeful that the packaging efforts underway will lead to more of that. Yes, and the use of the new name Z or Zed is a way to emphasize that the Zed library is NOT a big, monolithic app server; rather, it's something new and cool. Geoff ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two visions?
Geoff Davis wrote: Yes, and the use of the new name Z or Zed is a way to emphasize that the Zed library is NOT a big, monolithic app server; rather, it's something new and cool. Zope 3 is new and cool. Or at least, let's spin it this way. Screencasts, podcasts, 14'59 wikis (quicker than TurboGears!), the whole sheebang. S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source! ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two visions?
Stefane Fermigier wrote: Geoff Davis wrote: I think that the idea of giving Zed its own, distinct identity is great.. I think it is stupid. We (Zope Corp + the Zope Community) have spent 8 years building the Zope brand, and you want to restart from scratch ? Hehe, poor Geoff. :) In the past, the Zope community hasn't made it a *strategic* goal to play nice with other Python projects. In the past, the Zope community hasn't made it a goal to be a sea of autonomous components. Its goal has been: top-to-bottom app server. We now have (I think!) said those goals are now in scope. Those goals are currently being met using the same name as the assembly. Trying to achieve the goals of the components, using the same word as the assembly, might not be the best way to achieve those goals. The comments I got on my pro-Zope weblog post showed that, if we *do* care about these new goals, we should consider whether the name is a barrier *for the components*. Alternatively, we could say: The components should only be used in the Zope application server. Perhaps that's the goal. I think Geoff's core point could be met by keeping the word Zope for the app server. I think Geoff's deeper point was to rethink the word used for the CA, which actually doesn't want to be thought of us an app server. --Paul ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two visions?
Geoff Davis wrote: On Thu, 02 Mar 2006 10:38:03 -0500, Jim Fulton wrote: I think that the idea of giving Zed its own, distinct identity is great. Zope 3 is a _huge_ overhaul and it needs to be obvious to the world that it is dramatically better than crufty old Zope 2. Zope 3 then becomes the Zed application server; Zope 2 is getting Zed retrofits via Five, and the two will eventually converge into Zope 5 (or Zope 2.27 or whatever). Ooops. OK I guess I was clear as mud. :) My idea for Z, pronounced zed or whatever the naming gods decide is that it was *not* an app server. It is an un-app-server. :) A collection of technologies that are useful by themselves, to support an app server and useful to build non-app-server applications, web or otherwise. No, I think I understood you. I was being sloppy in my use of language. I should have said something more like Zope 3 then becomes an application server built around the Zed library. Good clarification. I think that Z3 is better than Z2 in a lot of ways. I also think that Z2 is more mature and complete. I really want us to combine those efforts. I think we've achieved enough and learned enough with Zope 3 that we can now bring that to bear and make Zope 2 better, refactoring the cruft away and applying the lessons we've learned with Zope 3. (Note that Zope 3 is not crust free.) I don't really care what this thing ends up being called, except that it *must* be called Zope. Yes, I agree. Zope is the app server. I think that is consistent with the past use of the brand. Yep. This paragraph makes me think I was clear. Yes, we need to follow Ian Bicking's advice and release our technology in bite-sized chunks. I'm hopeful that the packaging efforts underway will lead to more of that. Yes, and the use of the new name Z or Zed is a way to emphasize that the Zed library is NOT a big, monolithic app server; rather, it's something new and cool. I think this brings up an interesting paradox in the discussion. We want Zope to continue being the name of an app server. But we also want the CA to be perceived as usable outside of an app server. Outside of Zope, even. Thus, we are using the same name used to convey: It *is* an app server! It's *not* an app server! I think this might be a contradiction and might be worth discussing. People have it set in their brain that Zope is a monolithic web application server. Hard to dispel that meme. --Paul ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two visions?
Paul Everitt wrote: ... People have it set in their brain that Zope is a monolithic web application server. Hard to dispel that meme. Yup. I'd rather adjust the meme to: Zope is a agile flexible extensible app server with rich services. :) Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Re: Two visions
On Thu, 02 Mar 2006 09:43:03 -0330, Rocky Burt wrote: On Tue, 2006-28-02 at 13:21 +0100, Martijn Faassen wrote: Philipp von Weitershausen wrote: [snip] I would vote for spelling out Zed (which would also be a little easier to google but might create trademark problems). The namespace package could either be 'z' or 'zed'. Then again, I really should take Jim's side and stay out of naming decisions. Let's please not have a naming discussion again. I think renaming Zope 3 is really bad marketing myself and naming discussions mostly a waste of time... As I sit here spending sooo much time reading this thread yes, it's a big'un alright... 1) The Zope 3 name and brand is a marketing disaster (from my perspective) -- to be honest there's really no way I could see this actually getting worse by coming up with a new name. How many times in the #plone channel do we get asked, Does Plone run on Zope 3.1/3.2? or, When will Plone run on Zope 3.2 to which we say no to the first question and dunno to the second question. +100. it's a confusing mess to anyone who isn't spending as much time as we all are reading this stuff every day. come to think of it, it's a confusing mess to us, too. If we started treating zope 3 as just a framework and put energies back into maintaing/refactoring/beautifying zope2 as an application server that uses that framework at its core (this is essentially what zope 2.8+ is working towards with Five IMHO) then this could help several ways: 1) we stop spending time reproducing zope2 app server functionality in zope3 2) we stop building more into zope2 as a framework (i think this is pretty much already happening) i agree with this sentiment, although i do recognize that there are folks who are currently using zope3 as an app-server, and who (understandably) don't want to have anything to do w/ anything zope2 related, ever again. Anyway, this still keeps things very confusing from a naming perspective (mostly for new adopters). So having said all of that, I am actually +1 on Jim's proposal #2. What I see from that (someone correct me if I'm wrong) is the following: 1) rename zope 3 the framework as Z or zopelib or Zed or something sensical that doesn't confuse the early adopter's conquest of trying to figure out which zope to start with 2) Make zope 2 the application server acquire the name zope once again and be the only app server. This could only work (from a new adopter's perspective) if either the application server is given a new name or given a version number higher than 3. i support this idea as well, but i think we have to recognize that there will be some parallel app-server-ness happening for a while, until z2 becomes so thin that we have achieved complete convergence btn the z2/five-based and the z3-based app server platforms that are already being used. -r ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Re: Re: Two visions
Strange how (most of) the Plone people seem to be so quick in willing to sacrifice the Zope brand :( S. -- Stéfane Fermigier, Tel: +33 (0)6 63 04 12 77 (mobile). Nuxeo Collaborative Portal Server: http://www.nuxeo.com/cps Gestion de contenu web / portail collaboratif / groupware / open source! ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two visions?
Stefane Fermigier wrote: I think that the idea of giving Zed its own, distinct identity is great. I think it is stupid. We (Zope Corp + the Zope Community) have spent 8 years building the Zope brand, and you want to restart from scratch ? Good point. There's the question: Does this zed thing need a different name at all? If we want other people to pick it up, then it seems like a good idea to distinguish it from Zope-the-app-server. Paul seems to suggest that in his response. How about zopelib? E.g.: * import zopelib.session * ez_install zopelib.publisher * etc. Actually, Shane suggested this once: http://dev.zope.org/Zope3/ZopeLibPackage Philipp ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Two visions
Stefane Fermigier wrote: Strange how (most of) the Plone people seem to be so quick in willing to sacrifice the Zope brand :( It's not about sacrificing the Zope-the-app-server brand. It's actually about growing it in the sense that it becomes much clearer WHAT THE HELL Zope actually is. Or can you explain what Zope is in one sentence? I surely can't. I currently need more than a page in my book. Rocky Burt is right, the naming actually confuses the heck out of people. In that sense, Zope X3 was not such a bad idea that it clearly said that Zope 3 is totally different. Just the 'X' itself standing for 'eXperimental' was bad Zope3-marketing in itself, so we dropped it. I will also note that Jim's proposal is really not a lot about naming (he wants to stay out of it) but about focusing effort in ONE application server and ONE set of reusable libraries. This focus in efforts seems to suggest to come up differnet names for the two things, but that doesn't mean they can't still be related in a brand naming sense (e.g. Zope and zopelib or somethign like that). Philipp ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Two visions
Stefane Fermigier wrote: Strange how (most of) the Plone people seem to be so quick in willing to sacrifice the Zope brand :( um, if you reread what i said, and what i think rocky is trying to say, i'm in favor of _keeping_ the zope brand for the app server, which is what zope has always been, and what plone runs (and will continue to run) on top of. strange how stefane seems to be so quick to write incendiary posts w/o any real content in them... -r ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope3-dev] Re: [Zope-dev] Two visions?
Philipp von Weitershausen wrote: Good point. There's the question: Does this zed thing need a different name at all? If we want other people to pick it up, then it seems like a good idea to distinguish it from Zope-the-app-server. Paul seems to suggest that in his response. How about zopelib? If we want people outside of the zope community to use these components, they should not have the word zope anywhere in their name. If it says zope people will *always* assume it is for use only with/inside Zope (Zope 2 more often than not). I've seen this when I've told people about testing their web apps with zope.testbrowser. Their first response is invariably oh, I can't use that; I'm not using Zope. Therefore, whatever the bag-o-components is named it should not contain zope. Z or zed would be OK with me (especially if we could come up with some decent domain names that are still available). -- Benji York Senior Software Engineer Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope3-dev] Re: [Zope-dev] Two visions?
Benji York wrote: Good point. There's the question: Does this zed thing need a different name at all? If we want other people to pick it up, then it seems like a good idea to distinguish it from Zope-the-app-server. Paul seems to suggest that in his response. How about zopelib? If we want people outside of the zope community to use these components, they should not have the word zope anywhere in their name. If it says zope people will *always* assume it is for use only with/inside Zope (Zope 2 more often than not). I've seen this when I've told people about testing their web apps with zope.testbrowser. Their first response is invariably oh, I can't use that; I'm not using Zope. Therefore, whatever the bag-o-components is named it should not contain zope. Z or zed would be OK with me (especially if we could come up with some decent domain names that are still available). I agree. zopelib was just a compromise for the people who like to keep the zed thing somewhat associated with Zope-the-project whereas we don't want this to be associated too closely with Zope-the-application-server for the reasons you state above. In the end the question is where we draw the line in all of this. Philipp ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Re: Re: Re: Two visions
On Thu, 02 Mar 2006 19:31:38 -, Stefane Fermigier [EMAIL PROTECTED] wrote: Strange how (most of) the Plone people seem to be so quick in willing to sacrifice the Zope brand :( I don't think that's true. I'm certainly not, and I've not heard anyone directly in favour of that either. What I *am* in favour of is branding the current Zope efforts much more strongly, and I think that an *additional* name to hype a Zope 3 brand around (Zope 3 Zebra or whatever) would make such marketing easier. Building our software on a less obscure appserver would make Plone much stronger. I know a very large organisation that would jump on Plone if it were built in Java. Zope is scary. Martin -- (muted) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Two visions?
On Thu, 02 Mar 2006 16:18:27 -, Jim Fulton [EMAIL PROTECTED] wrote: Zope is a agile flexible extensible app server with rich services. You forgot Enterprise. Martin -- (muted) ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Next release un June (was Re: [Zope3-dev] Re: [Zope-dev] Release schedule and deprecation decisions)
Jim Fulton wrote: On Mon, 2006-02-06 at 09:58 +0100, Christian Theune wrote: Hi, On Sun, 2006-02-05 at 12:11 -0500, Jim Fulton wrote: A while ago, we had some discussion on when to make releases and how long to support deprecated features. The discussion has died down so I'll summarize what I think the conclusions were: - We'll move releases up one month to may and November from June and December. This means that the next release is scheduled for May and the next feature freeze is April 1. ... Yikes. I do support the general decision, although this mangles my schedule about getting ready with the CC implemetation. +1 Thinking about this some more, I propose we should go for June and November this year, to give Christian and others more time and then do May and November from there on. OK, this is a decision. The next release wil be in June. After that release, we'll switch to a May/November schedule. Jim -- Jim Fulton mailto:[EMAIL PROTECTED] Python Powered! CTO (540) 361-1714http://www.python.org Zope Corporation http://www.zope.com http://www.zope.org ___ Zope-Dev maillist - Zope-Dev@zope.org http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-PAS] project questions
On 1 Mar 2006, at 21:50, Tino Wildenhain wrote: Jens Vagelpohl schrieb: Zac has asked to step back a bit as the contact for the project and I told him I could take over that part. That includes things like release stewardship. One of the items that had been on my list for a while was to move both the download area as well as the collector out of Zac's member folder on zope.org into the well-known areas, underneath / Collectors and /Products, respectively. +1 on that. This eases development a lot. PAS, PluginRegistry and the PAS collector have now moved: http://www.zope.org/Products/PluggableAuthService http://www.zope.org/Products/PluginRegistry http://www.zope.org/Collectors/PAS I continue to be foiled by %$£@ zope.org in that many items are private after pasting. I have repaired the worst of of, but catalog searches are still not revealing anything useful for PluggableAuthService. I am hoping this is a caching issue. jens ___ Zope-PAS mailing list Zope-PAS@zope.org http://mail.zope.org/mailman/listinfo/zope-pas
