This commit is contained in:
@@ -48,11 +48,9 @@ CURRENT TODOs
|
||||
SHELL / NAV / MENUS / LAYOUT
|
||||
|
||||
|
||||
|
||||
TODO: Put useful info in page title when routing so that user can see history and easily select past record etc, right now it always just says AyaNova and nothing more
|
||||
- Maybe each page can do it's title or maybe the menu can do the title?
|
||||
- Not sure which is best way to go or if it even matters
|
||||
- In a PWA you can't see the title anyway so if it matters it should be inside the shell anyway
|
||||
TODO: Trial route ui support in client
|
||||
- Add an area to support refreshing the database and generating test data
|
||||
- Would be useful to see and manage OPS things related to deployment to server just to save time, can refine them later
|
||||
|
||||
TODO: WHEN GET TO HERE, POST TO SERVER AND TEST DRIVE AGAIN WITH ALL BROWSERS / DEVICES
|
||||
|
||||
@@ -159,13 +157,11 @@ TODO: MAIN GRID LIST ANALYSIS, DESIGN AND COMPLETION KEEPING IN MIND TTM
|
||||
- Needs to remember last settings (stored centrally) like filter used, number of rows etc
|
||||
- When user opens up AyaNova it should always look the same in each area as last time they were there
|
||||
|
||||
TODO: change LT for OPerations console and remove "console" (main nav panel)
|
||||
|
||||
|
||||
TODO: Make errorBoxError message box on all forms a component instead as it's just boilerplate
|
||||
|
||||
TODO: Trial route ui support in client
|
||||
- Add an area to support refreshing the database and generating test data
|
||||
- Would be useful to see and manage OPS things related to deployment to server just to save time, can refine them later
|
||||
|
||||
|
||||
TODO: TIME ZONE MISMATCH MESSAGE
|
||||
- Time zone mismatch message sb localized and far shorter with an actionable link to that area of the client
|
||||
@@ -195,12 +191,17 @@ TODO: ANY TIME - SIDE v7 STUFF DataDump plugin needs an explanation of what it i
|
||||
|
||||
|
||||
=================== FINALIZATION OF EDIT FORM BEFORE "STAMPING" OUT MORE ===========================================
|
||||
TODO: REPORT LIST STUB
|
||||
TODO: REPORT LIST
|
||||
- Stub out some fake reports in a drop down selection for testing, doesn't have to do anything but be present
|
||||
- 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
|
||||
- SB localized 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?
|
||||
- will the menu be too crowded?
|
||||
|
||||
@@ -5,7 +5,7 @@
|
||||
<script>
|
||||
import UnderConstruction from "../components/underconstruction.vue";
|
||||
/**
|
||||
*
|
||||
* NOTE: In router.js I've made the ayatype parameter OPTIONAL, so make sure to deal with that, it may be undefined, not just zero
|
||||
* - PUT SEARCH into main menu, it's constantly there like help with the source as part of the data sent with the click
|
||||
- I.E. source could be widget from list or widget entry form and so user is searching widgets or source could be a main page where there is no source so it's empty and search everything
|
||||
- User clicks on search, it opens a main search form view which is also accessible under HOME section normally so two ways to get there
|
||||
|
||||
@@ -675,6 +675,22 @@ function generateMenu(vm) {
|
||||
});
|
||||
}
|
||||
|
||||
//STUB REPORTS
|
||||
//Report not Print, print is a further option
|
||||
menuOptions.menuItems.push({
|
||||
title: window.$gz.locale.get("Report"),
|
||||
icon: "file-alt",
|
||||
key: FORM_KEY + ":report",
|
||||
vm: vm
|
||||
});
|
||||
|
||||
menuOptions.menuItems.push({
|
||||
title: "stub: Last report used",
|
||||
icon: "file-alt",
|
||||
key: FORM_KEY + ":report:STUBlastusedreportid",
|
||||
vm: vm
|
||||
});
|
||||
|
||||
if (vm.rights.change) {
|
||||
menuOptions.menuItems.push({
|
||||
title: window.$gz.locale.get("Duplicate"),
|
||||
@@ -684,15 +700,6 @@ function generateMenu(vm) {
|
||||
});
|
||||
}
|
||||
|
||||
//STUB REPORTS
|
||||
|
||||
menuOptions.menuItems.push({
|
||||
title: window.$gz.locale.get("Print"),
|
||||
icon: "print",
|
||||
key: FORM_KEY + ":report",
|
||||
vm: vm
|
||||
});
|
||||
|
||||
window.$gz.eventBus.$emit("menu-change", menuOptions);
|
||||
}
|
||||
|
||||
|
||||
Reference in New Issue
Block a user