Zope 3.1 will include a new feature in METAL, the Macro Expansion Tag
Attribute Language used in page templates.
The implementation is largely complete, but some issues with it were
uncovered in the past week that have caused some re-evaluation of the
details. At this point, we discovered that su
Fred Drake wrote:
I'll do that. In particular, I propose:
1. The macro extension feature be associated with a new METAL
attribute, extend-macro. This must be used only in conjunction with
define-macro.
2. The define-macro/use-macro combination will become disallowed once more.
3. The METAL s
On 8/18/05, Shane Hathaway <[EMAIL PROTECTED]> wrote:
> Ok. It takes a while to twist my brain back into a mode that
> understands this stuff. Your solution adds capabilities without taking
> any away. +1.
Cool! Thanks for helping think about this.
> Now that I see this better, I'll retract m
Fred Drake wrote:
On 8/18/05, Shane Hathaway <[EMAIL PROTECTED]> wrote:
My use case for macro extension is as follows: a third party provides a
complex macro I'd like to reuse as a macro, but I want to replace only
certain slots in my macro. I need my macro to offer all of the slots
that the b
On 8/18/05, Shane Hathaway <[EMAIL PROTECTED]> wrote:
> My use case for macro extension is as follows: a third party provides a
> complex macro I'd like to reuse as a macro, but I want to replace only
> certain slots in my macro. I need my macro to offer all of the slots
> that the base macro offe
Hello to all,
Maybe a bit to general question .But is there possibilty to send status
information
about a Zope3 Server via SSL to a different remote system
Thanks for any sort of feedback
Rgds
Gottfried
___
Zope3-dev mailing list
Zope3-dev@zope.org
Fred Drake wrote:
T3 should be filling the slot A defined in T2, and T2 should be filling the
slot A defined in T1; this was not happening when T2 extended T1. If T2 did
not extend T1, but simply used it, this worked as expected. Having this slot
construct behave differently in the case of ma
Not a good reason, just laziness -- basically our app is deployed in
two pieces, and it's easier to write the installer for the piece
containing zope.proxy if you don't need to worry about the extension
module. Actually, that's only true for our Win32 target. Just
thought I'd check before spendin
On 8/18/05, Nathan R. Yergler <[EMAIL PROTECTED]> wrote:
> We're using some of the Zope libraries for non-Zope apps, and need to
> include zope.proxy. We're not at the point where we care about
> performance (well, much), so it would make life easier if we had a
> Pure Python version of zope.proxy
We're using some of the Zope libraries for non-Zope apps, and need to
include zope.proxy. We're not at the point where we care about
performance (well, much), so it would make life easier if we had a
Pure Python version of zope.proxy. Has anyone created such a
creature? I glanced through the SVN
Gary brought up an issue with the macro extension work that Shane did in the
page templates code for Zope 3.1; the relevant code does not exist in Zope
2.x or 3.0.x. Gary's bug report is issue 440 in the Zope 3 collector:
http://www.zope.org/Collectors/Zope3-dev/440
There appears to be a d
11 matches
Mail list logo
