+1. Create a new field for barely similar things is not productive.
Regards. 2014-07-17 20:30 GMT+02:00 Holger Brunn <[email protected]>: > > field type etc. We don't want that since lots of users doesn't know what > > integer and float, or any other data type is. Also because we don't want > > to make data validation. The idea is to keep it simple for developer and > > user. > > why don't you write a widget for fields.serialized that does what you > want? If > you make this configurable (pass attribute(s) about what fields you expect, > forms api comes to mind) and extensible, that would be a great > contribution I > think. > > -- > Therp - Maatwerk in open ontwikkeling > > Holger Brunn - Ontwerp en implementatie > > mail: [email protected] > web: http://therp.nl > _______________________________________________ > Mailing list: https://launchpad.net/~openerp-community > Post to : [email protected] > Unsubscribe : https://launchpad.net/~openerp-community > More help : https://help.launchpad.net/ListHelp > >
_______________________________________________ Mailing list: https://launchpad.net/~openerp-community Post to : [email protected] Unsubscribe : https://launchpad.net/~openerp-community More help : https://help.launchpad.net/ListHelp
