[Zope-Checkins] SVN: Zope/branches/philikon-aq/lib/python/Products/Five/browser/tests/aqlegacy_ftest.txt Corrected test with expected output

2008-04-17 Thread Hanno Schlichting
Log message for revision 85454:
  Corrected test with expected output
  

Changed:
  U   
Zope/branches/philikon-aq/lib/python/Products/Five/browser/tests/aqlegacy_ftest.txt

-=-
Modified: 
Zope/branches/philikon-aq/lib/python/Products/Five/browser/tests/aqlegacy_ftest.txt
===
--- 
Zope/branches/philikon-aq/lib/python/Products/Five/browser/tests/aqlegacy_ftest.txt
 2008-04-17 08:41:12 UTC (rev 85453)
+++ 
Zope/branches/philikon-aq/lib/python/Products/Five/browser/tests/aqlegacy_ftest.txt
 2008-04-17 09:55:48 UTC (rev 85454)
@@ -186,18 +186,15 @@
 No arguments required
 =
 
-ViewPageTemplateFile's requires no arguments.
+ViewPageTemplateFile's require no arguments, but you can only use them as
+class variables:
 
-XXX This currently fails with:
-TypeError: __call__() takes at least 2 arguments (1 given)
-
-We do call the template class in our own view code, without passing in 'self'
-as an argument. This worked so far, as the Five version didn't require any
-arguments:
-
view = getMultiAdapter((self.folder, request), name='template_two')
print view()
-  pThe falcon has taken flight/p
+  Traceback (most recent call last):
+  ...
+  TypeError: __call__() takes at least 2 arguments (1 given)
+  
 
 
 Clean up

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins


[Zope-Checkins] SVN: Zope/branches/philikon-aq/lib/python/Products/Five/browser/pagetemplatefile.py Whops, I removed the first comment line.

2008-04-17 Thread Hanno Schlichting
Log message for revision 85456:
  Whops, I removed the first comment line.

Changed:
  U   
Zope/branches/philikon-aq/lib/python/Products/Five/browser/pagetemplatefile.py

-=-
Modified: 
Zope/branches/philikon-aq/lib/python/Products/Five/browser/pagetemplatefile.py
===
--- 
Zope/branches/philikon-aq/lib/python/Products/Five/browser/pagetemplatefile.py  
2008-04-17 10:31:06 UTC (rev 85455)
+++ 
Zope/branches/philikon-aq/lib/python/Products/Five/browser/pagetemplatefile.py  
2008-04-17 10:36:23 UTC (rev 85456)
@@ -1,3 +1,4 @@
+##
 #
 # Copyright (c) 2004, 2005 Zope Corporation and Contributors.
 # All Rights Reserved.

___
Zope-Checkins maillist  -  Zope-Checkins@zope.org
http://mail.zope.org/mailman/listinfo/zope-checkins


[Zope-Checkins] SVN: Zope/trunk/lib/python/zope/app/EXTERNALS.txt Removed externals file, which wasn't updated anymore in a long time

2008-04-17 Thread Hanno Schlichting
Log message for revision 85459:
  Removed externals file, which wasn't updated anymore in a long time
  

Changed:
  D   Zope/trunk/lib/python/zope/app/EXTERNALS.txt

-=-
Deleted: Zope/trunk/lib/python/zope/app/EXTERNALS.txt
===
--- Zope/trunk/lib/python/zope/app/EXTERNALS.txt2008-04-17 14:26:08 UTC 
(rev 85458)
+++ Zope/trunk/lib/python/zope/app/EXTERNALS.txt2008-04-17 18:15:56 UTC 
(rev 85459)
@@ -1,68 +0,0 @@
-annotation  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/annotation
-apidoc  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/apidoc
-applicationcontrol  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/applicationcontrol
-appsetup
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/appsetup
-authentication  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/authentication
-basicskin   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/basicskin
-broken  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/broken
-cache   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/cache
-component   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/component
-container   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/container
-content 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/content
-content_types   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/content_types
-copypastemove   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/copypastemove
-datetimeutils   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/datetimeutils
-debug   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/debug
-decorator   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/decorator
-dependable  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/dependable
-dtmlpage
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/dtmlpage
-dublincore  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/dublincore
-error   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/error
-event   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/event
-exception   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/exception
-file
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/file
-filerepresentation  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/filerepresentation
-folder  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/folder
-form
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/form
-ftests  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/ftests
-generations 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/generations
-http
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/http
-i18n
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/i18n
-interface   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/interface
-intid   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/intid
-introspector
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/introspector
-keyreference
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/keyreference
-layers  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/layers
-locales 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/locales
-location
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/location
-mail
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/mail
-onlinehelp  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/onlinehelp
-pagetemplate
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/pagetemplate
-preference  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/preference
-preview 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/preview
-principalannotation 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/principalannotation
-publication 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/publication
-publisher   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/publisher
-rdb 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/rdb
-renderer
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/renderer
-rotterdam   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/rotterdam

