ayanova/devdocs/todo.txt

@@ -48,8 +48,29 @@ CURRENT TODOs
 
 
 
-TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION
-	
+*((((  NEXT GO OVER FEATURES AND IDENTIFY LIST RELATED AND SEE WHATS REQUIRED TO FULFIL AND DOCUMENT HERE BELOW ))))*
+
+TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION KEEPING IN MIND TTM
+	- WHAT is the actual purpose of the grid lists?
+
+		- Add new record of that type		
+		- Selection of record(s) FILTERED OR ALL for reporting or mass operations
+		- Feeding into reports that are highly customizable and can be used to view all data rather than fucking around with grid columns?		
+		- Mass operations
+			- in v7 could do a mass op on *all* records, but here that would mean downloading all the records into the client which could be very fucking slow or too big
+				- Reporting: in v7 could report against individually selected items or all				
+				- Plugins: in v7 plugins could be enacted against individually selected from list of items or all etc
+			- Maybe a good middle ground to allow for more flexibility with mass ops is to allow up to large but arbitrary number to prevent an *all* option, like 1000 or 5000 or something which should be enough for almost anything to be practically done in segments
+				- i.e. report on all workorders for year maybe is too large but if filter by month then can print each month separately
+			- CLIENT for selective ops only, for any feature that is going to commonly be required to use against *all* records it should be a defined route at the server and the server should handle it when client triggers
+		- Features requiring mass ops:
+			- 
+
+	- COLUMNS DISPLAYED
+		- Crtical columns are the name or equivalent that is unique as the primary item
+		- Other columns that are critical would be any that are stock and required
+		- Leaning toward static fixed column display that is sortable
+
 	- Should users be able to set columns or am I really going to force it to a preset?
 			- I had a customer today request the Description field from unit show in the workorder service grid, it doesn't do that
 			- Customers probably want the option of picking what fields show and what don't
@@ -61,8 +82,13 @@ TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION
 	- Main list hidden fields in edit form should not show in main grid either? 	
 		- overlaps with the user selectable stuff immediately above here
 		- Test with widget serial field as before
-	- Filtering 
+	- FILTERS
+		- ??A cool feature might be built in filters for common date things so no need to make a "this quarter" filter it would just be there as a selectable filter option
+			- Although it might just pollute the list when the user just wants some basic ones they deem important
+		- ??what if a filter also had a selectable default sort order so whenever you picked that filter it also set the sort to what was chosen, however user could still click on visible column headings to change sort?
+			- But then what about hidden fields set to sort that user is not aware of and fight with the header clicks they make?
 	- Sorting
+		- V7 can sort by up to 3 columns which makes it possible to do something like sort all customers together then by date or something
 	- STUB out any other main grid list options
 		- Put in the menu options will likely need even if not coded yet.
 		- go through cases find the new things that need to be on the menu and stub them out.