From 1057e2a2b5904706e485abf6952dec417d8d71fe Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Sat, 2 May 2020 00:09:04 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 35abc0a5..5a3d24e5 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -72,6 +72,7 @@ BIZ OBJECT STUBBING FOR EXPORT TESTING Modify v8 export to have an intermediate form where user chooses options Add option to export assigned docs as attachments + Add method to handle this and gracefully accept missing docs as that will be quite common (log them I guess) Modify v8 export to export everything (at least teh wikiable and attachable and custom fieldable) Uniquify: go through all and check which ones need to be uniquified by checking db schema of v7 or biz rules maybe @@ -82,6 +83,7 @@ Modify v8 export to export everything (at least teh wikiable and attachable and Region - wiki, files -> User "V7_REGION_WIKI_REPOSITORY_regionnamehere" this is preliminary as there is a ton of other shit to import from region into various other areas but it has a wiki so that should be dealt with +Finish off the v8 test export then get the below shit done so can move to stage 3 ASAP @@ -93,6 +95,16 @@ todo: PLANNING workorder data and class and route structure: Controller - all in root controller or seperate controllers? likely follows biz object decision Use foreign keys!! + Consider UI in this as well, will need to decide at least what is visible when + All workorder in one document and just really really tall? (people bitch about RI requiring too many navigation steps to get to shit) + Header and items in one document then bottom in seperate pages? + Is it going to be far easier to code this bitch if I have all the workorder data at hand or..? + How does WBI handle all this because it's kind of the poster child for RAVEN + Workorder is one of those things that may require different views for phone and tablet and laptop etc + Kind of like two views, tiny phone and anything larger + On a PC people will want and expect it to look as much like v7 workorder as possible, maybe that's still a valid layout + just tweaked to work better as a web app a bit but theoretically I could almost duplicate that layout with the tools I have + TTM!! Don't re-invent the wheel! PLANNING Workorder templates Keep as is or...? TTM!?