Roger Ineichen wrote:
> What do you recommend to do? I'm open to improve it but how can we reflect
> the different adaption concepts like we have with the different __init__
> used by IPagelet and IContentProvider.
It should be easy to do by using a factory function which is registered as
the mul
Roger Ineichen wrote:
> Yes you are right, that was the reason I didn't define the __init__ method
> in the interface. But I still think a IPagelet isn't a IContentProvider by
> default. Of corse another class can be defined as IContentProvider and
> IPagelet. Such a class whould then provide a di
Roger Ineichen wrote:
> Probably we should say;
> "Pagelets are views which support the publisher __call__ attribute and
> provide the update/render pattern."
True.
> You are wrong here. A IContentProvider doesn't define content. A
> IContentProvider provides content. That's different.
I see di
Roger Ineichen wrote:
> I was carfully skip some additional method decalration because I didn't
> know if we gona use IPagelets without render and update in other
> implementations.
The z3c.pagelet README.txt says that "Pagelets are views which can be
called and support the update and render patt
During the gocept sprint on z3c.form last week we found that the interface
of pagelets (z3c.pagelet.interfaces.IPagelet) is a mere marker interface
on top of IBrowserPage, which seems to me a bit thin.
For one, the implementation of pagelets makes use of the render and update
methods. Since these
Philipp von Weitershausen wrote:
> This is an interesting move. I can settle with the idea, but I wonder this
> was discussed... Last time I remember we were discussing the idea of a
> package a la zope.site or zope.componentsite... (Also, as long as we're
> moving things, I wouldn't mind renaming
Am Wed, 21 Feb 2007 10:22:08 +0100 schrieb Thomas Lotze:
> I'd like the testrunner recipe to be able to create a part directory to
> use as its working directory as:
As nobody has responded for a couple of days, I now made the change: If
the working directory is not specified, or s
I'd like the testrunner recipe to be able to create a part directory to
use as its working directory as:
- I do want tests to run in their own directory in general,
- I don't want them to run in a temporary directory as I might be
interested in keeping coverage reports etc around for a while, an
Roger Ineichen wrote:
> I think that's not a good idea because this could be incompatible with
> others work. The formlib tempaltes are used in many project.
>
> Note, in many project the formlib is used without the Rotterdam skin and
> this isn't a problem.
So the real question is, what's the i
Hi,
while working on one of our projects at gocept, we noticed that formlib's
pageform.pt template defines a "viewspace" slot which we feel it
shouldn't, as the Rotterdam skin's template.pt has a div defining the same
slot and carrying the same id. We found this because of an extraneous line
insid
Am Sat, 26 Aug 2006 09:12:23 -0400 schrieb Jim Fulton:
> Note that I just ran the tests, including test_zeo on an up-to-date Ubuntu
> box, a Centos box, and on a Mac without failure. There may not be a
> problem with your setup,
As Benji pointed out, the problem is a bug in the particular Python
Am Sat, 26 Aug 2006 09:14:15 -0400 schrieb Benji York:
> Yes it is. That pre-release Python (2.4.4c0) has a bug in sgmllib that
> causes hangs.
Thanks, that explains it then.
> I suspect if you use Python 2.4.3 instead it'll begin working.
The manual tests do get through after installing 2.4.3
Am Sat, 26 Aug 2006 08:26:38 -0400 schrieb Jim Fulton:
> No it is not.
Then I'll connect my buildbot slave again as the problem is in Zope and
not in my setup.
--
Thomas
___
Zope3-dev mailing list
Zope3-dev@zope.org
Unsub: http://mail.zope.org/mailma
Am Thu, 24 Aug 2006 08:01:22 -0400 schrieb buildbot:
> The Buildbot has detected a failed build of Zope3 trunk 2.4 Linux tlotze.
Running all the steps by hand reveals that on the current trunk,
python2.4 test.py -vv -u --module '!^ZEO[.]' --all
gets stuck on test_zeo (zope.app.twisted.tests)
Am Mon, 27 Feb 2006 15:56:16 -0600 schrieb Paul Winkler:
> We are planning to do this to a number of other packages:
>
> zope.i18n
> zope.i18nmessageid
> zope.deprecation
> zope.exceptions
> zope.tal
> zope.component
What was the reason for choosing these and not choosing others? What
about, e.g
Hi,
after having posted this to what I guess is the wrong list (all hail gmane
group names...) and having received no answer, I'll repost it here:
I noticed that zope.app.file.File does not inherit from
zope.app.container.contained.Contained. This does not stop a file from,
e.g., getting added to
Philipp von Weitershausen wrote:
> Please note, however,
> that there are translation teams for certain languages.
JFTR: I did ask on #zope.de before making the changes, so it was merely
the wrong place to ask; I hadn't been aware of the right place. Sorry for
that.
> http://dev.zope.org/Zope3/G
Fred Drake wrote:
> Yes, it is easy to run into when taken outside of Zope. If nobody is
> using strictinsert=True, then perhaps the whole mess should be removed. I
> don't think changing the default is out of the question, either.
I'm +1 on removing it.
> I'll send a note to the ZPT list to s
Fred Drake wrote:
> Do you have a use-case for strictinsert=True, or was this just an
> implementation wart you ran into?
The latter. And it's easy to run into that wart, too: after all, it's the
default behaviour.
--
Thomas
___
Zope3-dev mailing li
Hi,
I fiddled a bit with TAL, METAL and TALES without page templates, using
TALGenerator (from zope.tal.talgenerator) and TALInterpreter (from
zope.tal.talinterpreter) directly. Something puzzles me about the engine
related parameter the __init__ method of either expects.
A TALGenerator expects a
Benji York wrote:
> That would be great, especially because we don't have any Debian slaves
> yet.
I can provide cycles on a Debian machine as well, it's a "testing"
installation kept more-or-less current.
--
Thomas
___
Zope3-dev mailing list
Zope3-
On Tue, 23 Aug 2005 08:36:22 -0400, Benji York wrote:
>> ACK
>
> I assume this means "acknowledged" as opposed to "an exclamation of
> surprised disgust".
ACK
--
Thomas Lotze
___
Zope3-dev mailing
simple timing test suggests that using setdefault is actually faster,
the construction of empty dicts and objects notwithstanding.
> If you're looking for a simplification here, I'd use "+" rather than "%"
> above, for example:
>
>
23 matches
Mail list logo
