Views refactoring

[fosterlynn]

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.

• create user, ?

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.)

• customer order

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.

[fosterlynn]

Mapping of proposed view based apps to model segregation. This is off the top of my head, not verified in the code, so consider it tentative!!

Agents

• agent

Users

• ?? still not sure where AgentUser goes, so this might need agent

Resource types and recipes

• recipe

Make stuff (and services)

• event, process, agent, resource, recipe, schedule, facet-value, location

Exchange stuff (and services)

• trade, event, agent, resource, facet-value, location

Inventory

• resource, recipe, agent

Customer orders (will need to separate out and call code in make stuff, exchange stuff)

• recipe, resource, agent

Distributions

• distribution, agent, event, process, resource, recipe

Accounting

• some admin setup
• agent, event, ?

[fosterlynn]

Also, I'll just offer some info on the other random apps that exist in the code base.

board: This was done for a local herbal network, which used it but may or may not keep going this coming summer. It has a bunch of hard-codings for them. It's feature is a trello-like board based on their exchange sequence. But very primitive UI for the trello-like board. It could be made more universal by adding exchange types into recipes and using that to drive it.

equipment: This was done for Sensorica, meant to run on a phone and support use of their 3D printer. Very specific to them and also tons of hard-codings. This one is probably not worth keeping around except for maybe some sample code. Or really probably not. It was never used by Sensorica (grrrrr, but we did learn a lot).

Neither one of these is worth doing any upgrading or anything else to.