On 03/03/11 19:29 +0100, Mathias Behrle wrote: > * Betr.: " [tryton-dev] ir.default removal" (Thu, 3 Mar 2011 18:27:20 +0100): > > Hi Nicolas, > > > Yesterday we talked on IRC, about removing the ir.default object from > > tryton. > > > > Our main issues with ir.default are: > > > > - No access right what so ever: anybody can set a default value > > for anybody else, > > - No multi-company support: A default value set through this > > feature will be used for every companies > > - Can break workflow or other stuffs: A user can set as default > > the value of states to a certain state and thus it might break > > some logic that relies on this field. > > > > Moreover it seems that the current use of this feature can be replaced > > either by: > > > > - making tryton's modules more clever > > - customizing the company object to set default company-wise. > > > > Does anybody have strong feelings about this issue or could we go on > > with their removal ? > > The feature to enable an user to adapt the application to his preferences is > still very attractive for me. Wouldn't it be able to harden the feature to > only > offer per user and company settings without completely removing it?
The current design makes the enforcement very difficult and perhaps
impossible because:
- the dialog box is design in the client (so no module customization)
- the database schema is very simplistic:
- value: Text field
- clause: Text field
- it is not possible to add business rules because it is defined in deeply
in the kernel
--
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/
pgpij7QV1QkeL.pgp
Description: PGP signature
