270ccc546a57df7e295bf9bd43a189a8ebd32c26
If the value returned by a field is the literal 'null' or an empty string, then the field is empty (empty input, no valued option selected, etc...). On the other hand, because openerp.base.search.Field.get_value returns a *javascript* value it can be the literals '0' or 'false'. Those are falsy in a boolean context (for good reasons, for 'false') but they should still count as the field having a value. I'm guessing this part is going to reach "spin off in its own per-field method" complexity pretty soon. bzr revid: xmo@openerp.com-20110324184713-sf7skv34s9824ge6
About OpenERP --------------- OpenERP is a free Enterprise Resource Planning and Customer Relationship Management software. It is mainly developed to meet changing needs. The main functional features are: CRM & SRM, analytic and financial accounting, double-entry stock management, sales and purchases management, tasks automation, help desk, marketing campaign, ... and vertical modules for very specific businesses. Technical features include a distributed server, flexible workflows, an object database, dynamic GUIs, customizable reports, NET-RPC and XML-RPC interfaces, ... For more information, please visit: http://www.openerp.com
Languages
Python
49.6%
JavaScript
47.8%
SCSS
2%
CSS
0.3%
HTML
0.2%