[Kde-pim] Re: Free-busy integration in KDEPIM - Osnabrück outcome

[Thomas McGuire]

Hi Grégory,

I had a quick look at some parts. I think they look quite good, although Brad 
should have a look to see if it fits his OpenChange usecase. And someone from 
the KOrganizer team as well.
Thanks for the great work.

For the kdepimlibs parts, they look quite ok, maybe they should be in the 
kcal/ subdir of akonadi though? (yeah we missed that for the transport 
resource...)
Can lastCacheUpdate() not use a KDateTime instead of a QString? What format is 
the email address in, something like "bla at foo.com" or are display names 
allowed as well? That should be documented. Same with freeBusyRetrieved(), I 
have no idea what format "@param freeBusy The free-busy data." is in.
Maybe instead of using a boolean to indicate an error, have a QString for the 
user-visible error message somewhere, that KOrganizer could display?

I didn't look at FreeBusyManager or the Resource.

Regards,
Thomas

On Saturday, March 19, 2011 01:34:57 PM Grégory Oestreicher wrote:
> I've finally made public the work I started in the KDEPIM meeting in
> Osnabrück pertaining to the free-busy integration (yeah, it was about
> time).
> 
> - git://anongit.kde.org/clones/kdepim/goestreicher/freebusy-provider
>   This extends the FreeBusyManager in two ways. One is to add the new F/B
>   retrieval mechanism before the "groupware way", which was based on an
>   URL build with the email address to get F/B info for. Now all resources
>   that have the 'FreeBusyProvider' capability are queried. If none answers
>   positively (for short, once again comments provide more information)
>   then there is a fallback on the groupware mechanism.
>   The other extension is to add a new method to retrieve F/B info for
>   a limited period.
> 
> -
> git://anongit.kde.org/clones/kdepim-runtime/goestreicher/freebusy-provider
> This is the PoC of the free-busy retrieval, using the DAV groupware
> resource. You need a CalDav server obviously, and a compliant one. I'm not
> sure that this will work with Google calendar for example. I've
> successfully tested this with Davical and I'm eager to hear successes or
> failures with other implementations.
> 
> All of this will be submitted to reviewboard after KDEPIM 4.6 is released,
> as kdepimlibs has been changed, and hopefully should find its way into
> KDEPIM 4.7. Feel free to comment before the official review :)
> 
> Finally I'd like to thank all the people that were here in Osnabrück.
> KDEPIM is really a great community to get involved into, and this meeting
> really boosted my involvment, or at least the will to involve myself more
> (talk about free time). You guys rock.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20110403/15bb2e4e/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/