[no subject]

I think this can easily be achieved in GEmblemedIcon by allowing it to
have more than
one emblem, and associate some extra information with it. Like

g_emblemed_icon_add_emblem (GEmblemedIcon *icon,
                                                     GIcon
     *emblem,
                                                     const char
   *origin)

If there is more extra data for emblems than just the origin, then we
could still introduce
a GEmblem class, but I'm sure that is really necessary (you haven't
said what  additional
properties your GEmblem provides).

What I'm not convinced about is adding an extra interface for
'emblemable' icons and
implementing it multiple times for GFileIcon, GThemedIcon, etc. I just
don't see the benefit.
Code that handles GIcon implementations (the serialization code in
gvfs, and the rendering
code in gtk) will have to learn about emblems anyway. I don't foresee
tons of apps
implementing their own GIcon handling code. At least thats not the intention.


Matthias