ayanova/devdocs/todo.txt

@@ -13,34 +13,22 @@ TODO CLIENT STUFF
 #### A PHONE IS PROBABLY NOT THE MOST COMMON SIZE FORM FACTOR THAT WILL BE USED SO SUPPORT IT, YES,  BUT DON'T GET HUNG UP ON IT TO THE POINT WHERE IT RUINS THE EXPERIENCE ON A FULL COMPUTER OR TABLET
 
     TODO NEXT
-		- Misc items below to get feet wet (and clean up list see bottom item in MISC section)
-		- Make the list menu and options fully Functional
-		- CRUD form fully formed with custom fields (see below)
-		- Need a demo before people start revolting!!!!!
-
-
-	- MISC			
-		
-		- Clean up todo below here and up to "Stage 2", seems to be a lot of wild speculation and repeated stuff, need a clean list of discrete actionable items.
-
-	- Just get basic Functionality working then iterate rather than trying to plan out everything at once!!
-
-
-
 	
-	- numeric inputs need to be set as such so that the number keyboard appears
-	
-	- CRUD form for widget that supports all the aspects (NEED THIS BEFORE MUCH OTHER CODING HAPPENS)
-        	
+
+	- CRUD form for widget:        	
 
         - Everything needs to work in this form right down to the reports so that once it's done I can move forward confidentally with testing, demo-ing and with cranking out the other forms
         - Don't want to solve any problems that should have been solved with this form later as I will inevitably be full on copy and pasting once I get it down and so it needs to be as solid as possible First
+		- TEST SMALL and LARGE device layout regularly, don't get too far ahead of the testing
         - Every type of entry field fully localized properly including numeric, date, time, tags etc			
 			- Client: initialize after login sets locale formats for everything.
 				- Best to do this useroptions stuff after a form is in place that I can play with at the client and experiment to see what is possible
 				- How much flexibility do we have to set things like numeric / currency input / display format?		
 				- First it gets useroptions to know what to override or not, then sets defaults based on browser or override settings in central client area for all display/parsing etc
 		- All numeric and date displays and input in locale format
+		- numeric inputs need to be set as such so that the number keyboard appears
+			- And all specialty inputs of course
+		- Custom fields implemented!
         - A printable report
             - Even if there is no designer yet for the report and it has to use a manually created report format HTML doc
         - Error and validation properly implemented