Totaly objectively, All Fabien said is true but it is important to keep in mind few things about Tryton :
It's a rewrite so it is like a new birth. The Tryton project is more "open" than the openerp project, by this I mean that, the give more transparency to their development process. By giving acces to development discussions, and documentin changes in their code. They provide UPDATED documentation on how the framework works, and how to work wtih this framework, even through python's doc string. This is why I keep an eye on Tryton, and may be will contribute to the project. Actually Openerp's lack of up to date developper documentation, is the main problem for me. Every things are keep in the obcurity , dont know why ... This is totaly the opposite I expect from a framework. I hope this will change shortly, Openerp has lot of ready to use use modules, this is really interesting, but I still consider developping for Tryton because this project is more "readeable". Sure it is not fully usable yet, but if they keep contribution easy and good openess I guess contributors will come. Any way Thank's to the OpenERP team for the stuff they provide , and I hope they will ear my wishes : Please Update Developper's documentation, keep comment in code, and publish the changes you do in the framework. I read Fabien's blog post about documentation, I know he is looking for a good solution, but things have to move faster on this matter. Regards -------------------- m2f -------------------- -- http://www.openerp.com/forum/viewtopic.php?p=27730#27730 -------------------- m2f -------------------- _______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman/listinfo/tinyerp-users
