On 03/03/12 12:19 +0100, Cédric Krier wrote: > On 03/03/12 12:12 +0100, Albert Cervera i Areny wrote: > > A Dissabte, 3 de març de 2012 11:35:45, Cédric Krier va escriure: > > > > IMHO the problem with current workflow (v2.2) is that the flow is kept > > > > in > > > > the database. That is solved in the new design but the problem is that > > > > permissions are managed in python code. > > > > > > > > I think we want "workflow" to be handled in python (that should happen > > > > when we have the fields.Button with the appropriate states attribute) > > > > and "group permissions" to be handled in the database (just like we do > > > > with model access and rules). > > > > > > Indeed, I think the main issue is the button definition because it > > > have to combine 2 kind of states: > > > > > > - the workflow depending on the state of the Model > > > - the permission depending on the user group > > > > > > So yes, it will be great to manage the groups in the database but the > > > workflow must be managed in the code. > > > But any way, this is for the button improvement of Tryton. For now, with > > > the current "no-workflow" design, we don't loose a functionality as the > > > button definition was (and is still) managed in the XML. > > > > Ok. So we agree in the in the final goal. > > I will try to update the current patch, I think I have an idea on how to > do it that will not change too much the current patch.
I made the implemenation in the Set 7. -- Cédric Krier B2CK SPRL Rue de Rotterdam, 4 4000 Liège Belgium Tel: +32 472 54 46 59 Email/Jabber: [email protected] Website: http://www.b2ck.com/
pgpyEMaLwinS0.pgp
Description: PGP signature