[Zope-Checkins] SVN: Zope/branches/philikon-aq/lib/python/zope/app/EXTERNALS.txt Removed outdated externals from the branch

2008-04-17 Thread Hanno Schlichting
Log message for revision 85460:
  Removed outdated externals from the branch
  

Changed:
  D   Zope/branches/philikon-aq/lib/python/zope/app/EXTERNALS.txt

-=-
Deleted: Zope/branches/philikon-aq/lib/python/zope/app/EXTERNALS.txt
===
--- Zope/branches/philikon-aq/lib/python/zope/app/EXTERNALS.txt 2008-04-17 
18:15:56 UTC (rev 85459)
+++ Zope/branches/philikon-aq/lib/python/zope/app/EXTERNALS.txt 2008-04-17 
18:16:43 UTC (rev 85460)
@@ -1,68 +0,0 @@
-annotation  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/annotation
-apidoc  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/apidoc
-applicationcontrol  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/applicationcontrol
-appsetup
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/appsetup
-authentication  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/authentication
-basicskin   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/basicskin
-broken  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/broken
-cache   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/cache
-component   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/component
-container   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/container
-content 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/content
-content_types   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/content_types
-copypastemove   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/copypastemove
-datetimeutils   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/datetimeutils
-debug   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/debug
-decorator   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/decorator
-dependable  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/dependable
-dtmlpage
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/dtmlpage
-dublincore  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/dublincore
-error   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/error
-event   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/event
-exception   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/exception
-file
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/file
-filerepresentation  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/filerepresentation
-folder  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/folder
-form
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/form
-ftests  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/ftests
-generations 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/generations
-http
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/http
-i18n
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/i18n
-interface   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/interface
-intid   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/intid
-introspector
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/introspector
-keyreference
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/keyreference
-layers  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/layers
-locales 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/locales
-location
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/location
-mail
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/mail
-onlinehelp  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/onlinehelp
-pagetemplate
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/pagetemplate
-preference  
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/preference
-preview 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/preview
-principalannotation 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/principalannotation
-publication 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/publication
-publisher   
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/publisher
-rdb 
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/rdb
-renderer
svn://svn.zope.org/repos/main/Zope3/branches/3.3/src/zope/app/renderer
-rotterdam   

[Zope-Checkins] SVN: Zope/branches/philikon-aq/ Update branch to use the exact same Zope 3 version as the trunk

2008-04-17 Thread Hanno Schlichting
Log message for revision 85463:
  Update branch to use the exact same Zope 3 version as the trunk
  

Changed:
  _U  Zope/branches/philikon-aq/lib/python/zope/
  _U  Zope/branches/philikon-aq/lib/python/zope/app/
  U   Zope/branches/philikon-aq/setup.py

-=-

Property changes on: Zope/branches/philikon-aq/lib/python/zope
___
Name: svn:externals
   - annotation  -r 77445 
