ayanova/devdocs/rando-todo.txt

@@ -33,4 +33,51 @@ todo: consider feature to set server to always use a pre-set browser locale sett
 	Scenario is user in another country but needs to login and work with central server?
 	server - wide 
 	User specific
-	YAGNI / TTM?
+	YAGNI / TTM?
+
+todo: REPORTING bits and pieces
+	- page breaks properly EXAMPLE NEEDED
+		this is the current CSS property, not the one jsreport was using: https://developer.mozilla.org/en-US/docs/Web/CSS/break-before		
+		There are many options including ones for columns and some to prevent page breaks splitting up blocks.
+
+			<div style="break-before: page;">
+				<h2>{{ Name }}</h2>
+				<div>Notes: <span class='example'>{{ Notes }}</span></div>
+			</div>
+		
+		old jsreport ref:	https://playground.jsreport.net/w/admin/dI2_fUqZ (for example this sample report shows   <div style="page-break-before: always;"></div> which is interesting)	
+	- print properties in css ref: https://www.tutorialspoint.com/css/css_print_references.htm
+		@page https://developer.mozilla.org/en-US/docs/Web/CSS/@page
+
+	- custom extra javascript functions EXAMPLE NEEDED
+		actually there's nothing really to this, just define function outside of the prepare block and it's there to use
+
+	- Mailing labels
+		if a hassle can skip, it's an unusual thing probably today and users could export to open office then print or whathaveyou
+
+	- Alternate paper sizes A4, Letter etc
+		https://developer.mozilla.org/en-US/docs/Web/CSS/@page/size
+		Also note that can pass on pdf render options to the puppeteer pdf rendering code which include 
+			http://www.puppeteersharp.com/api/PuppeteerSharp.PdfOptions.html
+
+	- Helper for datalist filter human readable
+		also useful for the UI of the datalist as well
+
+	- readable errors:
+		https://stackoverflow.com/questions/56959242/how-do-i-get-readable-browser-page-errors-out-of-puppeteer-sharp
+
+
+
+
+todo: ON HOLD TIL LATER Lagging typing in name field on customize form for data grid filter 
+	Giving up on this for now, but noticed the following:
+		No exceptions or errors just regular processing
+		On a lighter grid with less columns it's much faster so the column count contributes majorly
+		If I remove the v-model binding from the name control it types fast so it's the recalc going on from the model change
+	TO TRY LATER: 
+		More computed property usage (if any now) and less methods because functions run on every change wherease computed are not if not necessary
+			methods are going to be slower than computed properties theoretically
+			Pick through and replace function calls in UI with computed properties bit by bit and see what happens
+		Several collections bound to array in data object, is that array changing on typing text?  Triggering something?
+			Should it be bound to a computed getter instead of directly to the data object?
+			

ayanova/devdocs/todo.txt

@@ -1,15 +1,9 @@
-
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 @@@@@@@@@@@@@ ROADMAP STAGE 5 - FINALIZE ALL NON BIZ OBJECT SPECIFIC FUNCTIONALITY
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 
-todo: Much of this stage below needs TRIAGING, do that first.
-	Any real (corebizobject) shit goes to stage 7
-
-
-
-
 
+todo: keycodes mirror common menu options like save close back etc
 
 todo: can I support keycodes for saving in AyaNova and other shit that are the same as in v7 or as much as possible, i.e. ctrl-s to save (or whatever was defined)
 	watch out the report editor uses a bunch of hotkeys pre-defined
@@ -22,76 +16,59 @@ todo: can I support keycodes for saving in AyaNova and other shit that are the s
 
 
 
