devdocs/specs/core-notification.txt

@@ -30,7 +30,7 @@ IMPLEMENTATION PATH / PLAN - code as minimal a route as possible to get to worki
 		should it submit and send immediately bypassing generator as just an immediate test.
 		 OR 
 		 maybe it's an option for the user to choose.
-		 
+
 	widget / user crud ops and tag filtered in both App and in smtp
 	Then viewed in UI and worked with, properly shows count waiting etc
 	Examine system, bulletproof it as much as possible from first impressions
@@ -40,6 +40,20 @@ IMPLEMENTATION PATH / PLAN - code as minimal a route as possible to get to worki
 todo: Make the notification subscription front end page
 	At least enough to subscription to widget biz notifications
 	with translation keys
+	route needed of existing subs
+	route to add sub
+	route to delete sub
+	ui list of subs editable and saveable as a collection?
+	biz object
+	do it like widgets list and widget items, list up front and edit behind
+	TODO:
+		Do from front end back to server
+		SubscriptionList datalist needed first
+			timespan ui type for grid display
+		then edit form and routes can be added
+			Going to need a timespan control for editing
+
+
 todo: make the ops notification front end page
 todo: make the biz notification page
 todo: implement the Widget and User crud notification systems as per spec with an eye to replicating everywhere and allowing for specialty other types in system