[Kde-pim] Setting Akonadi agents' mime types

[Volker Krause]

On Friday 11 September 2009 10:24:24 David Jarvie wrote:
> On Fri, September 11, 2009 8:09 am, Volker Krause wrote:
> > On Friday 11 September 2009 01:38:40 David Jarvie wrote:
> >> Why doesn't the Collection show just a single mime type in
> >> AkonadiConsole?
> >> - is it necessary to do something else to save the new setting?
> >
> > I'm wondering why you try to modify the content mimetype from within the
> > application at all. Usually it's something only the resource should do,
> > as it
> > is the only thing that knows what types it can handle. If possible any
> > resource-specific knowledge should be avoided in the application, it will
> > fail once you exchange the resources at some point.
>
> It's only when creating a new collection that I want to specify a
> particular mime type. After any alarms have been added, the resource knows
> what mime type it is from the alarm type. Or do you think that it would be
> better to define separate resource types?

What are those different types anyway? That might help understanding the 
scenario here :)

There are ways to define separate resource types for the same resource 
executable btw, using separate desktop files with different resource 
identifiers but pointing to the same executable. The resource itself can then 
check its identfier to figure out which one it is supposed to be. Not really 
nice, but still better than writing for different resources.

regards
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20090911/7417b341/attachment.sig>
-------------- next part --------------
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/