[Kde-pim] Initializing IndexPolicyAttribute

[Kevin Krammer]

Oh boy, I should check for mails marked as TODO more often ;-)

On Monday, 2011-12-05, Will Stephenson wrote:
> On Sunday 04 December 2011 19:59:56 Kevin Krammer wrote:
> > On Sunday, 2011-12-04, Andras Mantia wrote:
> > > Kevin Krammer wrote:
> > > > Can you elaborate on this? I don't see any special mail collections
> > > > use
> > > > in the patch.
> > > > 
> > > > Do you mean that for whatever reason the collection for the a
> > > > special
> > > > IMAP folder is missing the respective attribute?
> > > 
> > > What I mean is that Inbox,Sent,Trash inside an IMAP resource is not
> > > marked as special collection. You can look at the attributes of the
> > > Inbox folder in akonadiconsole.
> > > So Akonadi::SpecialMailCollections::self()->defaultCollection(
> > > Akonadi::SpecialMailCollections::Inbox ); will return only the main
> > > Inbox
> > > for the local folder.
> > > As I see it is possible to register multiple collection as special
> > > ones, but this is not done atm.
> > 
> > I see.
> > Then we have to find a way to correctly set the special collections
> > attribute.
> > 
> > I guess the IMAP resource could always set the Inbox folder as Inbox, the
> > code handling identities should probably do the others.
> 
> What is the definition of a special collection?  I infer that the local
> folders are there as a a set of collections with roles that are necessary
> to KMail running, but is that all?  I see that Constantin Berzan wrote the
> specialcollections code as part of a GSoC but don't see any high level
> documentation for it.

On the generic collection level a special collection is just marked with an 
attribute containing a type specific identifier.
E.g. for mails such identifiers are "inbox", "outbox" and so on.

The code for the generic handling is in akonadi/specialmailcollections.h/.cpp, 
the one for mail specific stuff is in 
akonadi/kmime/specialmailcollections.h/.cpp

In each case there might be additional job classes.

The maildispatcher sets those attributes when it is the one creating the 
default mail resource, the mail migrator does it when migrating KMail local 
folders.

I guess the question is can the IMAP resource set respective markers on 
certain collections or should a client like KMail do it.
An end user client might have less information (it does't know that a 
collection is on an IMAP server), but it might have configuration telling it 
which folder to use for which purpose (identify setup, etc).

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 190 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20120311/189e6c6b/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/