ayanova/devdocs/todo.txt

@@ -110,17 +110,21 @@ TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION KEEPING IN MIND TTM
 		- Maybe make all stubbed things an alt colour so can tell at a glance what is outstanding.
 		- Reporting, list mass ops, go through cases look for stuff that will be required
 	
-	- Some stuff that might not be relevant from earlier (duplicated at server todo project)
+
-		- TODO: Two kinds of mass fetch records in RAVEN
+	- LIST TYPES USABILITY: Two kinds of mass fetch records in RAVEN
 		- 1) Reporting records
-				- Need to filter, sort and will probably pull in many different tables so would be a set of dedicated objects for that purpose at server 
+			- Need to filter, sort and will probably pull in many different tables so would be a set of dedicated REPORTING objects for that purpose at server 
+				- Reporting objects have responsibility for showing fields available, filter etc.  Maybe the filter and report are saved together and just duped for other filter / sorts?
+					- Only if the report is lightweight enoubh
 			- Not using name display format as it's a reporting responsibility how the raw data is displayed at that point
-			- 2) Selection records
+		- 2) Selection records (ALL THE MAIN GRIDS ARE REALLY THIS IN RAVEN AND SHOULD ONLY THINK OF IT THIS WAY IN PLANNING SO DON"T GET IN THE WEEDS WITH COLUMN SELECTION ETC)
+			- In v7 the grids did double duty but a huge waste of bandwidth to send all that data if they merely want to find Bob's Lobsters customer to open it for example
 			- USED IN 
 				- In forms in pick lists for selection
 				- In main grids also for selection and viewing and triggering reporting (but reporting uses different lists to feed to report generator)
 			- Need to filter sort and search
 			- Uses templated name display format
+				- TEMPLATES are going to be a big thing
 				- Server needs to take into account display format
 		- ACTION required: 
 			- Make sure the server supports this