Re: [Zope-CMF] Security declarations on adapters
Hi Yuppie, Am 07.09.2012, 09:01 Uhr, schrieb yuppie y.2...@wcm-solutions.de: [-] means that we don't want/need to convert this [?] means that we still have to decide if and how this should be converted [/] means unfinished Regarding RSS: you've written [/] ISyndicatable @@rss.xml (not hooked up): - [x] RSS.py - rss.View - [x] RSS_template.pt - rss.pt - [?] rssDisabled.pt What do you mean by not hooked up? There's not an appropriate action but the template is configured. As syndicatability is determined by a marker interface I don't think we need to have a disabled view for it. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Security declarations on adapters
Hi Charlie! Charlie Clark wrote: Am 07.09.2012, 09:01 Uhr, schrieb yuppie y.2...@wcm-solutions.de: And I have a quick and dirty view implementation for local role/sharing. Reimplementing it based on formlib would be a lot of work, so maybe I should just check in my code. As I'm not even sure what it does I'd definitely suggest you check it in. Ok. I'd also be very interested in your skinless workaround. As luck would have it I was discussing CMF with someone and I think we should have it in the docs somewhere. Well. Basically it works out of the box. If you have a complete ZTK skin, you can delete the skins tool. The sites I converted just use the features that already have browser views in CMFDefault or customized browser views in my own code, so missing views like those for discussion were no problem. The biggest issue I had to fight with is the fact that zope.browserresource (or the Zope 2 specific version in Five) is much harder to use than static resources in a CMF DirectoryView. Some packages exist that try to provide better resources support, but I'm not aware of any package that resolves my issues. I really don't want to register each icon separately in zcml, but I want to be able to override single icons. And I want to have some control over the urls of the resources. I want files like 'robots.txt' and 'favicon.ico' in the root, other resources in subdirectories like 'images' or 'resources'. Currently I use browser:resourceDirectory to register one resources directory per layer, and a special view that walks through directlyProvidedBy(request).__iro__ to find the first layer that contains the requested resource. This is an expensive hack, but does what I need. I'm still fighting with HEAD and PROPFIND requests for resources. So far I wasn't able to figure out how ZTK handles these. The errors returned by Zope 2 are not useful. Some clients retry those requests several times because they interpret the errors as temporary. I would also like to add a quick install guide for anyone wanting to use CMFDefault as a springboard. Not sure what exactly you mean by springboard in this context. I didn't propose to pack all this in CMF 2.3. My list also contains the next steps after the release. Where is the list? I didn't mean a big list. Just the few steps I mentioned in the previous mail. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Security declarations on adapters
Hi Charlie! Charlie Clark wrote: Am 05.09.2012, 09:07 Uhr, schrieb yuppie y.2...@wcm-solutions.de: The setup of your doctest looks fine, you just have to enable syndication for the folder (app.site) to get the view. Tests landed yesterday and I also ran them with the oldstyle implementation. Good. What is, in your view, missing from a final release? Laurence proposed some changes for the utilities: https://mail.zope.org/pipermail/zope-cmf/2012-September/030381.html If we agree that's the way to go, I'd like to have his changes in CMF 2.3 before the final release. All the other unfinished tasks can be deferred to CMF 2.4. The last beta was at the end of March so maybe it's time for another one to include all the formlib stuff you've worked on? I use CMF trunk in production, so I don't need a beta release. But it might be a good idea if other people want a beta for testing. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Security declarations on adapters
Am 06.09.2012, 13:11 Uhr, schrieb yuppie y.2...@wcm-solutions.de: Good. What is, in your view, missing from a final release? Laurence proposed some changes for the utilities: https://mail.zope.org/pipermail/zope-cmf/2012-September/030381.html If we agree that's the way to go, I'd like to have his changes in CMF 2.3 before the final release. Unless something downstream is dependent on these kind of changes I don't see any reason to including them at this late stage. All the other unfinished tasks can be deferred to CMF 2.4. Do we have a list of these unfinished tasks? Off the top of my head: correcting the docs. I'd also like to see at least minimal support for a WYSIWYG editor for HTML-text fields. Not sure if this should be part of CMF or a standalone formlib addition because of the external dependencies. The last beta was at the end of March so maybe it's time for another one to include all the formlib stuff you've worked on? I use CMF trunk in production, so I don't need a beta release. But it might be a good idea if other people want a beta for testing. I definitely think another beta would make sense: my own sites don't use trunk simply what PyPI spits out. How can we get the sphinxified docs into the release process? Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Security declarations on adapters
On 6 September 2012 14:06, Charlie Clark charlie.cl...@clark-consulting.eu wrote: Am 06.09.2012, 13:11 Uhr, schrieb yuppie y.2...@wcm-solutions.de: Good. What is, in your view, missing from a final release? Laurence proposed some changes for the utilities: https://mail.zope.org/pipermail/zope-cmf/2012-September/030381.html If we agree that's the way to go, I'd like to have his changes in CMF 2.3 before the final release. Unless something downstream is dependent on these kind of changes I don't see any reason to including them at this late stage. I think the downsides from leaving it out are: * Another branch of five.localsitemanager to maintain. * Incompatibility between CMF 2.3 and Zope 4 once the parent pointer changes go in. Plone is unlikely to make a CMF upgrade until it removes its CMFDefault dependency. Laurence The main downside to leaving the changes out is the necessity of another five.localsitemanager branch to maintain. The changes are compatible with CMF 2.2, but it may not play nicely with the ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Security declarations on adapters
Hiya Laurence, Am 06.09.2012, 14:46 Uhr, schrieb Laurence Rowe l...@lrowe.co.uk: I think the downsides from leaving it out are: * Another branch of five.localsitemanager to maintain. * Incompatibility between CMF 2.3 and Zope 4 once the parent pointer changes go in. What's the timescale for that? I don't see a problem with 2.3 being tied to 2.13 and 2.4 being for 2.13 which I assume Zope 4 is? 2.3 has a slew of changes throughout. Plone is unlikely to make a CMF upgrade until it removes its CMFDefault dependency. Please elaborate. Laurence The main downside to leaving the changes out is the necessity of another five.localsitemanager branch to maintain. The changes are compatible with CMF 2.2, but it may not play nicely with the Did you hit enter too early? Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Security declarations on adapters
Am 06.09.2012, 16:24 Uhr, schrieb yuppie y.2...@wcm-solutions.de: These changes provide better backward compatibility for code using CMF tools/utilities and better forward compatibility for running CMF on Zope 4. (*If* the proposed changes become part of Zope 4.) As you say, if. We don't have to wait for the Zope 4 release, just for the decision about the changes and for a five.localsitemanager release. Some small changes I made for CMF 2.3 don't play nice with the changes Laurence is working on. Point taken. All the other unfinished tasks can be deferred to CMF 2.4. Do we have a list of these unfinished tasks? There are the (incomplete) todo lists for browser views. I'd also like to revisit the names we did choose for the views and make them the default target of Actions. hm, I drew up the lists from the existing Scripts/Templates and thought it was complete. I've just checked again and can only find the following as not done: - [?] viewThreadsAtBottom.pt (structure) - [?] talkback_tree.pt (macros) - [?] setup_talkback_tree.py - [?] discitem_delete.py I thought we'd agreed not to make them the default for this release but remove the experimental label from the profile. Personally, I would like to see them as the default, not least because they nearly all have coverage. But, we shouldn't be packing too much into a single release. Maybe because you work with trunk you notice less? As soon as we have a complete replacement for the oldstyle skins I'd like to move those skins into a separate legacy package. +1 (I recently removed the complete skins tool from some of my CMF instances. That depends on a few hacks, but works quite well.) Sounds great but should be in a separate release. We also should consider moving the skins tool and the directory view code into a separate package. This could be in 2.4 That code has some dependencies that were removed from Zope 2 (Zope 4) and are not required for sites without skins tool. In the long run I have no ambitions to maintain that code and its dependencies. I don't think anyone does. Off the top of my head: correcting the docs. There are also duplicate DCWorkflow docs. Someone has to figure out if the old .stx docs are redundant and obsolete. There are equivalents for all .stx as .rst. I thought I had moved the files over but apparently not. I don't know what to do about the examples. But the .stx files can go. I think all the docs need a review but would like them to be visible first. I'd also like to see at least minimal support for a WYSIWYG editor for HTML-text fields. Not sure if this should be part of CMF or a standalone formlib addition because of the external dependencies. Some day I want to switch to z3c.form which has more add ons. I wouldn't spend too much time on formlib specific features. Again that would be for a later release. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Security declarations on adapters
I always like the solipsism of replying to myself! ;-) Am 06.09.2012, 16:58 Uhr, schrieb Charlie Clark charlie.cl...@clark-consulting.eu: hm, I drew up the lists from the existing Scripts/Templates and thought it was complete. I've just checked again and can only find the following as not done: - [?] viewThreadsAtBottom.pt (structure) - [?] talkback_tree.pt (macros) - [?] setup_talkback_tree.py - [?] discitem_delete.py Just checked on these and it looks like there are no views for discussions. So I've added a stub for them and, at least temporarily, moved these putative todos to discussion. A bit difficult to write tests for them as I'm currently getting the following error when using the classic versions: Error Type: AttributeError Error Value: SectionValue instance has no attribute 'structured_text_header_level' We can, and should, revisit naming again. IIRC you weren't happy with my choices of skins and widgets. Charlie -- Charlie Clark Managing Director Clark Consulting Research German Office Kronenstr. 27a Düsseldorf D- 40217 Tel: +49-211-600-3657 Mobile: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] Security declarations on adapters
Hi Charlie! Charlie Clark wrote: * is there an easy way to write the test for something that requires a tool and some content? The setup of your doctest looks fine, you just have to enable syndication for the folder (app.site) to get the view. * backporting the changes to the PythonScript I hit a roadblock that I can't use security declarations on the adapter. Fortunately, I was able to use the tool as a workaround but, apart from ripping out the PythonScript, I can't think of a better solution. I think CMF 2.3 should ship with a complete oldstyle skin. So it would be nice if you could get this working. But I guess it will be the last release with the oldstyle skin as default. In the long run it will become unmaintained. Any ideas? I'm also struggling with a convenient way of handling the difference in time formatting arising form using native datetime and DateTime with it's convenient rfc822 method Removing DateTime completely has no high priority. If you need it as a formatting tool, just use it. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests