From 18d549f0195b4cfba8bdf74e9c39819afc4657db Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 2 Nov 2018 20:25:01 +0000 Subject: [PATCH] --- devdocs/todo.txt | 68 +++++++++++++++++++++++++++--------------------- 1 file changed, 39 insertions(+), 29 deletions(-) diff --git a/devdocs/todo.txt b/devdocs/todo.txt index 407b7939..336a7c12 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -18,37 +18,53 @@ Ensure all modern best practice security is properly enabled on helloayanova.com -CODING WORK -+++++++++++ - -DEVELOPMENT SCHEDULE --------------------- -WEEK OF 2018-10-22 - Learn Vue, select a UI framework - +CODING +++++++ +refs: - https://vuetifyjs.com/en/components/navigation-drawers - https://vuetifyjs.com/en/examples/layouts/googleContacts - - - Read this: https://qiita.com/nickhall/items/d1043f3f9874c90b6f8e - And this: https://logrocket.com/blog/an-imperative-guide-to-forms-in-vue-js-2/ +WEEK OF 2018-11-05 - RAVEN shell start work. +- 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 + - 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 - - Make a basic temporary test for learning PWA app code against RAVEN server a throwaway initial stab at RAVEN for learning what is needed to learn - - Be sure it's component-ized properly: https://vuejs.org/v2/guide/components.html#Organizing-Components - - Document areas needed to focus on for learning and then do them - - Examine on phone, ipad, all desktop browsers, low bandwidth test, no bandwidth test - - Appearance, look and feel: Look at this, it's modern and cool looking and gives an idea of what I should be considering: - https://laravel-enso.github.io/enso/videos/bulma_quick_walkthrough.webm - -WEEK OF 2018-10-29 TO NOV 12th - RAVEN shell start work. - - Plan out the shell basic requirements - - Make a widget view/list/enter/edit - - Login, logout, notification, localized text, status - - Graph / Readonly UI component - - Widget: List, search, edit, localized WIDGET UI components - - At the end of the two weeks re-assess and see what needs to be the focus going forward and if anything is amiss +- Stage 2: + - Make it work with the backend: + - Login, logout + - 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 3: + - At the end of this phase re-assess and see what needs to be the focus going forward and if anything is amiss - Plan out the next phase + - UI layout design, how I want to see things, don't re-invent the wheel; v7 isn't perfect but I don't have forever either + - Just remember roles and role based security and that might lead into the UI + - the dashboard can drive a lot because for example a graph or list of workorders could also be where you add a new wo + - Thorny issues: + - Reporting + - Notifications from the server + - File upload / download - NOTE: many users want to see some progress on v8 so it's important that the initial shell have some "flash" to it - Nice transitions - Some sample charts @@ -61,12 +77,6 @@ WEEK OF 2018-10-29 TO NOV 12th - RAVEN shell start work. - - - - - - IMMEDIATE ITEMS: ================