From e4991bdade495b6e76ec6d1aa69df0b25c826353 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 14 Nov 2018 00:05:45 +0000 Subject: [PATCH] --- devdocs/todo.txt | 51 ++++++++++++++++++++++-------------------------- 1 file changed, 23 insertions(+), 28 deletions(-) diff --git a/devdocs/todo.txt b/devdocs/todo.txt index 09bf7ab3..8fd3252c 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -32,38 +32,30 @@ WEEK OF 2018-11-12 - RAVEN shell start work. YAY! NEXT UP / CURRENTLY WORKING ON: + - Version / copyright info on bottom banner - Look over the (now two) api calls and look for optimization and code shrinkage / de-duplication - apiurl handling - - Move on to the next thing (build and post?) - - - -/* eslint-disable */ -- Stage 1: - - Make a rough but relevent shell with the idea of this being the actual release shell (Refine on the fly rather than re-do) - - Proper graphics all over - - Dummy form with all RAVEN required input controls on it for testing - - Document a release procedure while doing the next step: - - Post a dist version up to the dev server so can test with all our devices and note what works and what doesn't + - Get it from the current url if nothing entered + - need a way to enter it when not logged in yet + - Needs to preserve on refresh / logout + - About page with license info, server version / client version + - Dummy form with all RAVEN required input controls on it for testing + - As if a widget but not actual widget api calls yet so can expand this form later and save time + - Document a release procedure while doing the next step: + - Post a dist version up to the dev server so can test with all our devices and note what works and what doesn't - Test initial shell and dummy input form on all devices including a simple e2e test of some kind to get a start on that aspect - Test as PWA on all devices -- Stage 2: - - Make it work with the backend: - - Error handling at client (log? display?) - - Notification of some kind (bell / toast) - - Localized text - - About page with license info - - Add intro.js somewhere, even if just a quick hello type thing with one single pointer to something on the screen - - Look into: should each component do it's own ajax calls? - - Vuex, some data should be stored centrally, what state goes in vuex? - - creds? - - LT cache? - - app state - - Make a widget component / form to view/list/enter/edit - - Graph / Readonly UI component - - Widget: List, search, edit, localized WIDGET UI components - - Post up another build with the entry form and re-round of testing + +- Stage 2 AFTER POSTED TEST ROUND COMPLETED + - Error handling at client (log? display?) + - Notification of some kind (bell / toast) + - Add intro.js somewhere, even if just a quick hello type thing with one single pointer to something on the screen + - Look into: should each component do it's own ajax calls? + - Make a widget component / form to view/list/enter/edit + - Graph / Readonly UI component + - Widget: List, search, edit, localized WIDGET UI components + - Post up another build with the entry form and re-round of testing - Stage 3: @@ -77,6 +69,8 @@ NEXT UP / CURRENTLY WORKING ON: - Notifications from the server - File upload / download - Offline abilities? + - TIME TO MARKET TIME TO MARKET TIME TO MARKET + - RELEASE IT, RELEASE IT, RELEASE IT!!!! - Need a good think about this, time to market is of utmost importance but it would not hurt to see what can be done now or defferred to vNext - v7 is technically an always online app so there's that. - Would be nice to maybe be able to do some limited stuff offline @@ -92,7 +86,8 @@ NEXT UP / CURRENTLY WORKING ON: - Use Intro.js to introduce the demo to new users and also to introduce the UI elements and it will be used all over the place!! - +- Stage 4: + - Customer demo!!