ayanova/devdocs/todo.txt

@@ -46,33 +46,23 @@ CURRENT TODOs
 =-=-=-=-=-=-=
 
 
-TODO: UI would be greatly enhanced if server defined form customization rules for required fields REGULAR fields only (custom are already handled) were incorporated into client end before roundtripping to the server
-	- Right now it has to save the record to get the return errors about required regular fields, that is shit.  The client is easily able to tell what is required in the form customization so it should be able to surface that up front
-	- This will save bandwidth and annoyance factor 1000 for people
-	- ERROR MESSAGE: 
-		- Currently it appears identically to the stock required but should indicate it's user required
-		- Need new or maybe already exists locale key for it, currently it's this:  //   "ErrorRequiredFieldEmpty": "{0} is a required field.  Please enter a value for {0}",
-		
 
-TODO: Widget edit form, new record sb time and dates pre-filled in? Server involved? How to handle new record initial date set?
-	- Seeing a few issues that are probably related to having an empty record on start of new object
-	- Don't start blank basically
-	- some objects may be configurable what the default date/time range is so maybe enable that for widget to test
-	- SB defaults route on server or is this a profile thing and user selectable?
+TODO: Why am I using different values for ref in the form than the server knows the fields to be named???
+	- Answer is I'm not actually, the server knows them as the field names of the widget object for example StartDate but sends them not capitalized on first character
+	- I'm thinking of the LT keys which because they need to be system wide unique are prepended with the object name
 
-TODO: Form customize UI
+TODO: Form customization - hidden fields support
+	- Obviously not the required ones (how to know if required?)
+
+
+TODO: Any other widget form stuff, then do a on server test (bump version) then can proceed 
+
+
+
+TODO: MOVE THIS DOWN?  AFTER ALL WIDGET FORM STUFF IS DONE Form customize UI
 	- Where you create custom fields and edit 
 	- If a user changes a field data type there needs to be a big warning before accepting it.
 
-TODO: Support form customization beyond Custom:
-	- hide fields not used
-	- force user to enter a value in a field optionally that isn't already required
-
-TODO: Save button isn't enabling on changes in new record when it should.  Enter in a value in the Name field of an empty record and move to a new field and it should immediately show the save button due to dirtiness?  
-	- Or is it becuase of broken rules that are not being displayed immediately? (new record should really show a bunch of broken rules right away as it has some empty and required fields)
-		- Yes this seems to be it, also until all rules are unbroken save sb not enabled, but it appears that one more edit needs to be done after the last broken rule to unstick it or maybe it's the case mismatch issue above that will fix it
-
-