svn://svn.zope.org/repos/main/zope.annotation/trunk/src/zope/annotation
cachedescriptors-r 77445 
svn://svn.zope.org/repos/main/zope.cachedescriptors/trunk/src/zope/cachedescriptors
component   -r 77445 
svn://svn.zope.org/repos/main/zope.component/trunk/src/zope/component
configuration   -r 77445 
svn://svn.zope.org/repos/main/zope.configuration/trunk/src/zope/configuration
contentprovider -r 77445 
svn://svn.zope.org/repos/main/zope.contentprovider/trunk/src/zope/contentprovider
contenttype -r 77445 
svn://svn.zope.org/repos/main/zope.contenttype/trunk/src/zope/contenttype
copypastemove   -r 77445 
svn://svn.zope.org/repos/main/zope.copypastemove/trunk/src/zope/copypastemove
datetime-r 77445 
svn://svn.zope.org/repos/main/zope.datetime/trunk/src/zope/datetime
decorator   -r 77445 
svn://svn.zope.org/repos/main/zope.decorator/trunk/src/zope/decorator
deferredimport  -r 77445 
svn://svn.zope.org/repos/main/zope.deferredimport/trunk/src/zope/deferredimport
deprecation -r 77445 
svn://svn.zope.org/repos/main/zope.deprecation/trunk/src/zope/deprecation
documenttemplate-r 77445 
svn://svn.zope.org/repos/main/zope.documenttemplate/trunk/src/zope/documenttemplate
dottedname  -r 77445 
svn://svn.zope.org/repos/main/zope.dottedname/trunk/src/zope/dottedname
dublincore  -r 77445 
svn://svn.zope.org/repos/main/zope.dublincore/trunk/src/zope/dublincore
event   -r 77445 
svn://svn.zope.org/repos/main/zope.event/trunk/src/zope/event
exceptions  -r 77445 
svn://svn.zope.org/repos/main/zope.exceptions/trunk/src/zope/exceptions
filerepresentation  -r 77445 
svn://svn.zope.org/repos/main/zope.filerepresentation/trunk/src/zope/filerepresentation
formlib -r 77445 
svn://svn.zope.org/repos/main/zope.formlib/trunk/src/zope/formlib
#fssync  -r 77445 
svn://svn.zope.org/repos/main/zope.fssync/trunk/src/zope/fssync
hookable-r 77445 
svn://svn.zope.org/repos/main/zope.hookable/trunk/src/zope/hookable
i18nmessageid   -r 77445 
svn://svn.zope.org/repos/main/zope.i18nmessageid/trunk/src/zope/i18nmessageid
i18n-r 77445 
svn://svn.zope.org/repos/main/zope.i18n/trunk/src/zope/i18n
index   -r 77445 
svn://svn.zope.org/repos/main/zope.index/trunk/src/zope/index
interface   -r 77445 
svn://svn.zope.org/repos/main/zope.interface/trunk/src/zope/interface
lifecycleevent  -r 77445 
svn://svn.zope.org/repos/main/zope.lifecycleevent/trunk/src/zope/lifecycleevent
location-r 77445 
svn://svn.zope.org/repos/main/zope.location/trunk/src/zope/location
modulealias -r 77445 
svn://svn.zope.org/repos/main/zope.modulealias/trunk/src/zope/modulealias
pagetemplate-r 77445 
svn://svn.zope.org/repos/main/zope.pagetemplate/trunk/src/zope/pagetemplate
proxy   -r 77445 
svn://svn.zope.org/repos/main/zope.proxy/trunk/src/zope/proxy
publisher   -r 77445 
svn://svn.zope.org/repos/main/zope.publisher/trunk/src/zope/publisher
rdb -r 77445 
svn://svn.zope.org/repos/main/zope.rdb/trunk/src/zope/rdb
schema  -r 77445 
svn://svn.zope.org/repos/main/zope.schema/trunk/src/zope/schema
security-r 77445 
svn://svn.zope.org/repos/main/zope.security/trunk/src/zope/security
sendmail-r 77445 
svn://svn.zope.org/repos/main/zope.sendmail/trunk/src/zope/sendmail
sequencesort-r 77445 
svn://svn.zope.org/repos/main/zope.sequencesort/trunk/src/zope/sequencesort
server  -r 77445 
svn://svn.zope.org/repos/main/zope.server/trunk/src/zope/server
size-r 77445 
svn://svn.zope.org/repos/main/zope.size/trunk/src/zope/size
structuredtext  -r 77445 
svn://svn.zope.org/repos/main/zope.structuredtext/trunk/src/zope/structuredtext
tales   -r 77445 
svn://svn.zope.org/repos/main/zope.tales/trunk/src/zope/tales
tal -r 77445 
svn://svn.zope.org/repos/main/zope.tal/trunk/src/zope/tal
testbrowser -r 77445 
svn://svn.zope.org/repos/main/zope.testbrowser/trunk/src/zope/testbrowser
testing -r 77445 
svn://svn.zope.org/repos/main/zope.testing/trunk/src/zope/testing
testrecorder-r 77445 
svn://svn.zope.org/repos/main/zope.testrecorder/trunk/src/zope/testrecorder
thread  -r 77445 
svn://svn.zope.org/repos/main/zope.thread/trunk/src/zope/thread
traversing  -r 77445 
svn://svn.zope.org/repos/main/zope.traversing/trunk/src/zope/traversing
viewlet -r 77445 

[Zope-dev] Re: Splitting up zope.app.container

2008-04-17 Thread Christian Zagrodnick

On 2008-04-16 18:34:44 +0200, Malthe Borch [EMAIL PROTECTED] said:

The ``constraints`` module in zope.app.container seem to be usable 
outside a ZODB-application---ditto most of the interfaces.


If we want to support a nozodb-environment, it would be nice to not 
have to pull in ZODB just to get these frameworky definitions.


Is it package overkill to move these out to, say, zope.container?


+1

Also the container interfaces could be moved there.

--
Christian Zagrodnick

gocept gmbh  co. kg  ·  forsterstrasse 29 · 06112 halle/saale
www.gocept.com · fon. +49 345 12298894 · fax. +49 345 12298891



