From 8dfad9670e0252cfa2a03b3cb3c67dc8f72c0dde Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 7 Jun 2019 21:03:31 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index f3d4003f..6f22c1d0 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -120,9 +120,10 @@ TODO: INVESTIGATE - Dark mode / theming (dark with a half moon icon) - If it can be done with a half hour of work and doesn't affect anything support wise or maintainance wise then yes - Also see how to allow theming maybe or colour choices? Nah, dark mode is the most useful; I should decide the colours and stick with them it's part of our image -TODO: Grid / LIST VIEW = I know customers will want to control what shows in the list views (grid equivalent in v8). +TODO: INVESTIGATE - Grid / LIST VIEW COLUMNS SELECTABLE?? I know customers will want to control what shows in the list views (grid equivalent in v8). - 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 + - they will also want to set the order, maybe that's not going to be supported though - Need to think this over, do I have defined columns or is the list just for display to select the record in which case can it just be one column with user selected values showing?? - Security and business rules may affect this as well, for some users they have rights to some of the record but not all of it, i.e. subcontractor so we do need granular field level control over what goes out from the server and at the client expectations - Maybe list objects also return a list of fields the current user will expect to see so the list can be pre-set up with the columns at the client *then* the data fetched to populate the list