# HG changeset patch
# User Paul Boddie <paul@boddie.org.uk>
# Date 1396303016 -7200
# Node ID 3605eb85d56f6b34ad18816ea105f035747aefd3
# Parent  859ab0b33ddaa82141e59e72be79b4e458ba655d
Added the ongoing "to do" list.

diff -r 859ab0b33dda -r 3605eb85d56f TO_DO.txt
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/TO_DO.txt	Mon Mar 31 23:56:56 2014 +0200
@@ -0,0 +1,63 @@
+Provide a means of reviewing and importing keys, most likely in conjunction
+with actions provided by MoinMessage. A special parser might be the most
+elegant way of displaying such content.
+
+(Make the macro aggregate feeds from a collection of sources, just like
+EventAggregator. This is arguably superior to using URLs directly because the
+sources are more easily managed and restrictions can also be placed on URLs
+(in case someone deploys a resource that is too large for the wiki, for
+example, causing the wiki to become unresponsive or unavailable).)
+
+(Provide improved containers and navigation for update content.)
+
+Consider integration with MoinMessage, possibly adding MoinShare compatibility
+to posted content in MoinMessage (page regions would have a "moinshare"
+attribute), and supporting MoinMessage mailbox inspection (for internal use)
+and summaries (for external use) in MoinShare.
+
+  Provide more efficient (indexed) access to message stores.
+
+Support packaging of wiki content into MoinMessages such that referenced
+resources such as attachments are included in messages and accessible when
+messages are displayed by the recipient, potentially without creating the
+corresponding attachments in the recipient's system.
+
+  Message body content is first parsed and attachments identified. References
+  to attachments are rewritten in the formatted output, and the attachments
+  themselves are added as additional parts to the message.
+
+    Outgoing HTML content is parsed using a modified version of the
+    MoinMoin.support.htmlmarkup.HTMLSanitizer and attachment references are
+    rewritten.
+
+    (For Moin content, a modified version of the
+    MoinMoin.formatter.text_html.Formatter is required, supporting
+    alternatives for the attachment-related methods. This is currently
+    provided in the MoinMessage SendMessage action.)
+
+  Upon processing a message, references to external content are rewritten as
+  references to message parts involving links which invoke an action that can
+  retrieve message part content.
+
+    (Incoming HTML content is parsed using a modified parser and attachment
+    references are rewritten.)
+
+    For Moin content, attachment reference rewriting involves generating
+    special message-related links using another modified HTML formatter.
+
+    (The message-related links are supported by an action which retrieves
+    attachments from stored messages.)
+
+Consider integration with EventAggregator since it already presents aggregated
+data but does not yet support the retrieval of data from feeds.
+
+  Support for iTIP in conjunction with MoinMessage would be useful.
+
+  Support reading mailboxes from IMAP in order to access things like iTIP
+  requests.
+
+Evaluate the difference between cached but transient data provided by
+resources as used in EventAggregator (where the vitality of the resource is
+determined by its continued availability) and captured data provided by
+messages as used by MoinMessage. Feeds could also be treated like inboxes and
+the resources stored in a more permanent fashion.