Kamal Gill wrote:
Stability is especially important for those of us learning Zope 3, as
well as those who offer Zope 3 training. I realize Z3 is a fast-moving
target, but making existing books and documentation obsolete doesn't
help the adoption of such a fantastic collection of software,
[EMAIL PROTECTED] wrote:
what I like to see is something like:
html metal:use-macro=macro:StandardMacros/page
Such a macro could be lookuped by a ITALESExpression
called *macro* similar to the IContentProvider implementation.
The *StandardMacros* could be a mapping registred as a
Hi Philipp
ZCML as of Zope 3.2 is inconsistent and to someone who's new
and doesn't know every little detail from behind the scenes
it's very obscure. And then it also makes debugging hard
which has bitten me personally quite a few times. I explained
this is a reply to Rocky Burt in this
Hi Philipp
See also my (a little old) proposal at:
http://www.zope.org/Wikis/DevSite/Projects/ComponentArchitecture/Simpl
ifyMacroRegistration
Note: the proposal is a little bit old and I whould change the
directive browser:macros and make explicit use of a python factory
Hi Philipp
IMO it would be great to solve this properly, because one point of
using views is to have a fine control over what to publish
and what not.
And this is a bit broken at this point, currently.
Right, that's why page templates that just provide macros
should be registered
[EMAIL PROTECTED] wrote:
ZCML as of Zope 3.2 is inconsistent and to someone who's new
and doesn't know every little detail from behind the scenes
it's very obscure. And then it also makes debugging hard
which has bitten me personally quite a few times. I explained
this is a reply to Rocky
[EMAIL PROTECTED] wrote:
I think viewlets and contentproviders should have taken the
same road and used traversal namespaces. That's what they're for :).
I don't think so.
ITALESExpression are built for this use case.
I doubt that they were designed to *look up* things. They're
[EMAIL PROTECTED] wrote:
Hi Philipp
IMO it would be great to solve this properly, because one point of
using views is to have a fine control over what to publish
and what not.
And this is a bit broken at this point, currently.
Right, that's why page templates that just provide macros
Hi Philipp
Yes,
but this is only a problem how we lookup views/pages via /@@ in
templates.
That's how we lookup views. @@ is short for ++view++.
Traversal namespaces are the way to lookup things that are
not direct attributes.
The namespace ++view++ is in the first line a namespace
Yes, but speaking as another Zope3 learner, consistency and simplicity
(is orthogonality a word?) of the model/API is extremely important
too. I am in favor of such simplifying changes, as long as they are
properly documented and deprecation is properly applied.
For example: a deprecation
On Fri, Apr 21, 2006 at 01:03:58AM +0200, [EMAIL PROTECTED] wrote:
Hi Philipp
That confuses me even more. I *am* proposing changes to the
browser:page directive...
Hmm, never mind. I think I understand what you mean. You'd
like to see new directives, instead of changing the old
Hi Tonico
I once tried to understand how the default skin works --
after that I gave up the idea of creating a new ZMI skin
myself. (Especially the MacroMagic was difficult to
understand, but I want to try again someday).
I see, I personaly like macros, but it is true, sometimes
it is
Hi Philipp
[...]
I'll be fine with creating new directives instead of changing
the old ones, if that's what the majority prefers. But then
I'd very much like to see a Death Certificate for the old
directives made out for some time in the future (doesn't have
to be 2 releases, could be
[EMAIL PROTECTED] wrote:
I'll be fine with creating new directives instead of changing
the old ones, if that's what the majority prefers. But then
I'd very much like to see a Death Certificate for the old
directives made out for some time in the future (doesn't have
to be 2 releases,
Stability is especially important for those of us learning Zope 3, as
well as those who offer Zope 3 training. I realize Z3 is a fast-
moving target, but making existing books and documentation obsolete
doesn't help the adoption of such a fantastic collection of software,
IMO.
- Kamal
Hi Tonico
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On
Behalf Of Tonico Strasser
Sent: Friday, April 21, 2006 2:10 AM
To: zope3-dev@zope.org
Subject: [Zope3-dev] Re: RFC: The browser:page compromise
Philipp von Weitershausen schrieb:
I also think
16 matches
Mail list logo
