This commit is contained in:
@@ -4,7 +4,7 @@ Success is the ability to go from failure to failure without loss of enthusiasm
|
||||
|
||||
"A smooth sea never made a skilled sailor" Franklin D. Roosevelt
|
||||
|
||||
|
||||
"Every man has two lives, and the second starts when he realizes he has just one" ~ Confucius
|
||||
|
||||
BIG PLAN
|
||||
|
||||
@@ -71,7 +71,9 @@ 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.
|
||||
- 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
|
||||
#### HAPPY MONDAY MUTHAFUCKA! TODO: Fill selection boxes, autocomplete handling etc
|
||||
TODO: 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
|
||||
TODO: Fill selection boxes, autocomplete handling etc
|
||||
- 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.
|
||||
- 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.
|
||||
|
||||
Reference in New Issue
Block a user