+ Architecture: separate objects for each widget
+
+ Architecture: translucent configuration, with global values
+ shining through where a specific widget provides no local
+ value.
+
+ Architecture: decouple related elements using
+ publish/subscribe. (Jakub will probably do this.)
+
+ Architecture: managed widgets held in the Torus. Maybe.
+
+ Architecture: "3rd party widget platforms". I seems to recall
+ I copied this off one of Seb's lists on the flipchart, but I
+ can't remember what it refers to. Can anyone?
+
+ Allow debug() to be customised by setting a callback function
+ that is passed the string rather than just giving it to
+ console.log().
+
+ Create a logging widget which displays the output of debug().
+
+ Check that library selection (authentication) by hostname
+ works for MKWS.
+
+ Add library selection by secret key as an alternative to
+ selection by user/pw. This is appropriate for
+ security-conscious customers to embed in their own CORS-aware
+ Apache2 configuration.
+
+ Auto-executing widgets should be able to specifying limits (as
+ a full set of MK2-like widgets does in order to implement
+ facets).
+
+ Auto-executing widgets should be able to include filters (as a
+ full set of MK2-like widgets does in order to implement the
+ Target facet). This can be used to implement target categories
+ as well as the current cruder target-selection-by-ID facility.
+
+ Do target selection by UDB rather than ZURL. May need SP
+ changes, but we might already have the necessary functions.
+
+ We will want a facets-only widget, e.g. to list top authors
+