@Oscar_Agreda, Hello, I do no recommend you loose time with Dia UML, this is not a mature stuff, no integrator use it for real, it's just a proof of concept so far (you are however welcome to help turning it a suitable option). No, it will generate only the basic relational model at best, then you would need to complete the code with advanced hand coded functions and you will loose the "injectability" of your UML generation forever.
Now, if you want to easily draw UML diagrams of OpenERP, you can take a look at the new OOOR UML features, I documented them in that introduction post that will hopefully end up in the OpenERP planet blog: http://www.akretion.com/en/blog/2010/01/18/introducing-ooor---openobject-on-rails-drivingrequesting-your-openerp-became-a-child-play/ However this is generated UML (afterwards), not UML driving the code. My experience is that graphic tools to generate code are a dead end. They are extremely expensive to develop/maintain over the time. Only large organizations use such tools eventually and even with that, at the end they always show huge limits compared to coding. My experience is that you better invest in building an efficient coding framework with declarative (eg easy to learn) code style rather than such GUI tools that are more demagogic than anything else. Take Neogia (an Offbiz open source ERP derivative), well they had such an UML generator, and a much more powerful one than the current childish Dia for OpenERP. Specifically, you generate the realtions with their UML tool and then inherit the generated objects to add hand coded behavior to it, smart. Well, they used Poseidon UML freeware at the beginning. Then since such tools are expensive to build/maintain, Poseidon UML terminated their free version, then Neogia got caught. Then they had to invest time/money to migrate to Nebteans UML that will probably end the same way: like unmaintained for free and I'm not even sure they ever made that migration. At the end of the story, they invested lot's of time/money in non sustainable tooling instead of investing building an efficient framework. In Neogia, I would say that coding things manually indeed take like 3/4 times more than in OpenERP, so GUI tools are very much required, but they aren't there anymore... Well you get the picture. I've seen the same vicious circle develops in large companies too, that's why I claim: hell at some point one should understand what is done, so at some point coding is required: it's way more sustainable investing in a decent coding framework rather than tooling, even more at the expense of the framework. ------------------------ Raphaël Valyi CEO and OpenERP consultant at http://www.akretion.com -------------------- m2f -------------------- -- http://www.openobject.com/forum/viewtopic.php?p=49832#49832 -------------------- m2f --------------------
_______________________________________________ Tinyerp-users mailing list http://tiny.be/mailman2/listinfo/tinyerp-users
