-
Notifications
You must be signed in to change notification settings - Fork 59
drawing OpenERP UML diagrams with OOOR
OOOR makes it trivial to draw UML diagrams of OpenERP.
see an example here: http://www.akretion.com/en/blog/2010/01/18/introducing-ooor---openobject-on-rails-drivingrequesting-your-openerp-became-a-child-play/
It will print the UML for all the requested class and connex classes that are in the list of Ooor loaded models (all connex classes if you started Ooor with no restriction to custom set of models). It is optimized to reuse edges for reverse relations (ex o2n and m2o), just tweaking the edge label to explicit it. So it’s optimized for readability.
###API:
SomeOpenERPProxy.print_uml
ex: SaleOrder.print_uml
UML.print_uml([list_of_class ])
ex: UML.print_uml([SaleOrder, StockMove])
ooor_instance.print_uml
will print the UML of all classes loaded in first place the Ooor instance (not the classes loaded on the fly)
options:
:detailed – true by default, if a list of class is given; if true, it will print the class fields
:nodetail – use this option to skip the Object non relational fields list (a lot easier to read), ex: UML.print_uml([SaleOrder, StockMove], :nodetail)
:all – if specified all models in the Ooor instance are loaded and detailed is set to false unless the explicitly set to true
ex: SaleOrder.print_uml(:all, :detailed)
Warning, if you try to print the UML of a whole OpenERP install, dot might blow out in an out of memory error. In any case, you better use the power of OOOR to specify a set of classes incrementally until you reach your desired scope because the full scope wouldn’t be readable.