From cf0267728396acd8cc380f3ac44bb226116f23c8 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 9 Jan 2020 20:27:56 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index bef542fd..802c7aba 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -137,6 +137,19 @@ TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION KEEPING IN MIND TTM - DISPLAY FORMAT TEMPLATES - Needs to be in place for the grid to work basically so it's a high priority now - Speccd in core-display-format-template-system.txt + + - SERVER SENDS LIST OF COLUMNS + - The server needs to tell the client which columns are coming back with the list and what types etc so the client can just adapt to any template setting + + - HYBRID BIMODAL: XS or LARGE (for now but consider maybe a medium down the road in planning) + - in XS mode + - the client sends "viewport=xs" to the client with the grid data request + - Client receives two field list back (id and display field), displays the single field + - in large mode + - the client sends no viewport= parameter as it's optional and understood to be full size + - the list comes back as an object with not only the actual columns but also a separate property listing the set of columns in order to be displayed (maybe even their data type) + - Client expects an arbitrary set of columns in an arbitrary order defined by server so doesn't have a pre-ordained set of things. + - HMMM... Maybe I only need a single list object that adapts to the data being sent back - DETERMINE AND IMPLEMENT INCREASED MAXIMUM ROW COUNT ALLOWED - Changes required at server and client (need more options at client for selection in drop down max rows thingie)