This is to discuss what might make sense beyond the models split, and to see if this validates or invalidates the proposed models split here #1 (comment).
@escanda I think has been starting to think about this.
Here is my first attempt to think about NRP (not including OCP work app) splits based on views (and templates would follow with the views). This was done by looking around the app, not looking at the code. There will be tons of views that will need to follow on, like all the ajaxy calls, etc.
Agents
- config of types, although that is a lot in admin
- organization, create agent, maintain associations, all agents
- network diagram, association graph
Users (not sure if this should be separated out, but it seems like there will be different workflows for creating users, including the membership OCP piece, the "invite" option, etc. So this is the base minimum one. And I also don't know how the account app discussion affects this.
Resource types and recipes
- config of units, facets. ...
- resource types, resource type lists
- recipes - create, view, change
Make stuff (and services)
- process patterns
- planning - with recipe, without recipe, order page
- demand page (I think)
- process logging, non-production logging
- all work and my work pages
- [edit: moved these here from resource] event history, incoming value flow (I think)
Exchange stuff (and services)
- exchange types
- exchanges, exchange list
- supply page
Inventory (I made this separate, because it is integral to both making stuff and exchanging stuff. I think people may want exchange without producing, but not vice versa. And both will need the Inventory app. At the same time, Inventory could be a basis for resource access app later, so could be wanted as something separate.)
- inventory, resource,
- locations
Customer orders (I made this separate because a customer order automatically creates a sale exchange and makes a work plan to create the ordered items if not onhand.)
Distributions
- value equations
- distributions, sandbox
- payouts (?)
Accounting (there could be all the standard accounting reports here if people want them)
- cash report
- contribution reports (for lack of a better place at the moment)
Note that in most of these, there are currently buttons or links that will require other apps to work, and sometimes pieces of logic - I'm thinking we can add "if x app exists, show button" kind of things in the templates, and if's in the logic.
This is to discuss what might make sense beyond the models split, and to see if this validates or invalidates the proposed models split here #1 (comment).
@escanda I think has been starting to think about this.
Here is my first attempt to think about NRP (not including OCP work app) splits based on views (and templates would follow with the views). This was done by looking around the app, not looking at the code. There will be tons of views that will need to follow on, like all the ajaxy calls, etc.
Agents
Users (not sure if this should be separated out, but it seems like there will be different workflows for creating users, including the membership OCP piece, the "invite" option, etc. So this is the base minimum one. And I also don't know how the account app discussion affects this.
Resource types and recipes
Make stuff (and services)
Exchange stuff (and services)
Inventory (I made this separate, because it is integral to both making stuff and exchanging stuff. I think people may want exchange without producing, but not vice versa. And both will need the Inventory app. At the same time, Inventory could be a basis for resource access app later, so could be wanted as something separate.)
Customer orders (I made this separate because a customer order automatically creates a sale exchange and makes a work plan to create the ordered items if not onhand.)
Distributions
Accounting (there could be all the standard accounting reports here if people want them)
Note that in most of these, there are currently buttons or links that will require other apps to work, and sometimes pieces of logic - I'm thinking we can add "if x app exists, show button" kind of things in the templates, and if's in the logic.