On 04/12/10 11:27 -0800, vengfulsquirrel wrote: > Hey Cédric, > > Is it possible to enumerate the general cases where this ids > conversion is needed? I think knowing the use cases would really make > choosing a design easier. Right now I can't tell what methods would > be affected.
It is required when the system expect to find a method on a children Model
because it inherits some behavior from one of parents. Per example:
- button method (ids)
- on_write method (ids)
- default method
- on_change method
(perhaps more but I don't find now)
So only some methods receive ids and if so the ids must be the one from the
parent and not the one from the children.
But now, I realize that the methods that uses ids will not be called without
the intervention of a developper to activate some functionnality. So perhaps
we could drop the convertion and let the developper handle it.
> Is this conversion meant to be used arbitrarily by a module
> developer?
It is something that could be excepected from the framework as we got some
kind of inheritage.
> Seems more likely that it is used internally by base
> tryton methods, is that right?
No, this functionnality could be used by any modules.
--
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/
pgpfrRvvI2REt.pgp
Description: PGP signature
