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-04-19 20:33:57 +00:00
parent b9440822b4
commit 56f8ee0a35
2 changed files with 11 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

16
ayanova/devdocs/todo.txt
View File

@@ -30,14 +30,14 @@ All platforms and browsers
- DONE reorganize SAVE, DELETE ETC, put a divider between main form actions and then all the myriad of secondary things - DONE reorganize SAVE, DELETE ETC, put a divider between main form actions and then all the myriad of secondary things
- DONE LOCALIZE check all new menu items, some might be not localized (look for ALL CAPS) - DONE LOCALIZE check all new menu items, some might be not localized (look for ALL CAPS)
- DONE WIRE UP logout link to go to login form and logout properly - DONE WIRE UP logout link to go to login form and logout properly
### THIS NEXT -> - JUST CHANGED the keys to a new system and dropping data property, right in the middle of it actually but it needs to be changed back partially see below - DONE JUST CHANGED the keys to a new system and dropping data property, right in the middle of it actually but it needs to be changed back partially see below
- First of all, put gzmenu on to the vue object in main so can use it for little utilities like click handling, generating unique nav keys etc - DONE First of all, put gzmenu on to the vue object in main so can use it for little utilities like click handling, generating unique nav keys etc
- Reason was to ensure key uniqueness (two nav items with same key are erroring) - DONE Reason was to ensure key uniqueness (two nav items with same key are erroring)
- HOWEVER as I'm thinking about it now, do we really want all that url stuff being in the key? - DONE HOWEVER as I'm thinking about it now, do we really want all that url stuff being in the key?
- Instead, change back to using data but add a third parameter to make sure that keys are unique somehow - DONE Instead, change back to using data but add a third parameter to make sure that keys are unique somehow
- That way we can put anything into the data key again because in future might need whole objects etc (almost certainly will) - DONE That way we can put anything into the data key again because in future might need whole objects etc (almost certainly will)
- Move ABOUT item to just above HELP in menu and remove from main NAV and make it navigate properly on click - DONE Move ABOUT item to just above HELP in menu and remove from main NAV and make it navigate properly on click
- Make about contextual and insert a menu item to view log - DONE Make about contextual and insert a menu item to view log
- TODO navigating through menu doesn't "back" properly when clicking back on browser controls - TODO navigating through menu doesn't "back" properly when clicking back on browser controls
- WIRE up save menu item and add code to disable save on broken rules (and make red, disabled etc) - WIRE up save menu item and add code to disable save on broken rules (and make red, disabled etc)
- Wire up delete menu item - Wire up delete menu item

5
ayanova/src/views/About.vue
View File

@@ -130,7 +130,8 @@ export default {
"LicenseSerial", "LicenseSerial",
"LicenseExpiration", "LicenseExpiration",
"SupportedUntil", "SupportedUntil",
"LicensedOptions" "LicensedOptions",
"Log"
]); ]);
}, },
created() { created() {
@@ -140,7 +141,7 @@ export default {
title: this.$gzlocale.get("HelpAboutAyaNova"), title: this.$gzlocale.get("HelpAboutAyaNova"),
menuItems: [ menuItems: [
{ {
title: this.$gzlocale.get("log"), title: this.$gzlocale.get("Log"),
icon: "glasses", icon: "glasses",
surface: true, surface: true,
key: "app:nav:log", key: "app:nav:log",