ayanova/devdocs/todo.txt

@@ -7,33 +7,29 @@ Success is the ability to go from failure to failure without loss of enthusiasm
 
 NEXT TODOS:
 
-TODO: LOGIN navigate back to prior request when it triggers a login?
-	- Or would this cause a loop at times and fuck shit up?
 
-TODO: Trial mode client should offer alternative logins right on login page and fill in for user to try out
-	- So a list of user names and a short text of what that user is used for when testing
-	- User can select and it will prefill in the form
-	- Obvs when not trial mode then the client doesn't offer it
-TODO: Form dirty indicator on the form and easy to see, maybe the background tinges or something
-TODO: RIGHTS FOR LIST
-	- TODO LIST OBJECT RESEARCH / DECISION
-				- TODO: ?? DECISION server widget lists and other lists
-				- Either the list should show items with alternate icons to EDIT if they are read only or...
-				- Use a generic OPEN icon and link instead and user doesn't see status until they open it.				
-				- ReadFULL record but no change should show record read only
-					- To test use accounts:   ReadFullRecord = AuthorizationRoles.BizAdminLimited | AuthorizationRoles.InventoryLimited
-					- WidgetList should check if even possible to read any part of record, if not then no link to edit
-					- WidgetList should check if Own record possible and check the list object for owner ID (maybe all lists will need to provide owner ID's?)	
-TODO: Persist view on return
+TODO: VIEW PERSISTANCE / STATE 
+	- Persist view on return
 	- useful info here: https://vuejsdevelopers.com/2017/04/16/vue-js-browser-button-ux/
 	- there's another item like this below somewhere.
 	- Widget list, refresh page causes items per page to reset back to 5 from custom setting, it should cache that shit at least for a session anyway
 	- Although people probably would want this to be saved to survive sessions
 		- maybe it should save it per device locally only so that the customizations are local to the device so they can customize differently for different ui's?
 		- Or, maybe they always want to see 50 widgets no matter where but 10 clients??
+	- SCROLL POSITION !! - Very important, must return UI to exact scroll position on navigation backwards, not doing so causes a hellish UI to use.
+		- Seems to be a thing in teh vue router already:
+			- https://router.vuejs.org/guide/advanced/scroll-behavior.html
+		- Same position in window
+		- Same settings in any grids being shown and scrolled to same point in grids
+	- CODING: 
+		- Need two types of page state, one that survives a logout login session and the other that is cleared
+			- For example, a user may want to always show 30 items in one list but 5 in another so this should survive login
+			- On the other hand the scroll position should not survive a session and should be cleared
+				- We don't need to worry about this for the pages in theory as there is a built in method used in router to enable it which seems flakey but it's the way to do it
+			- Focus only on the type that survives a session for now, the rest as required
 
 
-TODO: NEW WIDGET 
+TODO: ADD NEW WIDGET 
 		- Code for new record to the server
 		- Need a path to making a new record
 		- ID 0 maybe
@@ -59,7 +55,10 @@ TODO: Grid / LIST VIEW = I know customers will want to control what shows in the
 	- I had a customer today request the Description field from unit show in the workorder service grid, it doesn't do that
 	- Customers probably want the option of picking what fields show and what don't
 	- Need to think this over, do I have defined columns or is the list just for display to select the record in which case can it just be one column with user selected values showing??
-
+	- Security and business rules may affect this as well, for some users they have rights to some of the record but not all of it, i.e. subcontractor so we do need granular field level control over what goes out from the server and at the client expectations
+	- Maybe list objects also return a list of fields the current user will expect to see so the list can be pre-set up with the columns at the client *then* the data fetched to populate the list
+	- Server should not send fields that are restricted or have them blocked out or something.
+TODO: Grid list view should be easier to open, the open button should not be at the far right but more of the whole entire element or a larger portion of it maybe?
 TODO: Outstanding case with vuetify bug in clear button when readonly, check if fixed and if it isn't might need a workaround
 
 TODO: code the user options with the currency symbol etc on the server and then update client to fetch them.  Use static values instad in locale.
@@ -188,11 +187,7 @@ Make all fields work according to specs below
 
 	- something I just forgot as I went to write it and got stuck reading older shit here
 
-	- SCROLL POSITION !! - Very important, must return UI to exact scroll position on navigation backwards, not doing so causes a hellish UI to use.
-		- Seems to be a thing in teh vue router already:
-			- https://router.vuejs.org/guide/advanced/scroll-behavior.html
-		- Same position in window
-		- Same settings in any grids being shown and scrolled to same point in grids
+
 	- AUTOMATED UI TESTING - I need to institute it now and make tests so I have a template to work off for all future tests 
 	
 
@@ -264,3 +259,16 @@ AUTOCOMPLETE
 	- Customer demo!!
 
 
+
+*********************************************************************************************************************************************************
+## TODO...MAYBE??
+
+This is stuff I thought of but is dubiously necessary for the initial release at least or could be polish added later:
+
+TODO: Form dirty indicator on the form and easy to see, maybe the background tinges or something
+	- Save button kind of is, do we need this?
+
+TODO: Trial mode client should offer alternative logins right on login page and fill in for user to try out
+	- So a list of user names and a short text of what that user is used for when testing
+	- User can select and it will prefill in the form
+	- Obvs when not trial mode then the client doesn't offer it