[Zope-CMF] CMF Tests: 6 OK
Summary of messages to the cmf-tests list. Period Tue Dec 9 12:00:00 2008 UTC to Wed Dec 10 12:00:00 2008 UTC. There were 6 messages: 6 from CMF Tests. Tests passed OK --- Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.5 : Linux From: CMF Tests Date: Tue Dec 9 20:48:34 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-December/010519.html Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.5 : Linux From: CMF Tests Date: Tue Dec 9 20:50:05 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-December/010520.html Subject: OK : CMF-trunk Zope-2.10 Python-2.4.5 : Linux From: CMF Tests Date: Tue Dec 9 20:51:35 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-December/010521.html Subject: OK : CMF-trunk Zope-2.11 Python-2.4.5 : Linux From: CMF Tests Date: Tue Dec 9 20:53:05 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-December/010522.html Subject: OK : CMF-trunk Zope-trunk Python-2.4.5 : Linux From: CMF Tests Date: Tue Dec 9 20:54:35 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-December/010523.html Subject: OK : CMF-trunk Zope-trunk Python-2.5.2 : Linux From: CMF Tests Date: Tue Dec 9 20:56:05 EST 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-December/010524.html ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] CMF add views and browser:page /
Am 09.12.2008 um 14:34 schrieb Martin Aspeli: Meh - of course, I meant: cmf:addview name=my.type for=Products.CMFCore.interfaces.IFolderish fti=..interfaces.IDexterityFTI class=.add.DefaultAddView permission=cmf.AddPortalContent / Hiya, I agree that many people do not understand immediately that Views are Adapters. This is partly conceptual but also related to conventions in ZCML and elsewhere: it's very natural in English to contract view adapters to views and subscriber adapters to subscribers, etc. which is why we get ZCML-directives like subscriber and browser. I think it is correct to encourage developers to move to the ZCML approach for configuring security and as the new add views are CMF specific using a special CMF directive would make this clearer. A separate but related issue might be how we deal with CMFDefault: you seem to refer to it in much the same way I do as the basis for more work as it provides so much useful functionality out of the box but Jens, Tres and others never tire of pointing out that it is actually only a demonstration of what's possible. Should we think of breaking the formlib stuff out of CMFDefault? So that it can be used without CMFDefault? I don't know whether it should move to its own package or CMFCore. Charlie -- Charlie Clark Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-938-5360 GSM: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] adding 'context' as an alias for 'object' in action expressions
Am 01.12.2008 um 16:49 schrieb Tres Seaver:
'context' is the canonical name for the object through which a
script or
templated was acquired (its aq_parent, in fact); 'here' is a
long-deprecated alias for 'context'. 'context' is like the 'self'
binding of a normal Python method.
Action expressions aren't scripts / templates, and don't have many of
the stock names ('context', 'container', 'template', 'script',
'traverse_subpath', 'namespace', 'subpath', 'options', 'modules',
'root') which scripts and templates offer; instead, they offer names
which are useful in writing action URLs (e.g., 'object_url',
'folder_url', 'portal', 'user_id', etc.) Their 'self' / 'context'
would
logically be the ActionInformation object, rather than the target
for
which the URL / condition is being computed.
And the proposal was to change the expression context for actions.
What
about CachingPolicyManager and DCWorkflow?
Exactly.
- -1 to the change from me. Writing TALES expressions involves
knowing
what the appropriate set of names are for the given usage.
Tres,
thanks very much for the explanation. I've probably missed it but my
experience has been that Actions and Workflow are the most difficult
parts of the CMF to work with because they don't conform entirely to
the way PythonScripts or PageTemplates behave but I think this is
largely down to a lack of user/developer documentation on what they
are and how to use them. I recently encountered the problem that user
defined action categories will be ignored by ListFilteredActionsFor().
Improving the documentation here would probably be the best solution.
Charlie
--
Charlie Clark
Helmholtzstr. 20
Düsseldorf
D- 40215
Tel: +49-211-938-5360
GSM: +49-178-782-6226
___
Zope-CMF maillist - Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf
See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