___
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] Splitting up zope.app.container

2008-04-17 Thread Bernd Dorn


On 16.04.2008, at 18:34, Malthe Borch wrote:
The ``constraints`` module in zope.app.container seem to be usable  
outside a ZODB-application---ditto most of the interfaces.


If we want to support a nozodb-environment, it would be nice to not  
have to pull in ZODB just to get these frameworky definitions.


Is it package overkill to move these out to, say, zope.container?


hi malthe

+1 good idea

what we need most ist zope.app.container.interfaces.IContained
and the proxies





\malthe

___
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 )


--
Lovely Systems, senior developer

phone: +43 5572 908060, fax: +43 5572 908060-77
Schmelzhütterstraße 26a, 6850 Dornbirn, Austria
skype: bernd.dorn





smime.p7s
Description: S/MIME cryptographic 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 )


AW: [Zope-dev] Re: Splitting up zope.app.container

2008-04-17 Thread Roger Ineichen
Hi Christian

 Betreff: [Zope-dev] Re: Splitting up zope.app.container
 
 On 2008-04-16 18:34:44 +0200, Malthe Borch [EMAIL PROTECTED] said:
 
  The ``constraints`` module in zope.app.container seem to be usable 
  outside a ZODB-application---ditto most of the interfaces.
  
  If we want to support a nozodb-environment, it would be nice to not 
  have to pull in ZODB just to get these frameworky definitions.
  
  Is it package overkill to move these out to, say, zope.container?
 
 +1
 
 Also the container interfaces could be moved there.

+1

Regards
Roger Ineichen

 --
 Christian Zagrodnick
 
 gocept gmbh  co. kg  .  forsterstrasse 29 . 06112 
 halle/saale www.gocept.com . fon. +49 345 12298894 . fax. +49 
 345 12298891

___
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] Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Hanno Schlichting

Hi.

I'd like to propose to merge the philikon-aq branch into Zope trunk aka 
Zope 2.12.


Scope:

For those unfamiliar with the branch, it makes Acquisition aware of 
__parent__ pointers. This makes it unnecessary to use Acquisition 
mixin's for Zope 3 code to use them in Zope 2 code. The security 
machinery of Zope 2 will still be able to work as expected.


Status:

All tests in the Zope itself pass. New tests have been written for all 
edge cases found during the development of the branch.


As a real world exposure Plone has been used to test the branch. All 
tests in Plone except one edge-case of a monkey-patch loaded package 
still pass. Plone in current versions make heavy use of Zope 3 and Five 
technologies inside Zope 2, so I see this as a very good indicator for 
the readiness of the branch. The one edge-case is something which needs 
to be fixed in Plone, as it doesn't make use of any official API.


Risks:

Using Zope 3 code inside Zope 2 has lead to various 'inventive 
solutions' to work around problems. Some of these have not used official 
API's. It is possible that some of those might need to be adjusted. 
Adjusting them should be straight forward in most cases and mostly 
consist of removing the hackish workarounds.


The second problem that might arise, is that the implicit assumption 
that every object inside Zope 2 inherits from Acquisition base classes 
no longer holds. Code that relies on the various aq_* attributes to be 
there need to be adjusted to use the Acquisition methods instead. This 
change is trivial to do and doesn't need to be done at first. It only 
needs to be done when you want to allow direct Zope 3 code in your 
application. As part of the branch all code in Zope 2 itself have been 
adjusted to use the aq_* methods.


Timeline:

I would like to do the merge as soon as possible, so people can easily 
test it against all their applications and report back problems.


Merging it into Zope trunk will get it into the Zope 2.12 release which 
is at this point not scheduled yet, but is unlikely to get a release 
before early 2009. This should give us plenty of time to test.


Opinions, votes?

Hanno

P.S. Thanks to philiKON for doing most of the work on this branch :)

___
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: AQ-Parent branch test failues was: Re: Five and browser-oriented components

2008-04-17 Thread Hanno Schlichting

Philipp von Weitershausen wrote:

Wichert Akkerman wrote:

Previously Philipp von Weitershausen wrote:

In my opinion, the fact that it accidentally worked as an instance
variable isn't a very strong argument for continuing to support it. To
me, this is a prime example of misusing a Five component which now
leads to problems when we go pure Zope3.


I'ld agree if there was a docstring or interface that made that
explicit. I've updated the relevant code in plone.app.portlets though
since the change is harmless.


Cool, that's great. If this is just a matter of a docstring, I'm sure 
that can be arranged :)


I added a docstring on the branch now. If we get approval for the branch 
merge in the current form (see new thread) I'll backport the docstring 
to all current active branches.


