ayanova/devdocs/todo.txt

@@ -96,11 +96,14 @@ TODO: Attached documents
 RETEST HERE ON ALL DEVICES
 
 TODO: NOW THAT FORM IS THERE MOSTLY, CLEAN UP CODE FOR RE-USE in many other forms
+	- Look for things to componentize
+	- Look for things that are not specific to the widget edit form but can be abstracted away for other forms
 	- Don't need to replicate common code so put it somewhere else
 	- Are any of the controls better as a component and self contained to save the size of the form code and complexity?
 		- What I mean is, for example, a text entry field could be standardized then re-used as a component if it's props and settings take up so much space etc
 	- formstate shit is also menu shit really so can they be combined somehow, like present two sets of menu options one read only and one fully read-write?
 		- some forms will have special needs but could handle them outside of the regular boilerplate shit?
+
 TODO: Outstanding case with vuetify bug in clear button when readonly, check if fixed and if it isn't might need a workaround
 TODO: Document in user manual the Widget form as an example with instruction on how to use the various controls etc
 	- "Anatomy of a AyaNova Form"