ayanova/devdocs/todo.txt

@@ -214,6 +214,8 @@ CURRENTLY DOING: workorder front POC
 	- make minimal front end enough for POC wokorder->woitem->woitemscheduleduser collection (STATE?)
 		- test out, confirm can CRUD as planned independantly and all at once
 		- will need some dirty fields and viz fields likely added to models so go minimal route as possible to POC it
+	- NEED editable field at every level to test out the updating and partial updating process
+	- NEED state control right away to test that aspect 
 	- once pass this step then second pass at new features that affect models (not necessarily UI stuff just fields required etc)
 		shouldn't be too much as already did that when recently fleshed out models but no doubt missed much
 	- then full in front end and flow out to back end as required, remove any backend that was a defunct evolutionary path so no cruft left around
@@ -248,7 +250,9 @@ todo: in UI the workorder state should show current state but be expandable to v
 	Status control, displays last status as a read only text field maybe decorated in an H3 tag or something, but when you click on it opens a form to append a new status
 		control handles the rights and roles and shit
 
-
+todo: remember, some users should not even have data sent from the server / scrubbed and not affect updating.
+	for example a user may not be able to see part costs so that should not even be sent over the wire
+	workorder will have to handle that as necessary adn expect sometimes data is not forthcoming
 
 todo: UI wo descendants data table exposure (old v7 wo tree nav pane ui)
 	people probably want them / it's an easy way to see certain things you can't see any other way

ayanova/src/components/work-order-items.vue

@@ -24,11 +24,17 @@
             This gives the user as much as possible at hand immediately to view and edit and the option of adding and selecting more items
             It also ensures a clean interface more like a piece of paper with only stuff added showing
 
-            So every level and collection is a control with 3 states:
+            So every level and collection including woitem and down is shown as a control with 4 states:
-                None entered: it's exposed as a clean and not too intrusive "Section title" control affordance with a title so "Scheduled users +" taking up very little vertical space (this is always visible)
+                Customized to not show at all or not allowed: is just not visible at all, doesn't render doesn't affect anything
+                None entered: it's exposed as a clean and not too intrusive "Section title" control affordance with a title so "Scheduled users +" taking up very little vertical space 
+                    but distinct enough and large enough to quickly find visually on the page (this is always visible)
                 1 entered: it's exposed as a edit form below the Title control (no grid)
                 More than 1 entered: it's exposed as a grid below the title control which is used to select a row and an edit form below the grid that is displayed ONLY when a row is selected in the grid
                     so if they just open the form and haven't picked a row yet then no edit form shows to save vertical space and be cleaner
+
+            Visually each section is separated by a distinctive title and whitespace around it, no lines or boxes or other ugly shit.  It should look as much as possible like a clean sheet of paper and be minimalist.
+            Roles and rights
+                some controls may have an alternative format for differing roles and rights users, so if it's a subcontractor then they may see an alternate view
                 
 
         e.g.