[Zope-CMF] Re: Re: CMF roadmap update
On Tue, 25 Apr 2006 20:21:09 +0100, Martin Aspeli [EMAIL PROTECTED] wrote: On Tue, 25 Apr 2006 16:33:01 +0100, David Pratt [EMAIL PROTECTED] wrote: Hi Jens. Z3 has it own uid facilities. I guess folks could pick this up through five could they not? Its all moving in that direction in any case. Plone doesn't have UID, but Archetypes does. This is used primarily for the reference engine, and it's one of the things we'd really like to componentise out to make it independent of Archetypes. I'd say we should aim to have one UID implementation at the Zope3 level and all use that, if it's feasible. I'm not quite sure which part of Z3 you're talking about though, so I can't comment on whether it's feasible. ... and Raphael says CMFEditions may depend on this. Martin -- (muted) ___ 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
Re: [Zope-CMF] Re: Re: CMF roadmap update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26 Apr 2006, at 07:40, Martin Aspeli wrote: On Tue, 25 Apr 2006 20:21:09 +0100, Martin Aspeli [EMAIL PROTECTED] wrote: On Tue, 25 Apr 2006 16:33:01 +0100, David Pratt [EMAIL PROTECTED] wrote: Hi Jens. Z3 has it own uid facilities. I guess folks could pick this up through five could they not? Its all moving in that direction in any case. Plone doesn't have UID, but Archetypes does. This is used primarily for the reference engine, and it's one of the things we'd really like to componentise out to make it independent of Archetypes. I'd say we should aim to have one UID implementation at the Zope3 level and all use that, if it's feasible. I'm not quite sure which part of Z3 you're talking about though, so I can't comment on whether it's feasible. ... and Raphael says CMFEditions may depend on this. Depend on what exactly..? Archetypes UIDs? Z3 UIDs? CMFUid? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFETx6qRAx5nvEhZLIRAkghAKCEb5Tenv9CuG9X178ra+01STF6zACfXSMO FM7BWE1o7Opk60iRihzVniM= =7fMZ -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
Re: [Zope-CMF] Re: Re: CMF roadmap update
CMFEditions makes heavy use of CMFUid, though if an alternate preferred uid generation mechanism were decided upon, it likely wouldn't be hard to switch. Alec On 4/26/06, Jens Vagelpohl [EMAIL PROTECTED] wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 26 Apr 2006, at 07:40, Martin Aspeli wrote: On Tue, 25 Apr 2006 20:21:09 +0100, Martin Aspeli [EMAIL PROTECTED] wrote: On Tue, 25 Apr 2006 16:33:01 +0100, David Pratt [EMAIL PROTECTED] wrote: Hi Jens. Z3 has it own uid facilities. I guess folks could pick this up through five could they not? Its all moving in that direction in any case. Plone doesn't have UID, but Archetypes does. This is used primarily for the reference engine, and it's one of the things we'd really like to componentise out to make it independent of Archetypes. I'd say we should aim to have one UID implementation at the Zope3 level and all use that, if it's feasible. I'm not quite sure which part of Z3 you're talking about though, so I can't comment on whether it's feasible. ... and Raphael says CMFEditions may depend on this. Depend on what exactly..? Archetypes UIDs? Z3 UIDs? CMFUid? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (Darwin) iD8DBQFETx6qRAx5nvEhZLIRAkghAKCEb5Tenv9CuG9X178ra+01STF6zACfXSMO FM7BWE1o7Opk60iRihzVniM= =7fMZ -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 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: CMF roadmap update
Tres Seaver wrote: Paul Winkler wrote: I saw Philip W. do a working prototype of this at the PyCon Dallas sprints. I don't know if anything happened with this after PyCon, and it would need at least some UI work. If the UI is to integrate with the CMF skins tool, I suspect there will need to be a thin layer of CMF-specific UI written as well. IIRC, Philip's prototype just dumped the templates into the Zope root, or maybe into the current folder, I forget. I believe the work which Philipp and I did at PyCon will land for Zope 2.10 / Five 1.4. Until then, we don't have any story for view customization: sites which depend on such customization will need to continue using the skins. Once that work lands, we should be able to integrate the UI from the prototype, which shows the template-driven views for a given object, and allows creation of a new templatee in the nearest site, shadowing the global view. Are you talking about the 'zpt customization prototype' that won't be ready in time for Five 1.5/Zope 2.10 according to the log message for http://mail.zope.org/pipermail/checkins/2006-April/001310.html? I'm not happy with limiting TTW customizations to zpt customizations. That will force people to add their custom logic to the templates. The goal of views was to move in the opposite direction. But I have no time to work on something better. Cheers, Yuppie ___ 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
Re: [Zope-CMF] Re: CMF roadmap update
I am using it rather heavily. The overengineery impression comes from the fact that it is intended to be highly pluggable (CMF-style, i.e. by replacing tools). For example I always replace the generator with something more robust than a simple counter. Using it is straight forward, you just do uid = handler.register(anObject) and anObject = handler.getObjectByUid(uid). Stefan On 25. Apr 2006, at 16:46, Jens Vagelpohl wrote: Well, I have my own opinion about that, but the course of action depends mostly on those people who are using it. No one seems to, judged by the complete silence. -- Anything that happens, happens. --Douglas Adams ___ 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: CMF roadmap update
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: Tres Seaver wrote: Paul Winkler wrote: I saw Philip W. do a working prototype of this at the PyCon Dallas sprints. I don't know if anything happened with this after PyCon, and it would need at least some UI work. If the UI is to integrate with the CMF skins tool, I suspect there will need to be a thin layer of CMF-specific UI written as well. IIRC, Philip's prototype just dumped the templates into the Zope root, or maybe into the current folder, I forget. I believe the work which Philipp and I did at PyCon will land for Zope 2.10 / Five 1.4. Until then, we don't have any story for view customization: sites which depend on such customization will need to continue using the skins. Once that work lands, we should be able to integrate the UI from the prototype, which shows the template-driven views for a given object, and allows creation of a new templatee in the nearest site, shadowing the global view. Are you talking about the 'zpt customization prototype' that won't be ready in time for Five 1.5/Zope 2.10 according to the log message for http://mail.zope.org/pipermail/checkins/2006-April/001310.html? Yes. I am most disappointed to see that work shelved for another six months. I am not convinced our release cycle is working in our favor here. I'm not happy with limiting TTW customizations to zpt customizations. That will force people to add their custom logic to the templates. The goal of views was to move in the opposite direction. Customization is hard: without TTW modules we *can't* do customization of arbitrary view logic. The templates which the prototype produced were going to enable the inline Python feature (currently possible in Z3's ZPT Page content type), which would have allowed a somewhat more manageable chunk of that use case. Those templates would then be wired together with the original view class from which the customization was done to create the overriding view. But I have no time to work on something better. Nor I. CMF can't do more than Zope2 / Zope3 / Five will support. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFET0Dq+gerLs4ltQ4RAhTXAJ4jp9UhaCX7hL+S+E1NONBuixFhbwCg2Ozu QqI2op4uKLxDj4pbRqYX6LU= =Bhn+ -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] [dev] 'request' in expression context
Hi! In createExprContext 'request' is currently set to getattr(object, 'REQUEST', None). 'object' might be None, making 'request' None as well. Would anybody mind if I change that to getattr(portal, 'REQUEST', None)? AFAICS portal is always available and can acquire REQUEST. If there are no objections I'll fix this in CMF 1.5, 1.6, 2.0 and trunk. Cheers, Yuppie ___ 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] CMFFolderExport Add-on Available
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Overview The implementation is dirt simple: it just leverages the content space export import facilities of GenericSetup, including the stock adapters registered by GenericSetup and CMFCore. If you don't like the filesystem representation those adapters produce (generally identical to the DAV source view) you can register your own adapters instead. Once the product is installed, folderish content has two new views available: '@@export.tar.gz' -- synthesizes the tarball '@@upload_tarball' -- allows you to upload the tarball, replacing any existing content. Currently the page template for this view does not play with the skinning machinery. Links - Product home, http://palladion.com/home/tseaver/software/CMFFolderExport - README, http://palladion.com/home/tseaver/software/CMFFolderExport/README.txt - Download 0.1 tarball, http://palladion.com/home/tseaver/software/CMFFolderExport/CMFFolderExport-0.1.tar.gz TODOs - Make the template play with skins. ;) - Wire up a profile which creates an action for folderish content types. - Fold it back into CMFCore. Tres. - -- === Tres Seaver +1 202-558-7113 [EMAIL PROTECTED] Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org iD8DBQFET6dQ+gerLs4ltQ4RAgaCAKCZquueZKyCXI4O+8bEt55NBeUA9ACfaiKY 5LWHMFEqHSLnL23Ra7Q1UU0= =x3w2 -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
