Bug 363201 - Zanshin's (0.4) context should match Akonadi's and Korganizer's category
Summary: Zanshin's (0.4) context should match Akonadi's and Korganizer's category
Status: RESOLVED INTENTIONAL
Alias: None
Product: zanshin
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR major
Target Milestone: already done
Assignee: Kevin Ottens
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-18 08:47 UTC by flyos
Modified: 2016-05-18 09:57 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description flyos 2016-05-18 08:47:00 UTC
On previous versions of Zanshin (e.g. 0.2 if memory serves), the "context" concept was synchronised in Akonadi using the "category" concept of Akonadi/Korganizer/CalDAV. 

This is not the case in 0.4. I don't know whether this is voluntary or not. 

My opinion is that there is sufficient overlap between both concepts to justify synchronising context using the category field. Especially since the alternative is to not synchronise context, meaning that Zanshin cannot be used on different devices (which, for a TODO list, means a no-go for many users, including me unfortunately...).
Comment 1 Kevin Ottens 2016-05-18 09:45:17 UTC
Unfortunately can't be addressed. We reached the limitation of the category fields with 0.2 already and abusing them for contexts were creating performance issues. If we want to sync contexts back to categories it would need to be done inside Akonadi, what we would do would be nasty slow workarounds otherwise.
Comment 2 flyos 2016-05-18 09:48:51 UTC
So synchronising "context" using calDAV is not a planned feature then?
Comment 3 Kevin Ottens 2016-05-18 09:56:16 UTC
Not for now indeed. Also, if we aim at fixing it, I think it should be addressed one level below us (in Akonadi).
Comment 4 flyos 2016-05-18 09:57:38 UTC
OK. Thanks