> For the navigation here is my proposal quite easy to implement:
> ==================
>
> We could make a link in every resource ("document") to his parent, the
> resource that create it. So it should contains "model" and "id".
IMHO a resource can have more than one parent (monthly invoice for all
packings of the month) and a parent can have many children.
it's a classical m2m situation
BTW - I like the process oriented approach of Cloves and a graphical
representation which shows all from beginning to end although it might be a
bit slower than "text" mode and might not fit on one screen (as already now in
the browser)
--
regards
Ferdinand Gassauer
ChriCar Beteiligungs- und Beratungs- GmbH
Official OpenERP Partner
_______________________________________________
Mailing list: https://launchpad.net/~openerp-expert-framework
Post to : [email protected]
Unsubscribe : https://launchpad.net/~openerp-expert-framework
More help : https://help.launchpad.net/ListHelp
