Seth Spitzer wrote:
> there is no more nsIMessage. we now use nsIMsgDBHdr.
Yes, I saw that. But why? From a high-level perspective, it's pretty odd
that an email app doesn't support the notion of a "Message" on the
interface level.
It seems like you did that to save an interface, which contained just
accessors to the folder. But IMO, a folder attribute is misplaced in a
"header" interface.
If I wanted to get the msg body, where/how would I do that? If I wanted
to add an interface "MIME part"* and let the source user get the main
mime "part" of the msg, where would I add the accessor? I'd add
|readonly attribute MIMEPart body| to |nsIMessage|.
*E.g. add an abstract interface MIMEPart, from which the interfaces
MIMEBody and MIMEContainer inherit. MIMEContainer can contain MIMEBodies
and other MIMEContainers. MIMEMMixed, MIMEMAlternative and MIMEMRelated
would then inherit from MIMEContainer.
> we already have nsINntpIncomingServer and nsNntpIncomingServer
> nsIMsgNewsFolder and nsMsgNewsFolder, which are the 6.x versions of
> those 4.x classes.
ah.