Hanno

___
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] Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Christian Theune
On Thu, Apr 17, 2008 at 12:43:25PM +0200, Martijn Pieters wrote:
 On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:
   I would like to do the merge as soon as possible, so people can easily test
  it against all their applications and report back problems.
 
   Merging it into Zope trunk will get it into the Zope 2.12 release which is
  at this point not scheduled yet, but is unlikely to get a release before
  early 2009. This should give us plenty of time to test.
 
   Opinions, votes?
 
 +sys.maxint!

Darn. My +1 won't fit in there anymore!


-- 
gocept gmbh  co. kg - forsterstrasse 29 - 06112 halle (saale) - germany
www.gocept.com - [EMAIL PROTECTED] - phone +49 345 122 9889 7 -
fax +49 345 122 9889 1 - zope and plone consulting and development
___
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: Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Andreas Zeidler

Christian Theune wrote:

On Thu, Apr 17, 2008 at 12:43:25PM +0200, Martijn Pieters wrote:

On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:

 I would like to do the merge as soon as possible, so people can easily test
it against all their applications and report back problems.

 Merging it into Zope trunk will get it into the Zope 2.12 release which is
at this point not scheduled yet, but is unlikely to get a release before
early 2009. This should give us plenty of time to test.

 Opinions, votes?

+sys.maxint!


Darn. My +1 won't fit in there anymore!


perhaps martijn's still on 32-bit? :)

anyway, +1 from me as well.


andi

--
zeidler it consulting - http://zitc.de/ - [EMAIL PROTECTED]
friedelstraße 31 - 12047 berlin - telefon +49 30 25563779
pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/
plone 3.1rc1 released! -- http://plone.org/products/plone/
___
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] Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Wichert Akkerman
Previously Martijn Pieters wrote:
 On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:
   I would like to do the merge as soon as possible, so people can easily test
  it against all their applications and report back problems.
 
   Merging it into Zope trunk will get it into the Zope 2.12 release which is
  at this point not scheduled yet, but is unlikely to get a release before
  early 2009. This should give us plenty of time to test.
 
   Opinions, votes?
 
 +sys.maxint!

I'm afraid any further +1s will turn that into a negative score now.

Wichert.

-- 
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/   It is hard to make things 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] Zope Tests: 5 OK

2008-04-17 Thread Zope Tests Summarizer
Summary of messages to the zope-tests list.
Period Wed Apr 16 11:00:00 2008 UTC to Thu Apr 17 11:00:00 2008 UTC.
There were 5 messages: 5 from Zope Tests.


Tests passed OK
---

Subject: OK : Zope-2.8 Python-2.3.6 : Linux
From: Zope Tests
Date: Wed Apr 16 21:00:32 EDT 2008
URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009415.html

Subject: OK : Zope-2.9 Python-2.4.4 : Linux
From: Zope Tests
Date: Wed Apr 16 21:02:02 EDT 2008
URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009416.html

Subject: OK : Zope-2.10 Python-2.4.4 : Linux
From: Zope Tests
Date: Wed Apr 16 21:03:32 EDT 2008
URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009417.html

Subject: OK : Zope-2.11 Python-2.4.4 : Linux
From: Zope Tests
Date: Wed Apr 16 21:05:02 EDT 2008
URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009418.html

Subject: OK : Zope-trunk Python-2.4.4 : Linux
From: Zope Tests
Date: Wed Apr 16 21:06:32 EDT 2008
URL: http://mail.zope.org/pipermail/zope-tests/2008-April/009419.html

___
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] Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Jens Vagelpohl


On Apr 17, 2008, at 12:27 , Hanno Schlichting wrote:

Opinions, votes?


+1



___
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] Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Martijn Pieters
On Thu, Apr 17, 2008 at 12:27 PM, Hanno Schlichting [EMAIL PROTECTED] wrote:
  I would like to do the merge as soon as possible, so people can easily test
 it against all their applications and report back problems.

  Merging it into Zope trunk will get it into the Zope 2.12 release which is
 at this point not scheduled yet, but is unlikely to get a release before
 early 2009. This should give us plenty of time to test.

  Opinions, votes?

+sys.maxint!

Thanks, Hanno, for carrying this to it's completion!

-- 
Martijn Pieters
___
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] Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Andreas Jung



--On 17. April 2008 12:27:42 +0200 Hanno Schlichting [EMAIL PROTECTED] 
wrote:



Hi.

I'd like to propose to merge the philikon-aq branch into Zope trunk aka
Zope 2.12.


Go ahead.

Andreas

pgphIV5gzoW65.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 )


[Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Philipp von Weitershausen

Hanno Schlichting wrote:

Timeline:

I would like to do the merge as soon as possible, so people can easily 
test it against all their applications and report back problems.


Merging it into Zope trunk will get it into the Zope 2.12 release which 
is at this point not scheduled yet, but is unlikely to get a release 
before early 2009. This should give us plenty of time to test.


This sounds good. Here's another idea, though: In accordance with 
release early and often, how about scheduling the 2.12 release shortly 
after the 2.11 one? So the only new thing in 2.12 would be the 
philikon-aq branch (it would still ship with the same Zope 3 libraries 
as 2.11, etc.).



Opinions, votes?


+1 :)


P.S. Thanks to philiKON for doing most of the work on this branch :)


And thanks to Hanno for testing it against Plone and making lots of 
improvements!

___
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: Five and browser-oriented components

2008-04-17 Thread Martijn Faassen

Hanno Schlichting wrote:

Martijn Faassen wrote:

Alexander Limi wrote:
On Mon, 14 Apr 2008 10:11:11 -0700, Philipp von Weitershausen 
[EMAIL PROTECTED] wrote:


*IF* you'd like to be pragmatic, I'd suggest we clean up those 
failing Plone tests, merge the branch and be on our way.


This gets back to Hanno's suggestion of writing a clean test case that 
demonstrates this problem. We can then get it into Zope and fix it. 
This should allow cleaning up the Zope 3 integration in Zope 2 
significantly.


I kept my promise and added the simple tests for the first two issues I 
found while doing testing against Plone.


Excellent, thank you very much! I hope this will motivate people to look 
into this branch again.


Regards,

Martijn

___
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: Splitting up zope.app.container

2008-04-17 Thread Martijn Faassen

Bernd Dorn wrote:


On 16.04.2008, at 18:34, Malthe Borch wrote:
The ``constraints`` module in zope.app.container seem to be usable 
outside a ZODB-application---ditto most of the interfaces.


If we want to support a nozodb-environment, it would be nice to not 
have to pull in ZODB just to get these frameworky definitions.


Is it package overkill to move these out to, say, zope.container?


hi malthe

+1 good idea

what we need most ist zope.app.container.interfaces.IContained
and the proxies


+1

I support this move as well. We just need to be careful not to move any 
content that can be persisted.


Regards,

Martijn

P.S. Thanks for bringing up topics on the mailing list like this Malthe, 
I think that's a really good initiative!


___
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: Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Martijn Faassen

Hey,

Hanno, this is a major step forward! +1 from me as well.

Regards,

Martijn

___
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] Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Stefan H. Holek

On 17.04.2008, at 12:27, Hanno Schlichting wrote:

Opinions, votes?



+1

--
Stefan H. Holek
[EMAIL PROTECTED]




___
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: Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Wichert Akkerman
Previously Philipp von Weitershausen wrote:
 This sounds good. Here's another idea, though: In accordance with 
 release early and often, how about scheduling the 2.12 release shortly 
 after the 2.11 one? So the only new thing in 2.12 would be the 
 philikon-aq branch (it would still ship with the same Zope 3 libraries 
 as 2.11, etc.).

+1

Wichert.

-- 
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/   It is hard to make things 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: Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Hanno Schlichting

Philipp von Weitershausen wrote:

Hanno Schlichting wrote:
Merging it into Zope trunk will get it into the Zope 2.12 release 
which is at this point not scheduled yet, but is unlikely to get a 
release before early 2009. This should give us plenty of time to test.


This sounds good. Here's another idea, though: In accordance with 
release early and often, how about scheduling the 2.12 release shortly 
after the 2.11 one? So the only new thing in 2.12 would be the 
philikon-aq branch (it would still ship with the same Zope 3 libraries 
as 2.11, etc.).


I suspect we want to do something about the eggification story of Zope 2 
for Zope 2.12 as well. Figuring out the approach and documenting it 
might take some additional time. I don't see that releasing another Zope 
2.13 shortly after 2.12 makes a lot of sense.


Hanno

