diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 58fe4d83..ffa254cd 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -133,6 +133,10 @@ TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION KEEPING IN MIND TTM - Make sure the server supports this - GRID TODO FOR SURE + - 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 + - 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) - Also docs for api need changing @@ -143,19 +147,19 @@ TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION KEEPING IN MIND TTM - Check on stackoverflow probably been asked recently in modern times - - SEARCH (need to be able to search from the grid for that type of object) - - Show the total quantity of records so it's clear the user is seeing a subset, i.e. "Showing 100 records of 30,124 (filtered)" or something to that effect. - - For efficiency this might need to be a fuzzy number gathered periodically at the server as part of a job and put on a route? - - Don't want to count them every time the list is fetched....or do I? Maybe it's pretty efficient in Postgres? - - Doesn't it already count them for paging purposes and even sends that value to the client already? - - Show current filter summary or text name of filter at top of filter - - going to need filter name and also a summarized fragment of text showing criteria for reporting so also could purpose that list to show current filter? - - Filter picklist will show name for the current filter and sb at top of filter right up front - - - - Needs to remember last settings (stored centrally) like filter used, number of rows etc - - When user opens up AyaNova it should always look the same in each area as last time they were there - + - SEARCH (need to be able to search from the grid for that type of object) + - Show the total quantity of records so it's clear the user is seeing a subset, i.e. "Showing 100 records of 30,124 (filtered)" or something to that effect. + - For efficiency this might need to be a fuzzy number gathered periodically at the server as part of a job and put on a route? + - Don't want to count them every time the list is fetched....or do I? Maybe it's pretty efficient in Postgres? + - Doesn't it already count them for paging purposes and even sends that value to the client already? + - Show current filter summary or text name of filter at top of filter + - going to need filter name and also a summarized fragment of text showing criteria for reporting so also could purpose that list to show current filter? + - Filter picklist will show name for the current filter and sb at top of filter right up front + - + - Needs to remember last settings (stored centrally) like filter used, number of rows etc + - When user opens up AyaNova it should always look the same in each area as last time they were there +