ayanova/devdocs/todo.txt

@@ -158,6 +158,35 @@ TODO: ATTACHED DOCS?
 
 RETEST HERE ON ALL DEVICES
 
+=========================================================================================================
+
+TODO: INVESTIGATE / REDO THE TOP LEVEL SHELL - TIME TO MARKET / Is my shell layout fucked?
+	- wouldn't it just suck to have all those lists exposed at once in inventory?
+		- Opening that page once they are all there would trigger huge traffic to the server, better to confine things to their own area as much as possible
+	- TTM: isn't it faster to just turn the menu into a tree like v7 or put options in each one's screen? (Like inventory page just shows a bunch of other icons to open details like widgets)
+	- TTM: I'm concerned that the modular UI is a bit too ambitious, yes it makes sense for re-usability but exposing it to users so they can redo their UI seems crazy ambitious at this point
+		- People just want to work and simpler is always better, less to maintain
+	- How about the easiest simplest layout possible even if it's a bit uglier but keep it all clean and focused instead of too much shit on each form?
+	- Really, for maintainability it makes sense to have a very simple clean layout and not try to put a bunch of complex controls all over the fucking place!!
+	- I need to make money from this, not win prizes for design!
+	- Easier to show or not things for authorization purposes when they are each in their own navigation path as much as possible
+	- users are used to a certain thing with v7 why re-invent the wheel, just clean it up and modernize where necessary
+	- There are so many other things I need to focus on, this is just adding complexity in an area that might be a nightmare to maintain and troubleshoot.
+	- DON"T get too fancy with this, my instinct is to make it more complex all the time, but actually ugly and simple and effective is better than pretty but fucky to use
+		- Also, mobile really doesn't go well with fancy but more with clean and simple.
+	- Sounds like my minds made up, this issue is more about changing the SHELL UI
+	- IDEAS:
+		- old fashioned switchboard kind of thing, big buttons for each area sit in a row, on mobile they are vertical full width?
+			- ugly but effective		
+			- Alternative is a Tree control in menu instead, but that would likely be ugly in mobile(could investigate but it's not common probably for reason, look at material apps on phone see what they do)
+		- Don't worry about having to navigate too deep with too many clicks for the top level, yes some won't like it, but it's more important to focus usability and minimizing clicks in the actual path that day to day users take
+			- In other words make the most common tasks quick to do from the top level / HOME screen perhaps and *thats* where to focus on customization so users can surface what they want there as a LINK 
+			- Users can modify what shows by default in the home screen but not the fancy active widgets I had envisioned but instead different task based buttons / links so they can get to where they need to go quickly
+				- e.g. click on inventory, select the Widgets switchboard button, the widgetlist opens full screen to the right side, one of the menu options is "Add to home screen" with a favorite button
+					- They click on add to home screen and next time they are on home screen a new button / link is there to that item, autoamtically pre-grouped by area of functionality or maybe they can just order it how they see fit?
+		- I really like the idea of the widgetlist being full screen to the right rather than in a component sharing that space as it's pretty necessary 
+		to have a lot of columns display at times, yes it's a ui made up of a bunch of lists but that's really what people understand, it's appropriate to the application, 
+		no business software can simply hide everything and it doesn't have to suck or be ugly			
 
 
 TODO: Clean up TODO list, have only actionable, not completed items.
@@ -201,33 +230,6 @@ TODO: Server needs to do widget validation 666.66 dollar amount test rules not o
 
 TODO: INVESTIGATE - DO I need to institute a back button? (in APP MODE?? installed to "desktop" on device will I be able to easily navigate without back and forward buttons)
 
-TODO: INVESTIGATE / REDO THE TOP LEVEL SHELL - TIME TO MARKET / Is my shell layout fucked?
-	- wouldn't it just suck to have all those lists exposed at once in inventory?
-		- Opening that page once they are all there would trigger huge traffic to the server, better to confine things to their own area as much as possible
-	- TTM: isn't it faster to just turn the menu into a tree like v7 or put options in each one's screen? (Like inventory page just shows a bunch of other icons to open details like widgets)
-	- TTM: I'm concerned that the modular UI is a bit too ambitious, yes it makes sense for re-usability but exposing it to users so they can redo their UI seems crazy ambitious at this point
-		- People just want to work and simpler is always better, less to maintain
-	- How about the easiest simplest layout possible even if it's a bit uglier but keep it all clean and focused instead of too much shit on each form?
-	- Really, for maintainability it makes sense to have a very simple clean layout and not try to put a bunch of complex controls all over the fucking place!!
-	- I need to make money from this, not win prizes for design!
-	- Easier to show or not things for authorization purposes when they are each in their own navigation path as much as possible
-	- users are used to a certain thing with v7 why re-invent the wheel, just clean it up and modernize where necessary
-	- There are so many other things I need to focus on, this is just adding complexity in an area that might be a nightmare to maintain and troubleshoot.
-	- DON"T get too fancy with this, my instinct is to make it more complex all the time, but actually ugly and simple and effective is better than pretty but fucky to use
-		- Also, mobile really doesn't go well with fancy but more with clean and simple.
-	- Sounds like my minds made up, this issue is more about changing the SHELL UI
-	- IDEAS:
-		- old fashioned switchboard kind of thing, big buttons for each area sit in a row, on mobile they are vertical full width?
-			- ugly but effective		
-			- Alternative is a Tree control in menu instead, but that would likely be ugly in mobile(could investigate but it's not common probably for reason, look at material apps on phone see what they do)
-		- Don't worry about having to navigate too deep with too many clicks for the top level, yes some won't like it, but it's more important to focus usability and minimizing clicks in the actual path that day to day users take
-			- In other words make the most common tasks quick to do from the top level / HOME screen perhaps and *thats* where to focus on customization so users can surface what they want there as a LINK 
-			- Users can modify what shows by default in the home screen but not the fancy active widgets I had envisioned but instead different task based buttons / links so they can get to where they need to go quickly
-				- e.g. click on inventory, select the Widgets switchboard button, the widgetlist opens full screen to the right side, one of the menu options is "Add to home screen" with a favorite button
-					- They click on add to home screen and next time they are on home screen a new button / link is there to that item, autoamtically pre-grouped by area of functionality or maybe they can just order it how they see fit?
-		- I really like the idea of the widgetlist being full screen to the right rather than in a component sharing that space as it's pretty necessary 
-		to have a lot of columns display at times, yes it's a ui made up of a bunch of lists but that's really what people understand, it's appropriate to the application, 
-		no business software can simply hide everything and it doesn't have to suck or be ugly			
 
 
 
@@ -239,6 +241,13 @@ TODO: INVESTIGATE - Dark mode / theming (dark with a half moon icon)
 
 
 #locale stuff
+
+TODO: LOCALIZATION form
+	- Dedicated area for localization adjustments
+	- Going to be a central form for all localization not form by form
+	- Review the spec doc and the cases regarding this as there are some little touches that were requested and make sense related to search and replace and other things.
+
+
 TODO: //todo: timezone doesn't match, offer to fix it in initialize.js there needs to be a prompt and autofix
 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.
 Locale should fetch those settings the first time it sees they are not present so that they are refreshed upon use and are not stored in localstorage