ayanova/devdocs/todo.txt

@@ -49,10 +49,19 @@ 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 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
+### 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
+			- 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)
+			- 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
+				- 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
+			- 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
 		- WIRE up save menu item and add code to disable save on broken rules (and make red, disabled etc)
 		- Wire up delete menu item
 			- api code is stubbed out for delete, need to write that as well
-		- Move ABOUT item to just above HELP in menu and remove from main NAV and make it navigate properly on click
+		
 		- DO I need to institute a back button? (in APP MODE?? installed to "desktop" on device will I be able to easily navigate without back and forward buttons)
 
 	- Navigation guard: navigate away with unsaved changes should warn and prevent but have option to continue anyway	
@@ -288,6 +297,8 @@ Make all fields work according to specs below
 			- List should remember where the user was when they go to edit and back again
 			- What to do if they edit?  Refresh the list but keep the same page location?
 
+	- something I just forgot as I went to write it and got stuck reading older shit here
+
 	- SCROLL POSITION !! - Very important, must return UI to exact scroll position on navigation backwards, not doing so causes a hellish UI to use.
 		- Same position in window
 		- Same settings in any grids being shown and scrolled to same point in grids