From 1675c495e55a33589427ab7bb9b66964d5b6cade Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 6 Aug 2020 23:35:59 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 33 +++++---------------------------- 1 file changed, 5 insertions(+), 28 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 1bd587f6..9306f5fd 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -3,28 +3,7 @@ PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route changes etc then back here in order lowest level first as affects the most stuff exponentially so best to do it early =-=-=-=- -javascript: -todo: open-object-handler.js deal with some utility types: - - //TODO: LIST VIEW - //TODO: Items that are able to be opened from the adm-history form - //need to decide to support them and if not then need to modify the message below - //to be localized and simply say "Can't open this object type" or something along those lines - //TODO: also an alternative might be to have a CanOpenObject method in open-object-handler that is consulted by data-table control before it builds links - -todo: NOW THAT FORM IS THERE MOSTLY, CLEAN UP CODE FOR RE-USE in many other forms - - Look for things to componentize - - Can I componentize the whole form itself so that I have all the basic requirements built in and can just customize certain things for each object type? - - Look for things that are not specific to the widget edit form but can be abstracted away for other forms - - Don't need to replicate common code so put it somewhere else - - Are any of the controls better as a component and self contained to save the size of the form code and complexity? - - What I mean is, for example, a text entry field could be standardized then re-used as a component if it's props and settings take up so much space etc - - formstate shit is also menu shit really so can they be combined somehow, like present two sets of menu options one read only and one fully read-write? - - some forms will have special needs but could handle them outside of the regular boilerplate shit? - -todo: Investigate Workorder structure and datagrid see case https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3768 - Likely that workorder grids inside will not be full blown custom datagrid I wrote but just a vanilla v-data-table control since there is likely no need for the full customization shit todo: Document in user manual the Widget form as an example with instruction on how to use the various controls etc - Can use widget for screenshots and examples of control types, but don't word with expectation it will remain because it won't @@ -42,15 +21,10 @@ todo: Bizobjectnamefetcherdirect at server make sure *all* types are coded even if they aren't valid for a name (code with a blank - character) -todo: **DEFERRED - Joyce is looking something up about this** Login form customizable for logo etc? +todo: AyaNova customer branding to login form / upload logos etc **UPDATED, SEE CASES, WILL IMPLEMENT MIGHT AS WELL DO IT NOW - https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3592 - https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/1849 - - possibly other cases? - - Still on the fence with this one, I mean why should we give up our branding, on the other hand if people MUST have it maybe a co-logo - Why exactly DO people HAVE to have it? So they can pretend they made it? - if they think their customers would be confused maybe all it needs is the company name predominently on it? - Seems weird to give up our branding and logo in the only place it's actually displayed beyond our marketing materials - Give this a serious thought because it seems like we might be being shitty to ourselves if we support this + - possibly other cases, check and also check the spec docs and notes, I think I chose a location / method to upload these files already? ========================================================================================================= @@ -292,6 +266,9 @@ todo: can beta test at this point +WORKORDER UI +todo: Investigate Workorder structure and datagrid see case https://rockfish.ayanova.com/default.htm#!/rfcaseEdit/3768 + Likely that workorder grids inside will not be full blown custom datagrid I wrote but just a vanilla v-data-table control since there is likely no need for the full customization shit todo: workorder UI layout stuff (TTM!! Don't re-invent the wheel!) There's been a lot of ideas about wo floating around and considered, but at the end of the day what I have works so maybe try to meld into what I have the new concepts and see what comes out. Support a rich wo UI on big screens and scroll around UI on phone maybe.