ayanova/devdocs/todo.txt

@@ -46,6 +46,43 @@ CURRENT TODOs
 
 TODO: FILTER AT CLIENT
 
+ListViewEditor
+	- Needs to know what formsettings key is in use to check with PUT ON ROUTE
+	- Needs to know which DataList key to work with PUT ON ROUTE
+
+DataTAble form inits listview as follows:
+	- Checks if there is a current active unsaved listview in the formsettings for that form and uses it if found
+	- If no active unsaved listview it then checks for an ID of a listview in formsettings last used and fetches and uses that if found
+	- If no current unsaved listview nor an ID then it just leaves that blank and let's server use default listview
+
+If user selects to edit listview then ListViewEditor inits as follows:
+	- Checks if there is a current active unsaved listview in the formsettings for that form and uses it if found
+	- If no active unsaved listview it then checks for an ID of a listview in formsettings last used and fetches and uses that if found
+		- Also sets in selection list of listviews (or is that in thsi form)
+	- If no current unsaved listview nor an ID then it fetchs from the server the default listview and uses that in the form
+
+If user leaves listview form without saving:
+	- If any changes were made then ListViewEditor persists that listview to the store under the formsettings specified so that form can pick it up
+	- If no changes were made then nothing is persisted
+
+If user saves view from ListViewEditor
+	- Overwrites with prompt if they save to same view
+
+
+User opens datatable is presented with default listview arrangement
+Until user opens listview editor the datatable uses the default and doesn't persist a listview
+If user opens a ListView editor without any local customizations then it fetches off the server and presents as the default for that DataListKey
+If Client makes any changes to a listview they are persisted as a formsetting for that datatable that survive a restart
+When datatable form is opened it checks if a persisted formsetting of listview, if found sends that with the request for the list, otherwise listview property is empty
+If user selects a listview from the server for the datatable as long as they don't edit it that listview's ID is stored instead in the formsetting.
+The moment they edit a listview it's stored in full in local formsetting as the current active.
+
+Client stores the active listview into the persisted formsettings if there are *any* customizations done
+
+Filter UI
+	- Works with a passed in listview array somehow (from STORE I guess, current list view kind of thing?)
+
+	
 JSON DataListView format:
 ONE string of json, not separate
 Contains all columns that are relevant each as an object with various props desired to be returned in order
@@ -98,10 +135,7 @@ TAGS - At server if equality compare value is an array of strings then it's assu
 
 	Sort / filter / select return columns all in one!
 		- This combined is a "view" or DataListView (fucking renaming again here we come! :)
-		- Each list has 2 default templates for fields to return etc, a table view and a picklist view
+		
-		- Server dataList can accept either Default=true or sort filter json
-			- Mini format or table format default
-			- Or is default when there is no sort/filter/columns to show?
 		- When user opens a data table they see for the first time the default table 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)