Re: [Framework-Team] [Plone-cvs] r40085 - buildouts/plone-coredev/branches/4.1/plips
On 9/20/10 17:58 , Rob Gietema wrote: > Author: robgietema > Date: Mon Sep 20 15:58:35 2010 > New Revision: 40085 > > Added: > buildouts/plone-coredev/branches/4.1/plips/plip10778-review-robgietema.txt > Log: > Added review for PLIP10778. > > Added: > buildouts/plone-coredev/branches/4.1/plips/plip10778-review-robgietema.txt > == > --- (empty file) > +++ > buildouts/plone-coredev/branches/4.1/plips/plip10778-review-robgietema.txt > Mon Sep 20 15:58:35 2010 > @@ -0,0 +1,55 @@ > +PLIP 10778: Standalone UUID implementation > +== ... > +- The test code is in testing.py and tests.py, I prefer this being in a tests > + folder to not mess up the package root. testing.py is something else: it contains utility code for writing tests. It does not contain tests itself. This is a common pattern. Wichert. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] FWT Meeting Minutes – Sept 7, 2010
On 9/20/10 8:56 AM, Eric Steele wrote: > Sorry for the delay getting these out. > > • #10280 – Allow overriding the tag on a per-template basis > • How common of a need is this? > • Using the viewlet instead allows customization / view > • Decision: Declined I'm sad to see this decision. Filling a slot is much easier than registering a new viewlet, works for non-view-based templates too, and seems low-risk to me. Have you ever tried to explain to someone how to change the ? > • #11021 – Simple theming customizations through the plone interface > • plone.app.themeeditor looks to be the way forward in this > area of site customization > • Like the idea of having text areas for editing css/js, but > not as a proxy for dtml documents. > • Render the two directly instead of proxying. > • Implement as an add-on, resubmit for 4.2 > • Decision: Declined We discussed this already on IRC, but just for the record: I don't think either David Bain or I have much time to put into plone.app.themeeditor on an ongoing basis, so we shouldn't let a hope for that to mature prevent inclusion of something that is less ambitious but still a useful improvement, IMHO. -- David Glick Web Developer davidgl...@groundwire.org 206.286.1235x32 Groundwire: You Are Connected http://groundwire.org ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] FWT Meeting Minutes – Sept 7, 2010
Sorry for the delay getting these out. • #10280 – Allow overriding the tag on a per-template basis • How common of a need is this? • Using the viewlet instead allows customization / view • Decision: Declined • #10964 – Asynchronously fetch suggestions for 404 Not Found Page • Do we still want to consider this? • Laurence hasn't had time to do benchmarks • Pass it along to implementation stage, ask for benchmarks as a deliverable? • Provide ability to disable suggestions, allow site admins to decide • Decision: Declined • #11003 – Content governance metadata • Is this a common need? • Sounds useful, but are people actually going to use this? • Should be developed as an add-on • Inappropriate to change the behavior of existing fields (expiration date) at this point • Decision: Accepted • #11013 – ARIA Landmark Roles for accessibility • Looks extremely low-risk • Previous experience of this resulting in JAWS getting confused with ARIA content. Will need testing • Make changes in markup, not Javascript. Make it opt-in. • Will XDV have problems? Parser ignores namespaces. • Decision: Accepted • #11016 – Configurable breadcrumbs • Like the idea, are there really no risks? • Would like to see this as an add-on • Too much configurability. • Decision: Declined • #11017 – Tags MultiSelectionWidget w/scrollbar & checkboxes • No jQuery UI. • Concept is good enough, no need to provide a proof-of-concept. • Decision: Accepted • #11021 – Simple theming customizations through the plone interface • plone.app.themeeditor looks to be the way forward in this area of site customization • Like the idea of having text areas for editing css/js, but not as a proxy for dtml documents. • Render the two directly instead of proxying. • Implement as an add-on, resubmit for 4.2 • Decision: Declined • #11025 – Content Batch Editing • Keep as an add-on for now • Some batch editing already included: name, id, workflow, expiration. • Decision: Declined • #11065 – Ship with plone.app.caching • Immediate consensus • Decision: Accepted Recording available at http://apps.calliflower.com/recording/download/8320?rec_key=3441aceb551f83efd252ed71ef055ed43e234bfa Next meeting will be Sept 21, 2010. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
