RFC822 support continued

[Philip Van Hoof <spam pvanhoof be>]

Those who tested the RFC822 support might have noticed discrepanties
lately.

Those have been fixed last night and committed now.

There's a new API in TnyMimePart: get_content_object. That method will
return the RFC822's content object, which is a TnyMimePart (usually a
TnyMsg, actually).

That TnyMimePart can again have n other mime parts, which can again be
RFC822 mime parts with again a content object.

The TnyGtkMsgView knows how to deal with that in a recursive way, yet
makes it easy to implement a TnyMsgView (by inheriting TnyGtkMsgView)
that only has to create a TnyMimePartView for your mime-part data.

You'll usually also create a TnyStream that streams the data from the
mime part to your mime part data viewer.

So:

TnyGtkMsgView implements TnyMsgView and TnyMimePartView and aggregates
one or more TnyMimePartView's (usually decorator style)

TnyMyHTMLMSgView inherits TnyGtkMsgView

TnyGtkMimePartView implements TnyMimePartView

TnyMyHTMLMimePartView inherits TnyGtkMimePartView

TnyMyHYMLStream streams data from a TnyMimePart to a
TnyMyHTMLMimePartView


Use the code, luke.


-- 
Philip Van Hoof, software developer
home: me at pvanhoof dot be
gnome: pvanhoof at gnome dot org
work: vanhoof at x-tend dot be
blog: http://pvanhoof.be/blog