openerp-expert-framework team mailing list archive

[<chanon.launchpad@xxxxxxxxx>]

Well putting it on the model might be a unique chance to generate index
accordingly. So don't drop it.

Also, I favour thinks that are model driven. I know it is not the current
focus, but the default view generation should be improved may be with extra
fieds or decorators. No xml for reference table means higher productivity
and better chance to migrate smoothly to upper version.

Christophe Hanon
ADINS

-----Original Message-----
From:
openerp-expert-framework-bounces+chanon.launchpad=gmail.com@lists.launchpad.
net
[mailto:openerp-expert-framework-bounces+chanon.launchpad=gmail.com@xxxxxxxx
unchpad.net] On Behalf Of "Lionel Sausin, de la part de l'équipe
informatique Numérigraphe"
Sent: 26 April 2012 12:04
To: openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Openerp-expert-framework] on the new API proposal

Le 26/04/2012 09:45, Valentin LAB a écrit :
> Some questions on the state of some part of the new API:
>
> - will reference type field value be converted to full object on the 
> fly (as a browse object does for many2one relation for example) ? If 
> no, what is the reason keeping this non-abstracted ?
>
> - will "_order" attribute be defined in the data model ? (I feel this 
> should go in the form descriptor, and have nothing to do in the data
> model...)
Having an order defined at the data model level let us get ordered browse
records, which can be quite handy at times. I don't think it weighs a lot on
the database either.
Lionel.

_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to     : openerp-expert-framework@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help   : https://help.launchpad.net/ListHelp