diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index e5b72768..080bb4c0 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -1,5 +1,5 @@ @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ -@@@@@@@@@@@@@@@ ROADMAP STAGE 4 - REPORTING / DASHBOARD / KPI +@@@@@@@@@@@@@@@ ROADMAP STAGE 4 - REPORTING / IMPORT / EXPORT / DASHBOARD / KPI @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ @@ -24,11 +24,11 @@ todo: check this issue for simplification: https://github.com/Cinchoo/ChoETL/iss todo: import - This is in it's own UI area I guess - Kind of a tricky one, do we really need it up front in initial release? - Should import it's own export I guess, but what would be the usage of that? - Import should really go through the api and just create the objects via api? - like v8Import does + This is important because it's how a lot of people will start with AyaNova from some other sources of data + Also, I don't like the idea of external application, everything should be in AyaNova already, not need to go to other app and create balkanization + I think it's ok to only support JSON import, there are a LOT of tools to do the conversion from csv to json or whatever + + todo: Lagging typing in name field on customize form for data grid filter @@ -36,6 +36,10 @@ todo: Lagging typing in name field on customize form for data grid filter Try stripping out other UI elements to see if it's just too much stuff Ask on https://github.com/vuetifyjs/vuetify/issues how to diagnose this lagging + + + + DASHBOARD / KPI / BIZ METRICS todo: DASHBOARD @@ -44,6 +48,7 @@ todo: DASHBOARD https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/2024 https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1974 - REPORTING / Printable, need to test render these same metrics graphs in reports + HOL UP...actually, this could be a v.next feature just to speed things along...or maybe never. Need to confirm this as I go along, probably need to replicate the graphs at the server end...shit could be images also but need to render somewhere I guess a wrapper over the graphs so they can be called directly during server render as well as from vuetify at client