ayanova/devdocs/todo.txt

@@ -15,7 +15,7 @@ TODO CLIENT STUFF
 TODO NEXT
 
 IMMEDIATE ISSUES:
-Now clearing server error box thanks to some last minute changes, but those chagnes need to be looked at and start with **THIS** in gzvalidate and move on
+How and where to display form errors that are unhandled on form and not related to notification, i.e. ErrorServerUnresponsive when attempting to use a form that was already open
 
 See server project widget validation code which will now give server errors on certain values so can proceed with work.
 Current issue is where to put notifications, code is to help test,
@@ -25,8 +25,9 @@ Issues:
 ISSUE: need to display multiple types of messages, best way to do that??
 	- DONE: Local validation errors - this works and is done
 	- DONE: Server errors - This works and is done
-	- Important transient application messages, equivalent of dialog boxes that popup in apps, i.e. "This object has broken rules, fix them to be able to save" or "Insufficient rights" or whatever
-		- Dialogs suck in web ui, so this should be right on the page itself in an alert probably
+	- Application errors 
+		- Make them show with the server error box, rejig it as a generic error box
+		- App errors don't need to survive page reload or api call, if they are that serious then they would be notifications instead
 	- Notifications, stuff that you want to know is there and can go and look at but isn't urgent enough to put in the users face
 		- Used for notification system, non-urgent system messages, direct messages from users etc, anything that isn't immediately important
 		- This seems like an application wide thing so maybe a bell icon that takes to another area of the program, or opens a div at the top or bottom of the page??