ayanova/devdocs/todo.txt

@@ -46,6 +46,27 @@ SHELL / NAV / MENUS / LAYOUT
 
 TODO: FILTER AT CLIENT
 	
+	Sort / filter / select return columns all in one!
+		- This combined is a "view" or DataListView (fucking renaming again here we come! :)
+		- Each list has default template for fields to return user can add more but they are built in lesser (only a few fields)
+		- When user opens a data table they see for the first time the default view and sort order and filter (no filter, sort by id, a few key fields)
+		- they can make a new view which shows all the fields and they can set props on each one:
+			- Filter (with filter code)
+				- INVESTIGATE: Will users need to set more than one filter condition on each column, could they in v7?
+					- I'm counting a between filter as a single one
+			- Sort
+				- INVESTIGATE: Does it matter which order they sort in? (probably)
+			- Visible
+				- Checkbox if visible which means the server returns it or not, visible maybe not correct word here
+		- This way the user can customize the grid all in one savable setting
+		- Grid defaults to last "View" that was in use
+		- Also has MINI options or is that a different UI?
+			- Maybe it *is* different because selects are a kind of unique situation with thier own requirements.
+				- Can default but also would be hellish if it's customizable user by user since there is probably a company standard for selecting parts for example
+				- Maybe the "Default" can be set by an admin and users can either select default or go off the books to their own custom
+		- Reports are a special circumstance, a report really would go with a specfic filter wouldn't it? INVESTIGATE THAT
+			- View filter set with report?  Report needs all fields sometimes but view may not have so what happens then?"		
+
 		
 	- PickList of filters for dataListKey (DO I have a server route for that?)
 	- ListOptions editor