Chris Withers wrote:
Jim Fulton wrote:

Yup. We implemented:

ob/adapter:name


...which to me says:

"take adapter, apply to it object with name as a parameter"

That's close to the meaning of Even Simpson's Zope 2 ':' extension. Which is why we don't want to use this syntax for adapters.

...what I'd like it to say would give meaning to:

my_content_object/zapi:title

...meaning apply the title adapter from the zapi package to my_content_object, which was where I left things last time I came close to understanding Zoppe 3.

Well, what we did in bristol, enabled:

  my_content_object/zope:title

Which really gets a special adapter named "zope"
which exposes zapi-like functionality for ZPT.

What's the equivalent to that in today's Zope 3 land?

What I described still works. But we want to pick a different syntax, like:

  my_content_object#zope/title

which is equivalent to:

  ob/adapter:/name

and, in fact, you can say just:

ob/adapter:


I'm afraid neither of those means anything to me so your equivalency makes so sense :-S

right, which is why we want to pick a different syntax.

Steve pointed out some problems with the syntax, which
the above examples should make obvious.


Hurm :-S Don't suppose you have a use for that off hand?

Use for what?

Jim

--
Jim Fulton           mailto:[EMAIL PROTECTED]       Python Powered!
CTO                  (540) 361-1714            http://www.python.org
Zope Corporation     http://www.zope.com       http://www.zope.org

_______________________________________________
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists - http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )

Reply via email to