Re: [Zope3-dev] RFC: CustomWidgetFactory and widgets having different __init__ signature

2005-11-22 Thread Dominik Huber
Johan Carlsson wrote: Anywhere I can read up on what's happening with this issue/bug? - The class attribute of the widget-directive can handle a custom factory or a widget class. - The __call__ method of custom widget factory (zope.app.form.CustomWidgetFactory) invokes collection, choice

Re: [Zope3-dev] RFC: CustomWidgetFactory and widgets having different __init__ signature

2005-11-22 Thread Johan Carlsson
Dominik Huber wrote: Johan Carlsson wrote: Anywhere I can read up on what's happening with this issue/bug? - The class attribute of the widget-directive can handle a custom factory or a widget class. - The __call__ method of custom widget factory (zope.app.form.CustomWidgetFactory)

Re: [Zope3-dev] RFC: CustomWidgetFactory and widgets having different __init__ signature

2005-11-22 Thread Dominik Huber
Johan Carlsson wrote: Dominik Huber wrote: Johan Carlsson wrote: Anywhere I can read up on what's happening with this issue/bug? - The class attribute of the widget-directive can handle a custom factory or a widget class. - The __call__ method of custom widget factory

[Zope3-dev] unique intids rationale

2005-11-22 Thread Jean-Marc Orliaguet
Hi! what is the rationale between the unique integer ids utility and the usage policy? more specifically: why are newly added objects registered in *all* IntIds utilities? It does not make sense if the utility is registered locally. If they are local they should not be concerned with

Re: [Zope3-dev] __init__.py interfaces.py guidelines?

2005-11-22 Thread Martijn Faassen
Gary Poster wrote: On Nov 21, 2005, at 12:29 PM, Jean-Marc Orliaguet wrote: There is another place where there seems to be two different patterns too: sometimes we have: import zope.schema name = zope.schema.TextLine(...) and sometimes: from zope.schema import TextLine name =

Re: [Zope3-dev] __init__.py interfaces.py guidelines?

2005-11-22 Thread Dominik Huber
Martijn Faassen wrote: I don't think using any of these patterns is a big style problem (I'm much less opinionated about this than about code in __init__.py); it's hard to recommend a single practice, so perhaps we shouldn't. +1 Regards, Dominik begin:vcard fn:Dominik Huber n:Huber;Dominik

[Zope3-dev] Re: unique intids rationale

2005-11-22 Thread j.kartnaller
This has already been added to the bug collector : http://www.zope.org/Collectors/Zope3-dev/466 Jürgen Jean-Marc Orliaguet wrote: Hi! what is the rationale between the unique integer ids utility and the usage policy? more specifically: why are newly added objects registered in *all*

Re: [Zope3-dev] Re: __init__.py interfaces.py guidelines?

2005-11-22 Thread Jim Fulton
Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jean-Marc Orliaguet wrote: There is another place where there seems to be two different patterns too: sometimes we have: import zope.schema name = zope.schema.TextLine(...) and sometimes: from zope.schema import TextLine

Re: [Zope3-dev] __init__.py interfaces.py guidelines?

2005-11-22 Thread Jim Fulton
Gary Poster wrote: On Nov 21, 2005, at 12:29 PM, Jean-Marc Orliaguet wrote: There is another place where there seems to be two different patterns too: sometimes we have: import zope.schema name = zope.schema.TextLine(...) and sometimes: from zope.schema import TextLine name =

Re: [Zope3-dev] unique intids rationale

2005-11-22 Thread Jim Fulton
Jean-Marc Orliaguet wrote: Hi! what is the rationale between the unique integer ids utility and the usage policy? more specifically: why are newly added objects registered in *all* IntIds utilities? It does not make sense if the utility is registered locally. If they are local they should

Re: [Zope3-dev] Re: unique intids rationale

2005-11-22 Thread Jean-Marc Orliaguet
j.kartnaller wrote: This has already been added to the bug collector : http://www.zope.org/Collectors/Zope3-dev/466 Jürgen Jean-Marc Orliaguet wrote: Hi! what is the rationale between the unique integer ids utility and the usage policy? more specifically: why are newly added objects

[Zope3-dev] zope.testrecorder

2005-11-22 Thread Benji York
We don't have the collective time right now to market this, but it's very cool so we thought someone might get some use out of it. Brian Lloyd has developed zope.testrecorder, a cross-browser (IE, Firefox, Safari) JavaScript app that records browser events (clicking, entering text, etc.) and

Re: [Zope3-dev] __init__.py interfaces.py guidelines?

2005-11-22 Thread Dieter Maurer
Jim Fulton wrote at 2005-11-21 09:43 -0500: ... A Python convention is that a leading underscore indicates privateness. - what about import paths inside a same package: relative or absolute? from mypackage.interfaces import ISomeInterface or: from interfaces import ISomeInterface

[Zope3-dev] zope.app.application.HTTPPublicationRequestFactory interprets text/xml requests as XML-RPC (was: [Zope] Hard-coded Content-type:text/xml as xmlrpc in Zope (2.8.1))

2005-11-22 Thread Dieter Maurer
John Ziniti wrote at 2005-11-21 15:04 -0500: ... Zope-2.8.1 now additionally has the zope.app.publication. HTTPPublicationRequestFactory class, which also assumes that text/xml means xmlrpc (in fact, it assumes that anything that startswith('text/xml') is an xmlrpc call). zope.app is part of

Re: [Zope3-dev] zope.app.application.HTTPPublicationRequestFactory interprets text/xml requests as XML-RPC (was: [Zope] Hard-coded Content-type:text/xml as xmlrpc in Zope (2.8.1))

2005-11-22 Thread Andreas Jung
--On 22. November 2005 20:37:16 +0100 Dieter Maurer [EMAIL PROTECTED] wrote: You should complain about this misfeature on zope3-dev@zope.org. Definitely, there should not be a fixed (not configurable) association between text/xml requests and XML-RPC as text/xml can be interesting for the