ayanova/devdocs/todo.txt

@@ -4,6 +4,7 @@
 
 
 todo: keycodes mirror common menu options like save close back etc
+	https://github.com/jaywcjlove/hotkeys/issues/115
 
 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
@@ -14,7 +15,7 @@ todo: can I support keycodes for saving in AyaNova and other shit that are the s
 
 
 
-
+todo: how to and search for memory leaks, excercise all forms and make sure now
 
 @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
 @@@@@@@@@@@@@@@ ROADMAP STAGE 6 - "REALITY" All in on porting over all the real objects from v7 
@@ -22,9 +23,9 @@ todo: can I support keycodes for saving in AyaNova and other shit that are the s
 
 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
 	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
+	(If an object would normally be accessible via client ui from another object that won't be ported until later then can make up a set of links on a dashboard page
+	to use for temp testing purposes until can fully implement)
 	
 
 
@@ -50,7 +51,7 @@ EACH OBJECT DEV CYCLE:
 
 	
 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
+	{LIST OF OBJECTS IN ORDER OF IMPLEMENTATION HERE}