10-12-2016, 08:17 PM
I really don't want to modify that code much, just the basic functionality and enhancements.
I would prefer to discuss a generic way of doing Master-Detail modules.
The inventory modules are a mess, there is a lot of javascript code scattered around in different places, the detail view has a bunch of HTML hard coded, the inventory lines themselves are not modules, ....
I think we should define a way of creating dependent module relations. So that we can indicate somehow that one module is the master of some others, which fields you want to use to tie them together and which fields you want to see when viewing and editing the master. Also which types of aggregations you need to have calculated. Note that this is the better part of the maser-detail mapping.
I would stay away from the stock inventory modules and create a new, more modern and flexible way of doing this.
This is on our roadmap, but at a very far distance....
I would prefer to discuss a generic way of doing Master-Detail modules.
The inventory modules are a mess, there is a lot of javascript code scattered around in different places, the detail view has a bunch of HTML hard coded, the inventory lines themselves are not modules, ....
I think we should define a way of creating dependent module relations. So that we can indicate somehow that one module is the master of some others, which fields you want to use to tie them together and which fields you want to see when viewing and editing the master. Also which types of aggregations you need to have calculated. Note that this is the better part of the maser-detail mapping.
I would stay away from the stock inventory modules and create a new, more modern and flexible way of doing this.
This is on our roadmap, but at a very far distance....
Joe
TSolucio
TSolucio