This is a response against the 'Tryton improvement against Open ERP'. It's not a comparaison, as Open ERP has MUCH more features than tryton that can not be listed here.
It's just an explanation on how Open ERP v5 implemented improvements of Tryton. We don't have the opposite description (what's in Open ERP which is not in Tryton) but Tryton implemented only a very small part of Open ERP v5. Client ###### - Provide IPv6 compliance Open ERP support IPv6 too. - Autodetect SSL connections Yes, in Open ERP you have to manually select you want to work with SSL. - Improve speed for communication between client and server with caches and compression - Improve speed with persisting socket connections - Improve robustness of the communication protocol Open ERP (v5) & Tryton made lots of speed improvement, in different areas. I tested 3 months ago, Open ERP is 30% faster than Tryton in average. My tests: * Browsing chart of accounts * Reading 1000 partners * Reading 1000 invoices * Reading 1000 * 1 invoice Open ERP was winning on this 4 tests (using NET-RPC for Open ERP, and the connection oriented system of Tryton) - Improve performance by removing glade This is a design decision. I don't agree at all it's an improvement. Glade allows RAD development by designing your screens using glade. The impacted performance is just when you open a new window and it does not change 0.01 second. I think it's better to use RAD tools than redevelopping everything from scratch and trying to win 0.01 sec on the client side. Glade is not used in Open ERP widgets, just in screens. So speed improvement is very very limited. - Auto detection of client plugins We try to avoid client plugins in Open ERP. Auto-detection is 2 lines :) - Colored widget in list edit mode Available in Open ERP. - Customization of client shortcut key binding Ok. - Allow to position focus on specific field Ok. - Set the cursor on the field that has to be changed after a validation error - Remove dependency on matplotlib In Open ERP too. - Allow to save graph to file In Open ERP too (web client :) - Allow to add action when clicking on graphs In Open ERP too, on any part of the graph instead of simple actions. * Allow to reorder tabs (now in OpenERP) In Open ERP too. - Add title on form view Open ERP already has title in form views. - Auto reload of menu after module installation We do reopen the menu too, after the configuration wizards. - Add operators on search widgets Implemented on the server, not yet on the client. But with a better approach. - Allow to use dates before 1900 In Open ERP too (curently in a branch that have to be merged) - Allow to work with very large lists of more than 20000 records instead of 80 You can change the limit in Open ERP. We choosed to limit at 80 by default for better speed improvement, but this can be configured in the action to 20.000 too :) - Allow to submit exceptions directly to bugtracker Maintenance module of Open ERP v5. - Format numbers according to the locales set in the users session In Open ERP v5 too. It's set according to the language and standard locale module, not in the user. I think it's better to keep using standards. - Allow to use the keyboard to navigate in tree views and menu In Open ERP too. - Allow for better appearence in list views to fill in an empty column - Allow to copy a selection of list values and paste it into any other application Open ERP does not (yet) support this. - Remember the column widths for each user when reopening forms Open ERP does not (yet) support this. - Carry out the sorting of reults on the server side Being implemented in v5. Already done in server, missing client parts for web, kde and GTK clients. Server ###### - Provide IPv6 compliance Open ERP support IPv6 too. - Allow to install modules from the command line You can use the -i MODULE option of Open ERP when launching the server. * Handle fuzzy translation We used a different (and I think much more better) approaches for translations. But we support fuzzy. Open ERP uses .PO. - Avoid crash when importing bad module Open ERP does not crash if you have buggy modules. It only crashes when you install or want to use it, and that's normal. Tryton made a system to not crash with bad modules, Open ERP has a system to not load unused modules. - Allow to override wizards Open ERP v5 not only allows to override wizard, but you can also change them through the web interface: server actions system, workflow editor, view editor. Much more flexible than developing everything. Moreover, since v5, Open ERP don't have a separate wizard system but simply uses objects in memory (osv_memory). - Store user passwords encrypted It's not as a standard of Open ERP but Open ERP has a module fir this, you just have to install - password send only once at login This is a design decision. Tryton choosed to be connection oriented, Open ERP choosed to be connection less oriented. (You can restart the server and it does not crash the client) - Support Decimal type Also in Open ERP. - Allow to customize locales Open ERP forces to use ISO standards for locales. I don't see this as an improvement. - Use odt file as template for reports (with relatorio) Tryton's main engine forces to use ODT and OpenOffice to generate reports. For speed improvement (on hundreds of pages), Open ERP produces PDF without using Open Office by default. But Open ERP also support to use ODT. Open ERP doesn't use Relatorio but has a Report Designer as an OpenOffice plugin (much more better for end-users) - Display only Tryton databases for login Open ERP choosed to display all DB of the current postgresql user. This allows to not request the DB just for listing them. - Handle BigInteger Also in Open ERP. - Improve security for SQL injection Open ERP has also lots of improvements against SQL injection. - Handle failures in the task execution of the scheduler by sending a request to the owner of the task Open ERP does not support this. But tasks linked to the scheduler uses try:except to trigger good error requests. - Disallow to modify data originating from xml files by default This is a design issue. I think it's better to be able to change views and menu, and being able to save this as a module. (later or in real time through the module_recorder module) - Manage caches for multi server instance Not in Open ERP. - Check for dynamic constraints (like required and domain) on records in write and create process Also in Open ERP, but managed in client side, to not impact too much speed. - Use psycopg2 instead of psycopg Work in progress in Open ERP v5. - Use SAX parser to allow parsing of big xml files Also in Open ERP v5. - Allow to use an SQL query as table for model Also in Open ERP v5. Most of report uses this system. - Allow to use many "Modified Preorder Tree Traversal" on the same model I don't consider this as an improvement. Open ERP does not support this but has a simpler definition of Preorder Tree Traversal fields. Who needs this ? So we prefered speed improvement and easy to design than supporting multiple PTT on one object. - Allow to have char without size constraint On Open ERP, you define this with a text field in the server side and a char field on the client side. - Add limit on caches Open ERP has limits on caches. - Add WebDAV protocol to browse the attachments and the reports We had this WebDAV protocol in our initial release of document management. We decided to switch to FTP because the library in Python (Tryton is using) does not work at all with lots of documents (>1000). So, in Open ERP we reimplemented The DMS of Open ERP is much more advanced than the one of tryton. Not comparable at all. - Use internal locale formatting to be thread safe Work in progress in OpenERP v5. - Add a unittest framwork In Open ERP, unittest are integrated in demo and normal data, which is a better approach in my sense for balckbox testing. This is the assert system. We also have external scripts for others tests. - Disallow to delete a record linked to a running workflow This is a design decision. I don't consider this as an improvement. People like to be able to delete draft invoices or quotations. The deletion is well managed in Open ERP's workflows. - Make cache thread safe I have no idea about what is this improvement ? - Provide time independent test for concurrency checks Open ERP also have separate scripts for this. - Add security test for remote callable functions Open ERP also has security tests for remote callable functions. - Allow to order on fields function Supported in Open ERP v5 too. Open ERP use a better approach by supporting storing the fields.function in the database. - Use a more pythonic way of inheritance The Open ERP inheritance is quite different from the Python one, in his result. -------------------- m2f -------------------- -- http://www.openerp.com/forum/viewtopic.php?p=27568#27568 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
