Re: [Framework-Team] My PLIPs for 3.1
On 12 dec 2007, at 00:03, Encolpe Degoute wrote: I'd like to see the following for 3.1: #214: Merge of CMFPlacefulWorkflow into CMFPlone/WorkflowTool CMFPlacefulWorkflow is now mature enough to be merge into the workflow tool: * since two major version there's no critical bug on it * GenericSetup support is implemented in the trunk * let him outside the workflow tool would leave 2 more monkey patches in Plone bundle * all page templates can be merged into a plone_workflow skin with the #210 Ok, how shall I say this? ;-) First of all, I truely like the idea of placeful workflows. The idea is good and I had a need for that in several occasions in the past. However, back in the days when it was introduced in plone I experimented with it and to be honest, the UI was a horrible mess. I understood the concept but the UI made me scream. And from what I've heard and seen afterwards, it hasn't become any better. That's why we (me,limi and others) decided to not have it installed by default to begin with. So, before I would say +1 I think that this beast needs a true overhaul for the UI. Workflow as it is is already hard to understand for many (end)users (mostly because it is not really a 'flow' (at least for users) but more a state-engine, but that's another discussion, and because it is being misused as a permissions managing system) and introducing placeful wfs makes it even harder. So, unless we fix this, I give this a -2. And it is far from trivial to do this right. Configlets need to be aware and redesigned. Containers need to have proper UI where you can assign (overrule) workflow(s!! see the other plip) in that place. And it doesn't end here. What about reassinging wfs? What happens with objects that have states that only exist in that workflow in that context? Are they reset to other states? Do you have to reassign new states as you can right now in the wf-configlet that we designed in Norway two years ago? What happens if you move an object to another folder where there's another workflow active. What happens with the permissions? How does it behave with multiple-workflows (see the other plip discussion)? How does it play with the current wf-confliget? As you can see, a lot of issues need to be addressed properly. And it is really a challenge to do this right. Especially because we introduce multiple-object workflows as well. Danny. ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
Re: [Framework-Team] My PLIPs for 3.1
On Dec 12, 2007, at 12:03 AM, Encolpe Degoute wrote: #214: Merge of CMFPlacefulWorkflow into CMFPlone/WorkflowTool CMFPlacefulWorkflow is now mature enough to be merge into the workflow tool: hmm, just to make sure, is this about merging the entire product into plone's workflow tool or just the necessary monkey patches that support the works of CMFPlacefulWorkflow? the former would certainly be too invasive for 3.1, especially since the product isn't used by default. on the contrary, being an optional add-on product there should be as little merging as possible — after all the idea is to componentize things to make them more easily pluggable, no? otoh if this is just about merging the two monkey patches in order to get rid of them (which i don't think it is), i wouldn't mind that. however, if alec's plip would make these obsolete by allowing to utilize the CA anyway, i think we should go for that — imho much cleaner — approach. so, i guess this would make it a -1 in the first case and a let's wait for more information in the second. andi -- zeidler it consulting - http://zitc.de/ - [EMAIL PROTECTED] friedelstraße 31 - 12047 berlin - telefon +49 30 25563779 pgp key at http://zitc.de/pgp - http://wwwkeys.de.pgp.net/ plone 3.0.4 released! -- http://plone.org/products/plone PGP.sig Description: This is a digitally signed message part ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
[Framework-Team] My PLIPs for 3.1
I'd like to see the following for 3.1: #196: GroupUserFolder removing There were and there are a lot of critical UI bugs around GroupUserFolder by PlonePAS. Because of these, several Plone release had to be delayed. We fix a lot of them in customer branch. #214: Merge of CMFPlacefulWorkflow into CMFPlone/WorkflowTool CMFPlacefulWorkflow is now mature enough to be merge into the workflow tool: * since two major version there's no critical bug on it * GenericSetup support is implemented in the trunk * let him outside the workflow tool would leave 2 more monkey patches in Plone bundle * all page templates can be merged into a plone_workflow skin with the #210 Regards, -- Encolpe Degoute INGENIWEB (TM) - S.A.S 5 Euros - RC B 438 725 632 17 rue Louise Michel - 92300 Levallois Perret - France web : www.ingeniweb.com - « les Services Web Ingénieux » Tel : 01.78.15.24.08 / Fax : 01 47 57 39 14 ___ Framework-Team mailing list Framework-Team@lists.plone.org http://lists.plone.org/mailman/listinfo/framework-team
