ayanova/devdocs/todo.txt

@@ -25,10 +25,10 @@ All platforms and browsers
 		- STATUS: I'm going to do another update and see if it's handled properly
 		- I thought they would update automatically via the loader code?!?
 		- 
-	- FIXED: Login user name field auto capitalizes first character on phones, need that to not do it
-	- Login, doesn't have any ui if failed login, maybe a red frowny face icon? :)
-	- need clear buttons on pw and login
-	- Numeric input fields don't give numeric keyboard
+	- IMPLEMENTED / NOT TESTED: Login user name field auto capitalizes first character on phones, need that to not do it
+	- IMPLEMENTED / NOT TESTED: Login, doesn't have any ui if failed login, maybe a red frowny face icon? :)
+	- IMPLEMENTED / NOT TESTED: need clear buttons on pw and login
+	- IMPLEMENTED / NOT TESTED: Numeric input fields don't give numeric keyboard
 	- Save on broken rules in Widget edit form it's not clear that save does nothing if there are broken rules.  Button should be deactivated or there should be a message if you click on it or something.
 		- Red outline and inactive seems ideal
 	- Save button placement, not sure I like having to scroll down the page to save on small format screens where there is potentially going to be a *lot* of scrolling needed which hides the info box etc
@@ -41,10 +41,15 @@ All platforms and browsers
 		- currently widget edit doesn't have a particular look or title so if you are at the top of it on a small device you can't see the url fully or really know which page it is
 		- A small title top left that stands out might be approprpiate, also a icon beside it?
 
-	- Application name is all lowercase "ayanova" when installed to device, must be something in the manifest files?
+	- IMPLEMENTED / NOT TESTED: Application name is all lowercase "ayanova" when installed to device, must be something in the manifest files?
 	- Check about page localization code, is it firing in the right place because on Edge and iPad firefox it didn't show localized at first until a refresh so it fetched the keys but didn't display properly
 	- Calendar on iPad in two occasions with ff and opera the calendar date could not be selected until a time was changed then the date worked.  Before that it would always stay the same no matter what selection was made and the UI would not show a change on select or press of date either.
-
+	
+	- Form menu
+		- for now make stub items similar to v7: Print, wiki, history, duplicate, delete, help
+	- Make a 3 dots menu item that is contextual and appears at the top of any form in the shell interface??
+		- Put the help option there since it's contextutal to whatever form is being displayed
+		- Move help menu item in shell into menu as bottom item instead
 
 
 iPad 
@@ -119,6 +124,10 @@ TODO NEXT
 End to end action
 	- Code for new record to the server
 
+TODO: Delete widget button and rights stuff
+TODO: History button, other AyaNova 7 example buttons all need to be there or their equivalent, do we need a top menu type thing?
+	- Also Save button at bottom seems like an issue too
+TODO: Rights stuff for form if insufficient rights / read only etc
 TODO: About AyaNova form should show the exact client browser and device info as much as possible as it also serves as the tech support info thing
 	- Maybe make a support info local class in client that can gather the correct info and then can be used to both display and to send to us for support with a click
 	- Also add a tech support reporting form / button that will gather up support info and possibly also send it to us??