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-19 22:39:09 +00:00
parent 89fd043548
commit b7d8075ed5
1 changed files with 7 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

7
ayanova/devdocs/todo.txt
View File

@@ -78,22 +78,27 @@ DONE: Turn widget edit ROLES into a static select populated from server
DONE: Widget - NOTES FIELD DONE: Widget - NOTES FIELD
TODO: TAGS!!! TODO: TAGS!!!
- Adding a new tag doesn't flag the record as dirty! (selecting does though) - Adding a new tag doesn't flag the record as dirty! (selecting does though)
- Localize the text enter a tag
- Layout: tags seems to buried into the rest of the form fields, maybe needs more whitespace around it, or a box - Layout: tags seems to buried into the rest of the form fields, maybe needs more whitespace around it, or a box
- COMPONENTIZE - COMPONENTIZE
- Could auto-insert tags in suggestion list like the current year or month or year/month/day or user name or ?? - Could auto-insert tags in suggestion list like the current year or month or year/month/day or user name or ??
TODO: Custom fields TODO: Custom fields
- Componentize
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
- Record history could be displayed on a timeline: https://vuetifyjs.com/en/components/timelines - Record history could be displayed on a timeline: https://vuetifyjs.com/en/components/timelines
- componentize
TODO: WIKI TODO: WIKI
- componentize
TODO: Attached documents TODO: Attached documents
- componentize
RETEST HERE ON ALL DEVICES 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
- 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? - 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? - some forms will have special needs but could handle them outside of the regular boilerplate shit?
TODO: Outstanding case with vuetify bug in clear button when readonly, check if fixed and if it isn't might need a workaround TODO: Outstanding case with vuetify bug in clear button when readonly, check if fixed and if it isn't might need a workaround