ayanova/devdocs/todo.txt

@@ -15,15 +15,17 @@ TODO CLIENT STUFF
     TODO NEXT
 
 DATETIME - Ok, fuck a combined date and time, no one else seems to support it but me so split it into separate components:
-- How to work with getting and setting a value from a component?  Because datepicker expects a string of only date and barfs otherwise but I have a combined field that needs to be set as well
-	-https://codepen.io/anon/pen/dQJOyQ?editors=1010 ??
-	- Get the test form working with a custom date and time thing like this:
-		- single read only text field with initial display of date and time in users's locale format
-		- A button to the left with a calendar icon to trigger a date picker to adjust the date
-		- A button to the right with a clock icon to trigger a time picker to set the time
-		- Once this is working how I like then make it a VUE component that is self contained
-			- Date and time formatting and display need to be abstracted in case we change date libs from dayjs to something else
-		- Must validate and report validation errors just like the built in fields do
+
+
+- Wrap the date picker to work with our dates without losing time.
+- Wrap a time picker to work with our dates without losing the date.
+- Once this is done then combine them into a single component that:
+	-wraps both pickers as buttons to trigger selection on either side of a text that displays read only the locale formatted dt	
+	- single read only text field with initial display of date and time in users's locale format
+	- A button to the left with a calendar icon to trigger a date picker to adjust the date
+	- A button to the right with a clock icon to trigger a time picker to set the time
+	- Must validate and report validation errors just like the built in fields do
+- Test on mobile and desktop and then if all is well we can move on to the other field types
 
 
 DON'T code the user options with the currency symbol etc until after it's all been worked out client side.  Use static values instad in locale.