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
2020-04-06 22:09:29 +00:00
parent ba8c4a66d1
commit f26f97aff3
1 changed files with 12 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

22
ayanova/devdocs/todo.txt
View File

@@ -54,19 +54,21 @@ CURRENT TODOs
todo: REPORT LIST
- Stub out some fake reports in a drop down selection for testing, doesn't have to do anything but be present
- Stub out some fake reports in a drop down selection for testing
- Have it open a report form stubbed out with a report control on it
- Test on mobile once done
- WAS implementing as a dialog, that needs to be replaced now, either I need to follow the vuetify dialog example and put it in the shell app.vue or I'm going to use the dialog library I already have once I get an answer on templates
- If I use the vuetify example it means there needs to be a dialog in the shell that is activated from any form inside it but it also needs to be bound and shit and won't be very clean
- 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.
- NEED to think about this one, can't put thousands of reports in a list in the menu
- One idea I just had is maybe the last report used for that form is surfaced on the context menu in addition to the regular reporting option
- If take last report used then it directly opens a preview
- If take generic Report option then it opens to another form for choosing the report and whether to print or not etc
- Implement chooser similar to gzconfirm seems best idea, original thinking below...
- WAS implementing as a dialog, that needs to be replaced now, either I need to follow the vuetify dialog example and put it in the shell app.vue or I'm going to use the dialog library I already have
once I get an answer on templates
- If I use the vuetify example it means there needs to be a dialog in the shell that is activated from any form inside it but it also needs to be bound and shit and won't be very clean
- 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.
- ACTUALLY if it doesn't render it doesn't render so it doesn't matter as it won't be taking up space anywhere unless there's a render of it, so maybe in app is fine
- NEED to think about this one, can't put thousands of reports in a list in the menu
- One idea I just had is maybe the last report used for that form is surfaced on the context menu in addition to the regular reporting option
- If take last report used then it directly opens a preview
- If take generic Report option then it opens to another form for choosing the report and whether to print or not etc
- SB translated in form as "Report" not "Print" because it's going to be likely that people will want to work with pdf (email, download) instead or just the view of it, print is maybe not a common option.
todo: WIDGET EDIT FORM SAVE AND NEW BUTTON LIKE V7?
- NO, just keeping this until I get here in case I think I need it again, don't need it.
todo: SEARCH UI