___
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: Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Hanno Schlichting wrote:
 Hi.
 
 I'd like to propose to merge the philikon-aq branch into Zope trunk aka 
 Zope 2.12.
 
 Scope:
 
 For those unfamiliar with the branch, it makes Acquisition aware of 
 __parent__ pointers. This makes it unnecessary to use Acquisition 
 mixin's for Zope 3 code to use them in Zope 2 code. The security 
 machinery of Zope 2 will still be able to work as expected.
 
 Status:
 
 All tests in the Zope itself pass. New tests have been written for all 
 edge cases found during the development of the branch.
 
 As a real world exposure Plone has been used to test the branch. All 
 tests in Plone except one edge-case of a monkey-patch loaded package 
 still pass. Plone in current versions make heavy use of Zope 3 and Five 
 technologies inside Zope 2, so I see this as a very good indicator for 
 the readiness of the branch. The one edge-case is something which needs 
 to be fixed in Plone, as it doesn't make use of any official API.
 
 Risks:
 
 Using Zope 3 code inside Zope 2 has lead to various 'inventive 
 solutions' to work around problems. Some of these have not used official 
 API's. It is possible that some of those might need to be adjusted. 
 Adjusting them should be straight forward in most cases and mostly 
 consist of removing the hackish workarounds.
 
 The second problem that might arise, is that the implicit assumption 
 that every object inside Zope 2 inherits from Acquisition base classes 
 no longer holds. Code that relies on the various aq_* attributes to be 
 there need to be adjusted to use the Acquisition methods instead.

The major downside here is that restricted code doesn't have access to
the required functions ('aq_inner', 'aq_parent', 'aq_acquire'), and
hence use the attributes.  ('aq_base' should not be allowewd at all, as
it strips away security context).

There are probably thousands (or even tens of thousands) of templates
and scripts in the wild which use these attributes.  I don't think we
can break them in a single release:  we need to deprecate them first
(with suitalbe logging output), and maybe even provide
'__parent__'-aware workarounds / fallbacks in their implementations.

 This 
 change is trivial to do and doesn't need to be done at first. It only 
 needs to be done when you want to allow direct Zope 3 code in your 
 application. As part of the branch all code in Zope 2 itself have been 
 adjusted to use the aq_* methods.

Good!

 Timeline:
 
 I would like to do the merge as soon as possible, so people can easily 
 test it against all their applications and report back problems.
 
 Merging it into Zope trunk will get it into the Zope 2.12 release which 
 is at this point not scheduled yet, but is unlikely to get a release 
 before early 2009. This should give us plenty of time to test.
 
 Opinions, votes?
 
 Hanno
 
 P.S. Thanks to philiKON for doing most of the work on this branch :)

Many kudos to both of you.



Tres.
- --
===
Tres Seaver  +1 540-429-0999  [EMAIL PROTECTED]
Palladion Software   Excellence by Designhttp://palladion.com
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIB4NT+gerLs4ltQ4RAvFlAKDLXkUC/ffrP4pGfNFC94Q815GcQgCfXqFU
WqXqkO8p6JAZiOT4zpgg4wQ=
=iWAn
-END 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 )


[Zope-dev] Re: Proposal: Merge philikon-aq branch into Zope trunk

2008-04-17 Thread Martin Aspeli

Hanno Schlichting wrote:

Philipp von Weitershausen wrote:

Hanno Schlichting wrote:
Merging it into Zope trunk will get it into the Zope 2.12 release 
which is at this point not scheduled yet, but is unlikely to get a 
release before early 2009. This should give us plenty of time to test.
This sounds good. Here's another idea, though: In accordance with 
release early and often, how about scheduling the 2.12 release shortly 
after the 2.11 one? So the only new thing in 2.12 would be the 
philikon-aq branch (it would still ship with the same Zope 3 libraries 
as 2.11, etc.).


I suspect we want to do something about the eggification story of Zope 2 
for Zope 2.12 as well. Figuring out the approach and documenting it 
might take some additional time. I don't see that releasing another Zope 
2.13 shortly after 2.12 makes a lot of sense.


Why don't we get started on that, too, then?

I think eggification of Zope 2 is relatively easy, and most of the 
necessary RD has already been done. In fact, a lot of the eggs exist 
already.


I wonder if Philipp would be amenable to writing a proposal on this, and 
get Chris McDonough's input.


Martin

--
Author of `Professional Plone Development`, a book for developers who
want to work with Plone. See http://martinaspeli.net/plone-book

___
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] anyone heard of Zamasing?

2008-04-17 Thread Philip Kilner

Hi Tim,

Tim Nash wrote:

  It is great to see more posts about how well zope works for Web
2.0 projects. I have used extjs with zope and really like the
combination. I'd like to learn more about your jquery /plone setup and
how you make it work. Would it be a time consuming for you to create a
generic product that demonstrates your setup? It would be helpful to
have a common set of artifacts to discuss.



Am happy to share - it's all very simple stuff, the elements just work 
very elegantly together. I'm stringing other people's pearls here - the 
tools are great, putting them together is trivial.


