ayanova/devdocs/todo.txt

@@ -54,12 +54,23 @@
 SCHEDULE TODO:
 	Basically just replicate google calendar UI with our own related objects driving it
 	Day, Week, Month, Year, Schedule (not actually a calendar, but a list, do we need??), 4 days views
-	Data list functionality with filters to drive schedule, however people select them in the UI rather than the way we filter datalists now
-
+	Data list functionality with filters to drive schedule, however people select them in the UI rather than the way we filter datalists now (would be ideal)
+		only real filters are who, when where who could be also a particular customer (or is that it's own view)
+	Making more schedule forms is a relatively cheap thing to do so if there is a customer centric view then maybe that's it's own schedule page
+		entirely, e.g. a "View Schedule" menu item option in Customer opens a customer centric view since it doesn't need a lot of other shit
+		(maybe even a timeline??)  This differs from the record history, it's the business history 
+		Also can schedule work from that calendar maybe? Or follow ups etc
+
+TO BE DETERMINED:
+	How / if show multiple users schedules at once?
+		same calendar, separate calendars?  How do major softwares booking multiple people do it or should it be done?
+			what are the tasks when multiple??  
+				compare, look for openings?
 
 
 
 
+//..........
 	Dashboard / widgets
 	Installer INNO
 		version with postgres included, version without postgres included
@@ -761,3 +772,4 @@ MID CENTURY MODERN TUNES - https://www.allmusic.com/album/ultra-lounge-vol-14-bo
 
 BUILD 131 CHANGES OF NOTE
 
+- case 3946 at a glance wiki present implemented