[Kde-pim] How can we improve Akonadi documentation?

[Kevin Krammer]

Hi Greg,

On Wednesday, 2010-09-15, Gregory Schlomoff wrote:
> Hello Stephen,
> 
> I would also strongly encourage you to help write the docs you are missing
> 
> > by asking the questions and the rest of us giving the answers. Many of us
> > are too deep into it that we don't see the high-level overview issues as
> > you
> > say.
> > 
> > 
> > I think asking it would help if people like yourself would ask the
> > highlevel
> > questions here or on IRC and maintain a list of answers or a getting
> > started
> > page. In many cases we don't even know the questions.
> 
> Sure. As soon as I get myself started (ie: as soon as I'm able to create a
> collection in Akonadi, which isn't the case, yet), I'll submit a piece of
> "getting started" doc for reviewal to this mailing list.

Awesome!

> > Also, please don't spend hours confused about something :). Ask here or
> > on irc within an hour instead of being confused. There's a lot of
> > difficult things in the API because it's all asynchronous, a bit
> > abstract, there's several channels of communication like imap/dbus,
> > heavily relies on platformy/funny things like mimetypes and desktop
> > files etc, and it can be hard to know where standards end and extensions
> > begin. Everyone hits a few brick walls at the start.
> 
> Yes. I found people on this mailing list and on IRC to be incredibly
> supporting. I guess the main problem at the moment is that as we do all our
> development on windows, we aren't sure yet if the issues we have come from
> building / configuration problems on this platform, or just lack of
> understanding of the Akonadi API. So it's not easy to ask, because we feel
> like we are a corner case :)

I can understand that this is awkward but since none of us uses Windows as the 
main development plaform, any feedback from that side is extremely valuable.

> For example, running the sample code from CollectionCreateJob, we get back
> a "Cannot create top-level collection" error message. Is that normal
> behaviour, or is our Akonadi setup incorrect?

Sorry, again a matter of an example gone wrong.
Only resources are allowed to create top level collections, i.e. so each 
subtree is "owned" by a resource.

Hmm, I guess the easiest way is to add a maildir resource and create 
collections below its toplevel collection. The resource will then create 
directories for each on disk.

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/20100915/41b23291/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/