MoinShare

Changeset

59:3605eb85d56f
2014-03-31 Paul Boddie raw files shortlog changelog graph Added the ongoing "to do" list.
TO_DO.txt (file)
     1.1 --- /dev/null	Thu Jan 01 00:00:00 1970 +0000
     1.2 +++ b/TO_DO.txt	Mon Mar 31 23:56:56 2014 +0200
     1.3 @@ -0,0 +1,63 @@
     1.4 +Provide a means of reviewing and importing keys, most likely in conjunction
     1.5 +with actions provided by MoinMessage. A special parser might be the most
     1.6 +elegant way of displaying such content.
     1.7 +
     1.8 +(Make the macro aggregate feeds from a collection of sources, just like
     1.9 +EventAggregator. This is arguably superior to using URLs directly because the
    1.10 +sources are more easily managed and restrictions can also be placed on URLs
    1.11 +(in case someone deploys a resource that is too large for the wiki, for
    1.12 +example, causing the wiki to become unresponsive or unavailable).)
    1.13 +
    1.14 +(Provide improved containers and navigation for update content.)
    1.15 +
    1.16 +Consider integration with MoinMessage, possibly adding MoinShare compatibility
    1.17 +to posted content in MoinMessage (page regions would have a "moinshare"
    1.18 +attribute), and supporting MoinMessage mailbox inspection (for internal use)
    1.19 +and summaries (for external use) in MoinShare.
    1.20 +
    1.21 +  Provide more efficient (indexed) access to message stores.
    1.22 +
    1.23 +Support packaging of wiki content into MoinMessages such that referenced
    1.24 +resources such as attachments are included in messages and accessible when
    1.25 +messages are displayed by the recipient, potentially without creating the
    1.26 +corresponding attachments in the recipient's system.
    1.27 +
    1.28 +  Message body content is first parsed and attachments identified. References
    1.29 +  to attachments are rewritten in the formatted output, and the attachments
    1.30 +  themselves are added as additional parts to the message.
    1.31 +
    1.32 +    Outgoing HTML content is parsed using a modified version of the
    1.33 +    MoinMoin.support.htmlmarkup.HTMLSanitizer and attachment references are
    1.34 +    rewritten.
    1.35 +
    1.36 +    (For Moin content, a modified version of the
    1.37 +    MoinMoin.formatter.text_html.Formatter is required, supporting
    1.38 +    alternatives for the attachment-related methods. This is currently
    1.39 +    provided in the MoinMessage SendMessage action.)
    1.40 +
    1.41 +  Upon processing a message, references to external content are rewritten as
    1.42 +  references to message parts involving links which invoke an action that can
    1.43 +  retrieve message part content.
    1.44 +
    1.45 +    (Incoming HTML content is parsed using a modified parser and attachment
    1.46 +    references are rewritten.)
    1.47 +
    1.48 +    For Moin content, attachment reference rewriting involves generating
    1.49 +    special message-related links using another modified HTML formatter.
    1.50 +
    1.51 +    (The message-related links are supported by an action which retrieves
    1.52 +    attachments from stored messages.)
    1.53 +
    1.54 +Consider integration with EventAggregator since it already presents aggregated
    1.55 +data but does not yet support the retrieval of data from feeds.
    1.56 +
    1.57 +  Support for iTIP in conjunction with MoinMessage would be useful.
    1.58 +
    1.59 +  Support reading mailboxes from IMAP in order to access things like iTIP
    1.60 +  requests.
    1.61 +
    1.62 +Evaluate the difference between cached but transient data provided by
    1.63 +resources as used in EventAggregator (where the vitality of the resource is
    1.64 +determined by its continued availability) and captured data provided by
    1.65 +messages as used by MoinMessage. Feeds could also be treated like inboxes and
    1.66 +the resources stored in a more permanent fashion.