ayanova/devdocs/todo.txt

@@ -50,11 +50,8 @@ SHELL / NAV / MENUS / LAYOUT
 
 TODO: GRIDS
 	- MAKE GRID AS GENERIC VUE COMPONENT
-		- Make a second main Widget list form accessible from the main ui just below the existing one to host and develop the new grid list (want to keep the original for comparison and to steal code from that already works)
-		- Make the grid itself as a generic component that handles the most essential parts common to all forms
-		- This way can plunk it in different list forms and then wrap it with what is unique to that form and type etc
-		- This will be helpful also down the road for reporting stuff when that comes up as a source of copy-pasta
-		- USE MOCK column definition at the server end for now so can do client dev right up to functioning grid *then* go back and do the server template and column definition stuff for real
+		- See gz-data-table.vue notes in component comments for it's own todo's
+
 		- MUST HANDLE HIDDEN FIELDS AND NOT DISPLAY (this is also a server issue)
 		- Grid does *NOT* have sort indicators or controls, that's behind the grid in the filter UI, this is necessary for reasons I forget 
 		- Max 100 rows in grid at a time with paging

ayanova/src/components/gz-data-table.vue

@@ -1,5 +1,6 @@
 <template>
   <v-data-table
+    caption="My Caption here"
     :headers="headers"
     :items="records"
     :options.sync="options"
@@ -73,12 +74,16 @@ What this grid needs to do:
 
 
 TODO:
-    - At server widgetlist route:
+    - Modify server widgetlist route:
         - Modify route to accept vp paramenter for small viewport 
         - Add mock column data and include it in the response for grid queries
         - modify server to return alternate list of just names and id's if vp paramenter is present and xs (may be other values in future so check for xs specifically)
             - this route could actually be just a defined c# object since it's always going to be one column and one id like namevalue list
             - full width all columns though would be different kettle of fish entirely so this is a good time to experiment and figure it out
+        - not sure if right time but also need to modify server return to hide hidden columns which we have working code for already for widgets to hide them so yay?
+            - Also custom fields, or is that a template issue?
+
+    - Start coding grid here with cue component parameters and handlers first and work down into detailed items once they are all in place between parent and here
 
 */
 export default {