Evan Simpson wrote:
Jim Fulton wrote:
...
Unless I'm misunderstanding something fundamental here, in the TALES
context an adapter is essentially a function accepting a single
argument.
Yes, except s/function/callable
The adapted object that results from applying the adapter
function is either
Ian Bicking wrote:
Jim Fulton wrote:
One disadvantage I see with the cast notation is that it's
a bit jarring in:
a/b/(adapter)c/d
as the adapter is applied to a/b/c. The order just doesn't
seem quite right.
That is indeed jarring, especially since c isn't an object, it's just a
name, and
Casey Duncan wrote:
On Fri, 21 May 2004 09:07:24 -0400
Jim Fulton [EMAIL PROTECTED] wrote:
Jim Fulton wrote:
I've posted two proposals:
http://dev.zope.org/Zope3/TALESPathExpressionAdapters
Proposes a mechanism for easily using adapters in TALES expressions.
| So far, I like:
|
| foo/bar-dc/title
|
| the best.
OTOH, for 'valid' xhtml, u would have to write:
foo/bar-gt;dc/title
Totally defeating the purpose. One may argue that this would not be
part of the output, but it breaks the editors (at least nxml-mode).
--
Sidnei da Silva [EMAIL
Sidnei da Silva wrote:
| So far, I like:
|
| foo/bar-dc/title
|
| the best.
OTOH, for 'valid' xhtml, u would have to write:
You mean well-formed.
foo/bar-gt;dc/title
Totally defeating the purpose. One may argue that this would not be
part of the output, but it breaks the editors (at least
| You mean well-formed.
Right.
| Wrong. Double check the spec. (I did. :)
|
| http://www.w3.org/TR/2004/REC-xml11-20040204/#NT-AttValue
|
| You only need to escape the less-than because there's no way to
| mistake a-b as a tag.
Beats me :)
--
Sidnei da Silva [EMAIL PROTECTED]
Jim Fulton wrote:
Sidnei da Silva wrote:
| So far, I like:
| | foo/bar-dc/title
| | the best.
OTOH, for 'valid' xhtml, u would have to write:
You mean well-formed.
foo/bar-gt;dc/title
Totally defeating the purpose. One may argue that this would not be
part of the output, but it breaks the
Hi there,
I try to access the Zope cvs anonymously according to the instructions.
However it fails.
Has anything changed, or is this temporarily.
Robert
[EMAIL PROTECTED]:/home/zope/Products cvs -d
:pserver:[EMAIL PROTECTED]:/cvs-repository co Zope
cvs [checkout aborted]: connect to
[robert rottermann]
I try to access the Zope cvs anonymously according to the instructions.
However it fails.
Has anything changed, or is this temporarily.
:pserver: access is disabled for now, because of recently announced security
holes. It will be enabled again when (and if?) CVS is
I would like to understand whether there's a chance that this issue gets
solved for the 2.7.1 release.
thanks in advance!
Jens
--
NEU : GMX Internet.FreeDSL
Ab sofort DSL-Tarif ohne Grundgebühr: http://www.gmx.net/dsl
___
Zope-Dev maillist -
Tres Seaver wrote:
Jim Fulton wrote:
Sidnei da Silva wrote:
| So far, I like:
| | foo/bar-dc/title
| | the best.
OTOH, for 'valid' xhtml, u would have to write:
You mean well-formed.
foo/bar-gt;dc/title
Totally defeating the purpose. One may argue that this would not be
part of the output, but
Tim Peters wrote:
[robert rottermann]
I try to access the Zope cvs anonymously according to the instructions.
However it fails.
Has anything changed, or is this temporarily.
:pserver: access is disabled for now, because of recently announced security
holes. It will be enabled again when
robert rottermann wrote:
thanks for your answer,
what I would like to download is CMFSetup
ViewCVS can give you a tarball:
http://cvs.zope.org/CMF/CMFSetup/CMFSetup.tar.gz?tarball=1
The major downside there is not being able to 'cvs up' to track changes;
given that that product is still
[EMAIL PROTECTED]
thanks for your answer,
what I would like to download is CMFSetup
I think that's still in CVS only, and so long as :pserver: access remains
disabled you simply can't get it that way.
You could go to
http://cvs.zope.org/CMF/CMFSetup/
and use the Download tarball link
Jim Fulton wrote:
IMO, if we take this route, we should think of the notation as
providing an alternate traversal operator. That is, there is
syntax that either modifies or replaces /, so of the examples
above, only:
context/*dc/title
In that case, I'd be happy to consider adaptation as
Evan Simpson wrote:
Jim Fulton wrote:
IMO, if we take this route, we should think of the notation as
providing an alternate traversal operator. That is, there is
syntax that either modifies or replaces /, so of the examples
above, only:
context/*dc/title
In that case, I'd be happy to consider
Jim Fulton wrote:
Evan Simpson wrote:
Jim Fulton wrote:
IMO, if we take this route, we should think of the notation as
providing an alternate traversal operator. That is, there is
syntax that either modifies or replaces /, so of the examples
above, only:
context/*dc/title
In that case, I'd be
On Thu, May 27, 2004 at 10:00:50PM +0200, Tonico Strasser wrote:
Jim Fulton wrote:
On IRC, Martijn Faassen suggested (brainstormed really :) '#', as in:
context#dc/title
I like this becase # kinda looks like a special kind of slash. :)
Looks ok to me.
Hm, special kind of slash ...
Jim Fulton wrote:
We don't. In fact, one could argue that adaptation is a bit like
a different kind of traversal. In fact, in Zope 3, we already have
a notion of this. In general, in Zope 3 paths, we can say:
foo/++namespace++name
where /++namespace++ can be thought of as a special form
On Thu, May 27, 2004 at 03:55:23PM -0500, Garrett Smith wrote:
So, we could also use something like:
content/++adapter++dc/title
but I think people want something more concide for ZPT.
I prefer this notation, even though it's more verbose. I think it should
be supported along with
20 matches
Mail list logo