-todo: ON HOLD TIL LATER Lagging typing in name field on customize form for data grid filter 
-	Giving up on this for now, but noticed the following:
-		No exceptions or errors just regular processing
-		On a lighter grid with less columns it's much faster so the column count contributes majorly
-		If I remove the v-model binding from the name control it types fast so it's the recalc going on from the model change
-	TO TRY LATER: 
-		More computed property usage (if any now) and less methods because functions run on every change wherease computed are not if not necessary
-			methods are going to be slower than computed properties theoretically
-			Pick through and replace function calls in UI with computed properties bit by bit and see what happens
-		Several collections bound to array in data object, is that array changing on typing text?  Triggering something?
-			Should it be bound to a computed getter instead of directly to the data object?
-			
-
-
-
-
-
-
-
-REPORTING bits and pieces
-	- page breaks properly EXAMPLE NEEDED
-		this is the current CSS property, not the one jsreport was using: https://developer.mozilla.org/en-US/docs/Web/CSS/break-before		
-		There are many options including ones for columns and some to prevent page breaks splitting up blocks.
-
-			<div style="break-before: page;">
-				<h2>{{ Name }}</h2>
-				<div>Notes: <span class='example'>{{ Notes }}</span></div>
-			</div>
-		
-		old jsreport ref:	https://playground.jsreport.net/w/admin/dI2_fUqZ (for example this sample report shows   <div style="page-break-before: always;"></div> which is interesting)	
-	- print properties in css ref: https://www.tutorialspoint.com/css/css_print_references.htm
-		@page https://developer.mozilla.org/en-US/docs/Web/CSS/@page
-
-	- custom extra javascript functions EXAMPLE NEEDED
-		actually there's nothing really to this, just define function outside of the prepare block and it's there to use
-
-	- Mailing labels
-		if a hassle can skip, it's an unusual thing probably today and users could export to open office then print or whathaveyou
-
-	- Alternate paper sizes A4, Letter etc
-		https://developer.mozilla.org/en-US/docs/Web/CSS/@page/size
-		Also note that can pass on pdf render options to the puppeteer pdf rendering code which include 
-			http://www.puppeteersharp.com/api/PuppeteerSharp.PdfOptions.html
-
-	- Helper for datalist filter human readable
-		also useful for the UI of the datalist as well
-
-	- readable errors:
-		https://stackoverflow.com/questions/56959242/how-do-i-get-readable-browser-page-errors-out-of-puppeteer-sharp
 
 
 
 
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
-@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - "REALITY"
+@@@@@@@@@@@@@@@ ROADMAP STAGE 6 - "REALITY" All in on porting over all the real objects from v7 
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
-All in on porting over all the real objects from v7 
 
-todo: First of all triage the features to port over in the sanest order so not stubbing too much stuff
+FIRST: Determine order to implement objects and write in below, try to list as thoroughly as possible by going over existing features and proposed new ones
-	Try to get scheduleable stuff early because schedule form will take some time
+	List should be objects in order of implementation, if new then flag with an asterisk * indicating it's a new feature that doesn't need import code
+
+	
+	Lone wolf objects with the least dependencies (that are staying) to the most connected ones with the biggest graph (workorder, schedule ui) in that order
 	
-todo: Schedule form
-	- new gold standard is Google schedule so emulate that amap
-	- This one is big but requires the data to be there so as soon as implement enough things that are scheduleable then do this
-	- printing / reporting 
 
-todo: Notifications
+
-	Many are on hold until there are real objects to code against, now is the time to code them as the objects are added
+EACH OBJECT DEV CYCLE:
+	BACK
+		AyaType and associated code
+		Model and Database table(s) and associated code		
+		Translation keys
+		Notification related if any
+		Routes and associated code
+	FRONT
+		AyaType / rights
+		front route
+		Edit form 
+		List form
+		Add to smoke test	
+		DOCS (at back but with front links, maybe not fleshed out just placeholder ok for now)
+	IMPORT
+		imports and flows through to new front end viewable and searchable and printable etc
+	REPORTING
+		Reportable
+	
+
+	
+OBJECT ORDER
+	Ideally in the order of who has the least number of connections to other objects, i.e. lone wolf objects to the most connected objects
+
+
+
+
+
+POST "REALITY" OR IN PARALLEL:
+
+todo: Schedule form	
+	- This one is big but requires the data to be there so as soon as implement enough things that are scheduleable then do this
+	- printing / reporting schedule?  Do-able? 
+
 
 todo: can beta test at this point
+	See below, specific ideas about public beta test (User accounts not seperate installs maybe)
 	post installer, enlist trial users get feedback, don't get too down when they shit all over it as they will undoubtedly :)
 	remember, it's for the new customers primarily, new customers = new $$
 
@@ -168,7 +145,8 @@ todo: workorder UI layout stuff (TTM!!  Don't re-invent the wheel!)
 
 
 
-todo: Documentation
+todo: Documentation POST "REALITY"
+	will already have placeholders from above
 	Need to think this through carefully
 	Need to get the critical bits in for onboarding and importing so people can get going
 	Most important stuff is anything non-obvious