[Zope-CMF] CMF Collector: Open Issues
The following supporters have open issues assigned to them in this collector (http://www.zope.org/Collectors/CMF). Assigned and Open jens - CachingPolicyManager: Support OFS.Cache.CacheManager, [Accepted] http://www.zope.org/Collectors/CMF/408 mhammond - Windows DevelopmentMode penalty in CMFCore.DirectoryView, [Accepted] http://www.zope.org/Collectors/CMF/366 Pending / Deferred Issues - Wrong cache association for FSObject, [Pending] http://www.zope.org/Collectors/CMF/255 - CMFSetup: Windows exports contain CR/LF, LF and even CR newlines, [Pending] http://www.zope.org/Collectors/CMF/266 - FSPropertiesObject.py cannot handle multiline input for lines, text attributes, [Deferred] http://www.zope.org/Collectors/CMF/271 - Can't invalidate skin items in a RAMCacheManager, [Pending] http://www.zope.org/Collectors/CMF/343 - CMFSetup: Workflow Tool export fails with workflows which have scripts, [Pending] http://www.zope.org/Collectors/CMF/373 - CMFCore.Skinnable.SkinnableObjectManager can merge skin data, [Pending] http://www.zope.org/Collectors/CMF/375 - Proxy Roles does't work for a Script using portal_catalog.searchResults, [Pending] http://www.zope.org/Collectors/CMF/380 - workflow notify success should be after reindex, [Pending] http://www.zope.org/Collectors/CMF/389 - 'except ...: pass' in CMFCore/TypesTool.py:_queryFactoryMethod() nullifies VerboseSecurity, [Pending] http://www.zope.org/Collectors/CMF/410 - Possible bug when using a BTreeFolder Member folder, [Pending] http://www.zope.org/Collectors/CMF/441 - Possible bug when using a BTreeFolder Members folder, [Pending] http://www.zope.org/Collectors/CMF/442 - Possible bug when using a BTreeFolder Member folder, [Pending] http://www.zope.org/Collectors/CMF/443 - Possible bug when using a BTreeFolder Members folder, [Pending] http://www.zope.org/Collectors/CMF/444 Pending / Deferred Features - Favorite.py: queries and anchors in remote_url, [Pending] http://www.zope.org/Collectors/CMF/26 - DefaultDublinCore should have Creator property, [Pending] http://www.zope.org/Collectors/CMF/61 - path criteria on Topic should honor VHM, [Pending] http://www.zope.org/Collectors/CMF/111 - Document.py: universal newlines, [Pending] http://www.zope.org/Collectors/CMF/174 - Add condition for transition's action like other action, [Pending] http://www.zope.org/Collectors/CMF/207 - Major action enhancement, [Pending] http://www.zope.org/Collectors/CMF/232 - portal_type is undefined in initialization code, [Pending] http://www.zope.org/Collectors/CMF/248 - CMFTopic Does Not Cache, [Deferred] http://www.zope.org/Collectors/CMF/295 - Wishlist: a flag that tags the selected action., [Pending] http://www.zope.org/Collectors/CMF/301 - CMFDefault should make use of allowCreate(), [Pending] http://www.zope.org/Collectors/CMF/340 - Nested Skins, [Deferred] http://www.zope.org/Collectors/CMF/377 - CatalogVariableProvider code + tests, [Pending] http://www.zope.org/Collectors/CMF/378 - manage_doCustomize() : minor additions, [Pending] http://www.zope.org/Collectors/CMF/382 - CMF needs View-based TypeInformation, [Pending] http://www.zope.org/Collectors/CMF/437 - Marker attributes should be deprecated, [Pending] http://www.zope.org/Collectors/CMF/440 ___ 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] DirectoryView, GenericSetup/skins, CMF 2.1
Hi all, I'm currently investigating registering DirectoryView's from regular python packages with GenericSetup+skins.xml. After debugging through this somewhat I have discovered that minimal paths described in skins.xml are made relative to $INSTANCE_HOME/Products. Obviously in a regular python package (living outside of Products) this means using minimal paths won't work. And of course since the actual location of the py package will vary from deployment to deployment, the logical approach would be to make the minimal path relative to the package home. Does anyone have any idea's on this? So far it looks like all other major cmf functionality can be used outside in a regular python package (living outside of Products). Perhaps I'm missing something? If this is indeed the case ... would you all entertain a proposal/patch from me providing a way to use skins from py packages that is b/w compatible with the current approach? Thanks, Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com News About The Server (blog) -- http://www.serverzen.net signature.asc Description: This is a digitally signed message part ___ 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: DirectoryView, GenericSetup/skins, CMF 2.1
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rocky Burt wrote: I'm currently investigating registering DirectoryView's from regular python packages with GenericSetup+skins.xml. After debugging through this somewhat I have discovered that minimal paths described in skins.xml are made relative to $INSTANCE_HOME/Products. Obviously in a regular python package (living outside of Products) this means using minimal paths won't work. And of course since the actual location of the py package will vary from deployment to deployment, the logical approach would be to make the minimal path relative to the package home. Does anyone have any idea's on this? So far it looks like all other major cmf functionality can be used outside in a regular python package (living outside of Products). Perhaps I'm missing something? If this is indeed the case ... would you all entertain a proposal/patch from me providing a way to use skins from py packages that is b/w compatible with the current approach? Hmmm, I thought this was landed already: I worked that out back in November / December, I think, on the 'tseaver-pkg_resources' branch. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFEsAfU+gerLs4ltQ4RApVYAKC2cDcC5iNMPJwR8166dOd0Si78JwCgvMkT bMpnYoZXjsPHBUjv0lZ0vvE= =c4B9 -END PGP SIGNATURE- ___ 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: DirectoryView, GenericSetup/skins, CMF 2.1
On Sat, 2006-08-07 at 15:30 -0400, Tres Seaver wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rocky Burt wrote: I'm currently investigating registering DirectoryView's from regular python packages with GenericSetup+skins.xml. After debugging through this somewhat I have discovered that minimal paths described in skins.xml are made relative to $INSTANCE_HOME/Products. Obviously in a regular python package (living outside of Products) this means using minimal paths won't work. And of course since the actual location of the py package will vary from deployment to deployment, the logical approach would be to make the minimal path relative to the package home. Does anyone have any idea's on this? So far it looks like all other major cmf functionality can be used outside in a regular python package (living outside of Products). Perhaps I'm missing something? If this is indeed the case ... would you all entertain a proposal/patch from me providing a way to use skins from py packages that is b/w compatible with the current approach? Hmmm, I thought this was landed already: I worked that out back in November / December, I think, on the 'tseaver-pkg_resources' branch. I just briefly inspected the tseaver-pkg_resources branch and I have a few questions/comments: 1. was this ever merged into trunk for cmf2.1 inclusion (my brief comparisons leads me to believe it was not) ? 2. it looks like the branch was put in place to make it so the cmf files themselves uses pkg_resources so they can be loaded from eggs and the like -- not that the paths pointed to by DirectoryViews could exist outside of Products (relative paths I mean) Perhaps I'm missing something? I'd welcome a technical explanation as to what exactly the branch tried to do and the ETA on inclusion into trunk. Thanks, Rocky -- Rocky Burt ServerZen Software -- http://www.serverzen.com News About The Server (blog) -- http://www.serverzen.net signature.asc Description: This is a digitally signed message part ___ 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
