ayanova/devdocs/todo.txt

@@ -49,6 +49,23 @@ PROFILE VIEWING ROUTES
 http://localhost:7575/profiler/results-index
 http://localhost:7575/profiler/results-list
 
+
+todo: Profiling
+	Go over profiling and unit tests, see where there are obvious issues and bottlenecks now that I have the data
+	Block licensing related queries and view from profile
+	Metrics view: 
+		find a way to get the raw data so it can be fed back to the metrics route and limited to what I want to allow to show
+		maybe store just the critical or slowest routes with some db info into the database on schedule from the in memory cache?	
+	Full profiling view:
+		but find a way to allow / enable the full suite of profile as it is for just technical support purposes, i.e. a hidden switch or something?
+		some kind of limitation to the route so not anyone can just open it (source IP or domain?, i.e. tech support)
+	Our metrics not route related
+		Can add our own metrics back into the profiling now that it's there with miniprofiler so if anything I want to track then can do that
+			rockfish license fetching timer?
+
+	
+
+
 todo: remove search option from metrics / logs etc as it implies you can search those things and you can't
 
 todo: document how to use chart as it's not all obvious
@@ -422,7 +439,7 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
         - Every type of entry field fully translated properly including numeric, date, time, tags etc			
 			- Client: initialize after login sets translation formats for everything.
 				- Best to do this useroptions stuff after a form is in place that I can play with at the client and experiment to see what is possible
-				- How much flexibility do we have to set things like numeric / currency input / display format?		
+				- How much flexibility do I have to set things like numeric / currency input / display format?		
 				- First it gets useroptions to know what to override or not, then sets defaults based on browser or override settings in central client area for all display/parsing etc
 		- All numeric and date displays and input in translation format
 		- numeric inputs need to be set as such so that the number keyboard appears
@@ -475,7 +492,7 @@ FIXES REQUIRED (WTF? Is this still valid stuff ?????????????????????????????????
 				- Override browser datetime with these settings instead (see below)
 					- One single date format string?  Or one for time, one for date and one for date/time? (see v7)
 						- Take from day.js (https://github.com/iamkun/dayjs/blob/master/docs/en/API-reference.md#list-of-all-available-formats)
-						- Do not allow anything other than numeric display, i.e. no January or Saturday so we avoid translation issues
+						- Do not allow anything other than numeric display, i.e. no January or Saturday so I avoid translation issues
 
 
 ......
@@ -581,7 +598,7 @@ ABOUT form - add the  user settings such as timezone offset, translation formatt
 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?
+	- Save button kind of is, do I 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
@@ -598,11 +615,11 @@ todo: Suggestion box feature
 @@@@@@@@@@@@@@@ ROADMAP STAGE 6 - INSTALLER, LICENSING, ROCKFISH SUPPORT FOR RAVEN
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 
-	Completely packaged and installable.  REady for users to install as a test as we iterate stage 7 below
+	Completely packaged and installable.  REady for users to install as a test as I iterate stage 7 below
 	All the stuff needed for someone to run it as a test without the real objects yet.
 	Some kind of expiring license so they can't just keep using it as fucked as it may be some might do that
-	we want short targetted testing only, not someone downloading and trying it out a month later, that's useless for us
-	This needs to be focused on what we need to get from people about testing
+	I want short targetted testing only, not someone downloading and trying it out a month later, that's useless for us
+	This needs to be focused on what I need to get from people about testing
 	BETA MODE Feedback form?
 		Sends errors, server log, suggestions etc, directly to rockfish?
 
@@ -667,8 +684,8 @@ todo: CASE 3780 what's going in the dashboard?
 
 
 todo: workorder UI layout stuff (TTM!!  Don't re-invent the wheel!)
-	There's been a lot of ideas about wo floating around and considered, but at the end of the day what we have works so maybe try to meld 
-	into what we have the new concepts and see what comes out.  Support a rich wo UI on big screens and scroll around UI on phone maybe.
+	There's been a lot of ideas about wo floating around and considered, but at the end of the day what I have works so maybe try to meld 
+	into what I have the new concepts and see what comes out.  Support a rich wo UI on big screens and scroll around UI on phone maybe.
 	some notes:
 		Workorder UI good ideas here: https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3475
 			Basically (based on RI) it boils down to don't make the user go up to the workorder item level when they can go sideways directly to an alternate child of woitem
@@ -761,7 +778,7 @@ Plan the order of criticality for plugins
 Assuming has passed all testing
 Plan pricing and sales strategy
 What to do with licenses for v7 people
-Do we need another payment processor?
+Do I need another payment processor?