[Zope-CMF] CMF Tests: 9 OK
Summary of messages to the cmf-tests list. Period Mon Jun 23 11:00:00 2008 UTC to Tue Jun 24 11:00:00 2008 UTC. There were 9 messages: 9 from CMF Tests. Tests passed OK --- Subject: OK : CMF-1.6 Zope-2.8 Python-2.3.6 : Linux From: CMF Tests Date: Mon Jun 23 21:45:22 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-June/009128.html Subject: OK : CMF-1.6 Zope-2.9 Python-2.4.4 : Linux From: CMF Tests Date: Mon Jun 23 21:46:52 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-June/009129.html Subject: OK : CMF-2.0 Zope-2.9 Python-2.4.4 : Linux From: CMF Tests Date: Mon Jun 23 21:48:24 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-June/009130.html Subject: OK : CMF-2.0 Zope-2.10 Python-2.4.4 : Linux From: CMF Tests Date: Mon Jun 23 21:49:54 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-June/009131.html Subject: OK : CMF-2.1 Zope-2.10 Python-2.4.4 : Linux From: CMF Tests Date: Mon Jun 23 21:51:24 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-June/009132.html Subject: OK : CMF-2.1 Zope-2.11 Python-2.4.4 : Linux From: CMF Tests Date: Mon Jun 23 21:52:54 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-June/009133.html Subject: OK : CMF-trunk Zope-2.10 Python-2.4.4 : Linux From: CMF Tests Date: Mon Jun 23 21:54:24 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-June/009134.html Subject: OK : CMF-trunk Zope-2.11 Python-2.4.4 : Linux From: CMF Tests Date: Mon Jun 23 21:55:54 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-June/009135.html Subject: OK : CMF-trunk Zope-trunk Python-2.4.4 : Linux From: CMF Tests Date: Mon Jun 23 21:57:24 EDT 2008 URL: http://mail.zope.org/pipermail/cmf-tests/2008-June/009136.html ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Inconstancy with CA traversal
Hi, I'd appreciate some tips from someone who knows zope2 and Five traversal code. I've observed an unexpected effect that you can override a skin based template or python script with a browser view in a sub folder but not at the portal root. I'm trying to get my head round all the various traversal code in zope/five and would appreciate any tips from someone who knows this code well. I'm trying to find out if its possible making CA traversal have precedence over zope2 style traversal in every case? and if so, do others agree its a worth while change? For me it would allow the transparent customization of plone skins based code with browser views and mean I can keep my customizations entirely out of the skin level. plus its makes for a much simpler description of how traversal works. ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
[Zope-CMF] Re: Formlib implementation for folder contents
Have you thought about making contents a widget rather than a form? Then it would be easy combine with other forms on folderish items. Charlie Clark wrote: Hi, now that I've had a couple of months practice with browser views in general and formlib in particular and also because I've got a particular itch to scratch I've started on a formlib version of folder_contents and I've now got a skeleton version of the form. Well, I've got the form at least! What I've done so far: * a view based on EditForm (haven't quite mastered redirects in PageForm) but not using setUpEditWidgets - I pass the field values in as 'data'. Fields are distinguished from each other using the prefix argument field = form.FormField(f, n, item.id) # using an interface self.form_fields += form.FormFields(field) * turned the buttons into actions - probably the easiest part :-) * generate fields (Boolean for the checkboxes) * use a custom template to iterate through the folder items and call the appropriate widgets. Although this works it's a bit clumsy. This is the rather stripped-down HTML and I'm anticipating renaming on the form. form class=form action=. method=post enctype=multipart/form-data tal:attributes=action request/ACTUAL_URL table tr thSelect/th thName/th thLast Modified/th thPosition/th /tr tr tal:repeat=item context/contentValues td tal:content=structure python: view.widgets['%s.select' %item.id]()Checkbox/td td tal:content=structure python: view.widgets['%s.name' %item.id]()/td td tal:content=item/ModificationDate/td td tal:content=repeat/item/number/td /tr /table div class=buttons tal:loop tal:repeat=action view/actions tal:replace=structure action/render / /div /form While I can probably tidy this up to use a method in the view I'm not convinced it's entirely the right way to do this. But it works! I'll continue working - the actions themselves should be most straightforward on this but would appreciate any comments. 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 http://collector.zope.org/CMF for bug reports and feature requests ___ Zope-CMF maillist - Zope-CMF@lists.zope.org http://mail.zope.org/mailman/listinfo/zope-cmf See http://collector.zope.org/CMF for bug reports and feature requests
