On Sun, 23 Mar 2003, Garold (Gary) L. Johnson wrote: (01)
> * Use wiki text in plain text messages.
> * Relax the wiki syntax to allow lists to be indented for appearance. Manage
> multiple line paragraphs in addition to the current line == paragraph model.
> * Process the purple numbers before posting the emails to the list.
> * For any situation in which email headers are inadequate, add elements to
> the wiki format to handle better subjects, better reply to, whatever.
> * Possibly support a body element to provide a subject for the email even
> though it is still in a thread, as I have done here.
> * Support a shorter URL for messages to clean up quoting (this is for
> appearance only). (02)
Processing incoming messages as WikiText and injecting purple
numbers before distribution is possible with the current
PurpleWiki parser (with some work), but presents some questions: (03)
- What should the output format be (wikitext, HTML, something
else, user's choice)?
- How to deal with quoted text (like your text above)?
- How to present output appropriate for mail readers (wikitext
output is not line wrapped)? (04)
There are, at the moment, a lot of interesting PurpleWiki changes
floating around that are not yet aggregated back to the main
source. This is mostly from lack of organization but also lack of
feedback. Some things that are floating around: (05)
- A PurpleWiki plugin for the movable type blog software
- Node based (instead of page based) content storage (will
eventually allow for transclusion, structured access to
parts of documents, and short URLs)
- Metadata to facilitate using the parser for "document"
authoring. That is, using it for writing papers, not just wiki
pages or email messages.
- Support for domain unique node ids (rather than page unique) (06)
More info: (07)
http://purplewiki.blueoxen.net/forums/devel/ (08)
--
Chris Dent
cdent@blueoxen.org (09)
--
This message is archived at: (010)
http://collab.blueoxen.net/forums/cgi-bin/mesg.cgi?a=yak&i=Pine.LNX.4.30.0303261844240.17792-100000@hot.burningchrome.com (011)
|