Re: [Zope3-dev] RFC: The browser:page compromise

2006-04-25 Thread Lennart Regebro
On 4/25/06, Bernd Dorn <[EMAIL PROTECTED]> wrote: > > On 25.04.2006, at 20:27, Lennart Regebro wrote: > > > At https://svn.z3lab.org/z3lab/hello/trunk there is now a page > > this url seems to be broken No, it works fine, but only for svn > > (If you don't want to check it out and test it, you c

Re: [Zope3-dev] Re: ClientStorage vs DemoStorage broken in Zope 3.2?

2006-04-25 Thread Christian Theune
Hi again, Am Mittwoch, den 26.04.2006, 08:05 +0200 schrieb Christian Theune: > I remembered there was a fix like that. Unfortunately that fix was > ported to the 3.6 branch actually. I'm poking around myself a bit more. > > What I found right now is that BaseStorage accesses an attribute "_oid"

Re: [Zope3-dev] Re: ClientStorage vs DemoStorage broken in Zope 3.2?

2006-04-25 Thread Christian Theune
Hi, Am Dienstag, den 25.04.2006, 23:50 -0400 schrieb Tres Seaver: > > Smells like a fix didn't get forward-ported somehow -- that looks like > the same error I helped Tim find and fix for Zope 2. > > CC'ing the ZODB list just in case anyone there has a better memory. > Here is the NEWS.txt entry

[Zope3-dev] Re: ClientStorage vs DemoStorage broken in Zope 3.2?

2006-04-25 Thread Tres Seaver
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christian Theune wrote: > Hi, > > I'm preparing a presentation and marketing campaign for Zope 3 for the > next weeks linux fair in here in Germany. I'm demonstrating a couple of > things and was trying to use DemoStorage with ClientStorage on a Zope

[Zope3-dev] ClientStorage vs DemoStorage broken in Zope 3.2?

2006-04-25 Thread Christian Theune
Hi, I'm preparing a presentation and marketing campaign for Zope 3 for the next weeks linux fair in here in Germany. I'm demonstrating a couple of things and was trying to use DemoStorage with ClientStorage on a Zope 3.2 server today. However, it didn't work and crashed with this message and trace

Re: [Zope3-dev] RFC: The browser:page compromise

2006-04-25 Thread Bernd Dorn
On 25.04.2006, at 20:27, Lennart Regebro wrote: At https://svn.z3lab.org/z3lab/hello/trunk there is now a page this url seems to be broken implementation that is easy to use and doens't do class generation. In fact, there are two versions, one that sets the __call__ attribute during instan

[Zope3-dev] getInterface()'s context parameter

2006-04-25 Thread Jean-Marc Orliaguet
Hi, zope.component.getInterface takes a 'context' as a parameter, which is unused practically or set to None. def getInterface(context, id): iface = queryInterface(id, None) if iface is None: raise ComponentLookupError(id) return iface is it a relic from an old API? why not s

Re: [Zope3-dev] RFC: The browser:page compromise

2006-04-25 Thread Lennart Regebro
At https://svn.z3lab.org/z3lab/hello/trunk there is now a page implementation that is easy to use and doens't do class generation. In fact, there are two versions, one that sets the __call__ attribute during instantiation, and one that uses browserDefault() and publishTraverse(). There is also an

Re: [Zope3-dev] RFC: The browser:page compromise

2006-04-25 Thread Jim Fulton
Philipp von Weitershausen wrote: Jim Fulton wrote: The browser2:pageTemplate and browser2:pagesFromClass directives don't really gain anything, because they still generate classes. They don't have to generate classes. They could just do clever factory construction to avoid class creation. I

Re: [Zope3-dev] RFC: The browser:page compromise

2006-04-25 Thread Philipp von Weitershausen
Jim Fulton wrote: The browser2:pageTemplate and browser2:pagesFromClass directives don't really gain anything, because they still generate classes. They don't have to generate classes. They could just do clever factory construction to avoid class creation. I don't think they can. browser2:pageT