todo

1. UI, Part 1: button and menuentry for creation of annotations
2. Creation of annotations (adding headers to compose code)
   Files to change:
   1. nsMsgHeaderMasks.h
   2. nsIMsgCompFields.idl
   3. nsMsgCompFields.h
   4. nsMsgCompFields.cpp
3. (Re)Storing of annotations (overwriting the existing one. The current compose code just stores in draft folder.)
   • Add new nsMsgDeliverMode to nsMsgComposeAndSend::CreateAndSendMessage.
4. Let the message store know the existance of annotations (create/store connections between annotations and messages)
   • Information from In-Reply-To: (and maybe also Reference:) field
5. UI, Part 2: showing, opening and deletion of existing annotation
   • Change icon in iconbar and/or
   • Create large icon inside message (like "Signed")
     • Rendering (Either place of "Signed" icon or beside of it)
6. Change the copying code to copy annotations, too.
7. UI, Part 3: Message Folder
   • Should the annotation be an entry in the folder?
     • I think: No, but not sure.
   • Icon in folder?
     • I think: No, but not sure.
8. Hope, that I didn't misunderstand or miss something, especially in (4) or (6)

• I won't implement the general scope annotation, but keep it in mind

Done

Changed Files

1. UI 1 (completed)
   1. messenger.xul
   2. locale/en-US/messenger.dtd
   3. widgetglue.js
   4. commandglue.js
2. Create
   1. nsIMsgCompose.idl
   2. nsMsgCompose.cpp: I18N
   3. allxpstr.h (MK_MSG_ANNOTATION_RECIPIENT): Name
3. Storage

The way to a message

• 1. messenger.xul
  2. widgetglue.js - MsgReplyMessage
  3. commandglue.js - ComposeMessage
  4. nsMsgComposeService::OpenComposeWindow
  5. ?...?
  6. MsgComposeCommands.js - ComposeStartup
  7. nsMsgComposeService::InitCompose
  8. nsMsgCompose::CreateMessage
• 1. nsMsgComposeAndSend::CreateAndSendMessage
  2. nsMsgComposeAndSend::Init
  3. nsMsgComposeAndSend::InitCompositionFields
  4. (nsMsgComposeAndSend::GetBodyFromEditor
  5. nsEditorShell::GetContentsAs
  6. One of nsEditor::OutputToString's children, at the moment only nsHTMLEditor::OutputToString
  7. ...)
  8. nsMsgComposeAndSend::SnarfAndCopyBody
  9. ...

Problems

• Don't know, when/where the flags are set. See MarkAttachment.

• The JavaScript-function ComposeMessagens and it's callers don't use the the enums. This will break as soon as I add a MSGCOMP_Annotation after MSGCOMP_ReplyAll, for example.
• Why do nsMsgCopy::Get*Folder exist?
• Where is nsIMessage::GetMsgFolder() implemented?
• Why is nsMsgCompFields.h so wierd?

Definitions

• Special headers of annotation-message
  • New field X-Mozilla-Annotation:
    • 0 = No annotation
    • 1 = Message annotation
    • 2 = General scope annotation
  • Connection through normal reply (no special treatment)
  • To: field has special value (like Annotation <annotation@mozilla.org>)
    • Not relyable, only for user of non-Moz-MUA
  • Maybe additional scope info