1 Provide a means of reviewing and importing keys, most likely in conjunction
2 with actions provided by MoinMessage. A special parser might be the most
3 elegant way of displaying such content.
4
5 (Make the macro aggregate feeds from a collection of sources, just like
6 EventAggregator. This is arguably superior to using URLs directly because the
7 sources are more easily managed and restrictions can also be placed on URLs
8 (in case someone deploys a resource that is too large for the wiki, for
9 example, causing the wiki to become unresponsive or unavailable).)
10
11 (Provide improved containers and navigation for update content.)
12
13 Consider integration with MoinMessage, possibly adding MoinShare compatibility
14 to posted content in MoinMessage (page regions would have a "moinshare"
15 attribute), and supporting MoinMessage mailbox inspection (for internal use)
16 and summaries (for external use) in MoinShare.
17
18 Provide more efficient (indexed) access to message stores.
19
20 Support packaging of wiki content into MoinMessages such that referenced
21 resources such as attachments are included in messages and accessible when
22 messages are displayed by the recipient, potentially without creating the
23 corresponding attachments in the recipient's system.
24
25 Message body content is first parsed and attachments identified. References
26 to attachments are rewritten in the formatted output, and the attachments
27 themselves are added as additional parts to the message.
28
29 Outgoing HTML content is parsed using a modified version of the
30 MoinMoin.support.htmlmarkup.HTMLSanitizer and attachment references are
31 rewritten.
32
33 (For Moin content, a modified version of the
34 MoinMoin.formatter.text_html.Formatter is required, supporting
35 alternatives for the attachment-related methods. This is currently
36 provided in the MoinMessage SendMessage action.)
37
38 Upon processing a message, references to external content are rewritten as
39 references to message parts involving links which invoke an action that can
40 retrieve message part content.
41
42 (Incoming HTML content is parsed using a modified parser and attachment
43 references are rewritten.)
44
45 For Moin content, attachment reference rewriting involves generating
46 special message-related links using another modified HTML formatter.
47
48 (The message-related links are supported by an action which retrieves
49 attachments from stored messages.)
50
51 Consider integration with EventAggregator since it already presents aggregated
52 data but does not yet support the retrieval of data from feeds.
53
54 Support for iTIP in conjunction with MoinMessage would be useful.
55
56 Support reading mailboxes from IMAP in order to access things like iTIP
57 requests.
58
59 Evaluate the difference between cached but transient data provided by
60 resources as used in EventAggregator (where the vitality of the resource is
61 determined by its continued availability) and captured data provided by
62 messages as used by MoinMessage. Feeds could also be treated like inboxes and
63 the resources stored in a more permanent fashion.