ayanova/devdocs/todo.txt

@@ -5,28 +5,21 @@ PRIORITY - ALWAYS Lowest level stuff first, i.e. TODO at server, api route chang
 
 
 
-
-NOTIFICATION
-____________
-
 ## CURRENT STAGE: 
 
 
-##########################
-
-
-todo: Evaluate form generate sample data sb inside a dialog, it's only done once or twice at most and takes focus away from the other buttons and future stuff
-
-todo: PMBIZ AND QUOTEBIZ AND QUOTETEMPLATEBIZ objects are fucked, seems to be an outdated version
-	redo it from current best practices (PM TEMPLATE BIZ?).  Note that it is missing many new methods like notifidation etc because of being fucked
-todo: UserBiz is partway there but needs also to be standardized like the rest
-
-todo: userbiz delete, add notification subs and events to the delete related code
-todo: workorderbiz::putworkordergraphitem no longer requires ayatype parameter since the corebizobject has it already now built in
-todo: workordertemplatebiz has inconsistent naming etc
-
-
 todo: CUSTOMER UI FORM AND USERS OFF OF THAT
+	LOOKING AT THINGS SINCE BELOW WRITTEN:
+		My lists suck for filtering user types to specific kinds:
+		Either combine all users like v7 (easiest, no need to change anything but merely additional stuff)
+		or
+		Make userlist a regular data-table object not my fancy one so I can then tie it to a dedicated list object at server, then have two separate ones, one in Customer area and one in User area
+			or
+			Figure out how to have my data-table custom system support pre-additional criteria (which it really should)
+		or
+			As per below, make my datalist have an alternative display without datafilter UI stuff and just takes a provided datalistview
+
+
 	Customer User UI area accessed from Customer form for CRUD User accounts tied to customers and also for setting up Notifications for those users
 	this is big and needs it's own NOTIFICATION area as well
 	can customer control this or does the biz admin control this?
@@ -37,7 +30,8 @@ todo: Customer User list form side track but relevant to this
 	Or is it both maybe, shit have to pick one
 	I can see a case for wanting to just see every user together regardless of type and another case for wanting to simplify it down to just going via the customer themselves
 		have to imagine the use cases and go accordingly.
-		My gut feeling is people would rather go via Customer page since they are likely in there via interacting with the customer in the first place, i.e. we fired Bob so take him off or we hired shirly so put her on or why am I not getting notifications can you test it etc
+		My gut feeling is people would rather go via Customer page since they are likely in there via interacting with the customer in the first place, i.e. we fired Bob so take him off or we hired 
+		Shirly so put her on or why am I not getting notifications can you test it etc
 		Case for the full list including customer users is really just a "it woudl be nice to see them all in one place" but they aren't like normal users and will need an alternative editing UI anyway
 		So My gut feeling is to do it via the Customer as a limited list, not via the regular Users page
 		it would have it's own edit form and own list as it would not need the full datalist treatment in theory