I second the need for versioning (keeping historical data). The osv_temporal example looks good, so you might as well add this class to the framework. Or integrate the idea a little further and build it into the existing classes, giving the option to enable it. Ofcourse, it would only be really useful if it is easy to add this history to any form. It would be amazingly powerful to look at a record and see the changelog below (user8 changed field4 from 'blabla' to 'blingbling' on 15/01/2008 12h35) Because people make mistakes (some make a lot actually :) ). And you need an easy way to track this. (Particularly seeing recently changed values)
Also, there are some concepts in Filemaker which are really good. 'looked up' fields would be nice performance-wise: copy data from a related table and only update when the original changed. And the way Filemaker predefines querysets is nice. The way you build queries is by creating relationships and defining query clauses, and afterwards you use them by name. It's a very clean separation of queries and code. That said, TinyERP is already a very well built system. You could also do with better documentation though :) _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