However, having got the elements together, I'm now moving from a TTW 
approach (yes, I know - I'm a dinosaur!) to a Product approach, which is 
going to be a pretty steep learning curve for me. I need to document my 
starting point (which is effectively a common folder of scripts and 
templates, which the working pages access by acquisition), so I'll post 
a link to the list asking for feedback when I'm at that point.


N.B. This is going to take me at least a couple of weeks - I've got some 
paying work to finish off before I can move on to that.


I've got a proof of concept set of templates without Formulator or any 
RDBMS interaction that I did somewhere. It's only about three templates 
and a scrip. I'll post them when I find them, so that you can see how 
Taconite works with ZPTs, which is the most joyful part of it for me.



--

Regards,

PhilK


'work as if you lived in the early days of a better nation'
- alasdair gray
___
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] anyone heard of Zamasing?

2008-04-17 Thread Tim Nash
@Garito,
  I hope you have another  release of ZSM. I really appreciate new
developer tools for zope like your ZSM and Zamasing. I am pretty
confident that the zope 3 crowd will eventually put back TTW,  simple
ZMI etc. (but hopefully not too much acquisitionthe great idea
that almost ruins zope 2).

Google is very close to making the business layer scalable, they have
been studying salesforce.com for some time now. When they conquer that
technical hurdle, huge ASP's will probably dominate computing
(especially in China). Easily distributed and maintained web services
like zope 2 may be one of the few remaining ways to compete with
monster ASP's. The zope 3 crowd will come back around with an even
better zope.

 @Phil,
   I think you will find the product learning curve isn't that steep
at all. The famous z-shaped curve has more to do with the lack of
up-to-date documentation than anything else. Products are the way to
go. It is very much like wriitng 'Scripts Python'. I am going to put a
simple 'boring' product on the zope.org site (if they let me) which
will show how to use zope and extjs for anyone who is interested.
Looking forward to your proof of concept

-Tim

On Thu, Apr 17, 2008 at 1:01 AM, Philip Kilner [EMAIL PROTECTED] wrote:
 Hi Tim,


  Tim Nash wrote:

   It is great to see more posts about how well zope works for Web
  2.0 projects. I have used extjs with zope and really like the
  combination. I'd like to learn more about your jquery /plone setup and
  how you make it work. Would it be a time consuming for you to create a
  generic product that demonstrates your setup? It would be helpful to
  have a common set of artifacts to discuss.
 
 

  Am happy to share - it's all very simple stuff, the elements just work very
 elegantly together. I'm stringing other people's pearls here - the tools are
 great, putting them together is trivial.

  However, having got the elements together, I'm now moving from a TTW
 approach (yes, I know - I'm a dinosaur!) to a Product approach, which is
 going to be a pretty steep learning curve for me. I need to document my
 starting point (which is effectively a common folder of scripts and
 templates, which the working pages access by acquisition), so I'll post a
 link to the list asking for feedback when I'm at that point.

  N.B. This is going to take me at least a couple of weeks - I've got some
 paying work to finish off before I can move on to that.

  I've got a proof of concept set of templates without Formulator or any
 RDBMS interaction that I did somewhere. It's only about three templates and
 a scrip. I'll post them when I find them, so that you can see how Taconite
 works with ZPTs, which is the most joyful part of it for me.


  --


  Regards,

  PhilK


  'work as if you lived in the early days of a better nation'
  - alasdair gray

___
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] authentication with python program

2008-04-17 Thread Miguel Beltran R.
I have this program what open a dtml what return a XML page, but I
have error with permisions:

import urllib, urllib2

pagina = http://10.28.1.239/bitacoras/alta/estado2.html;
datos = {btipo:D,
 bholo:87654321,
 bplac:dd-12345,
 accion:alta_gasolina,
}

params=urllib.urlencode(datos)
aut=urllib2.HTTPBasicAuthHandler()
aut.add_password(AFICON, pagina, myuser, mypass)
opener=urllib2.build_opener(aut)
urllib2.install_opener(opener)
r=urllib2.urlopen(pagina,params)
print r.read()
r.close()

but returned XML say:
ajax
  accionalta_gasolina/accion
   respuestaerror/respuesta
error_typeUnauthorized/error_type
error_descriptionYou are not allowed to access 'zsql_alta'
in this context/error_description

  /ajax

help? how I can send HTTPBasicAuth?

pd. Sorry by my bad english
-- 

Lo bueno de vivir un dia mas
es saber que nos queda un dia menos de vida
___
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: anyone heard of Zamasing?

2008-04-17 Thread Simon Michael

Tim Nash wrote:

up-to-date documentation than anything else. Products are the way to
go. It is very much like wriitng 'Scripts Python'. I am going to put a
simple 'boring' product on the zope.org site (if they let me) which


Hi Tim.. put it also on http://wiki.zope.org/zope2 if you wish. That is 
an easy place to grow and rework documentation.


___
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 )