admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2019-06-18 00:24:41 +00:00
parent 48a7081708
commit b8e77b8a58
1 changed files with 7 additions and 8 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
ayanova/devdocs/todo.txt
View File

@@ -71,20 +71,19 @@ DONE (NEEDS re-test ON MOBILE for appearance and functionality): Reports - stub
- If I use the library dialog component and figure it out in theory it will just popup when required and not pollute the shell template with anything. I guess it inserts itself into the dom. - If I use the library dialog component and figure it out in theory it will just popup when required and not pollute the shell template with anything. I guess it inserts itself into the dom.
- I have a question in to the developer about how to do the example with templates here: https://github.com/yariksav/vuetify-dialog/issues/39 - I have a question in to the developer about how to do the example with templates here: https://github.com/yariksav/vuetify-dialog/issues/39
- The vuetify dialog example I would use is here: https://vuetifyjs.com/en/components/dialogs#form and the top one without activator here: https://vuetifyjs.com/en/components/dialogs#without-activator - The vuetify dialog example I would use is here: https://vuetifyjs.com/en/components/dialogs#form and the top one without activator here: https://vuetifyjs.com/en/components/dialogs#without-activator
TODO: For form initialization modify widget edit make an simple init call for onCreate DONE: For form initialization modify widget edit make an simple init call for onCreate
- Init should be promisified and have a chain of promises for form initialization so async stuff can properly finalize before init is done and code moves on - Init should be promisified and have a chain of promises for form initialization so async stuff can properly finalize before init is done and code moves on
TODO: Fill selection boxes, autocomplete handling etc DONE: Turn widget edit ROLES into a static select populated from server
- Use the enumpicklist route to get a list of roles and use it for the widget UI - Use the enumpicklist route to get a list of roles and use it for the widget UI
- Do I cache that shit? Cache invalidation is hard. ### TODO: Widget - NOTES FIELD
- Also what is the best way to load that stuff, some will be unbounded and should be done through autofill / search route, but some are static like the roles and rarely change and small so they might as well just load all at once.
- Need to factor in both types really I guess.
TODO: Widget - NOTES FIELD (look for others missing not below)
TODO: TAGS!!! Do tags mofo TODO: TAGS!!! Do tags mofo
TODO: Custom fields
TODO: Record history display / check other AyaNova 7 options / buttons that need to carry forward TODO: Record history display / check other AyaNova 7 options / buttons that need to carry forward
- Some of this stuff is stage 2 for the edit form - Some of this stuff is stage 2 for the edit form
TODO: WIKI TODO: WIKI
TODO: Attached documents TODO: Attached documents
TODO: Custom fields
RETEST HERE ON ALL DEVICES
TODO: NOW THAT FORM IS THERE MOSTLY, CLEAN UP CODE FOR RE-USE in many other forms TODO: NOW THAT FORM IS THERE MOSTLY, CLEAN UP CODE FOR RE-USE in many other forms
- Don't need to replicate common code so put it somewhere else - Don't need to replicate common code so put it somewhere else