On Tuesday, 2013-11-19, 09:08:13, Aaron J. Seigo wrote:
On Monday, November 18, 2013 23:42:45 John Layt wrote:
On 18 November 2013 20:53, David Edmundson da...@davidedmundson.co.uk
There are 3 data engines and 2 runners which link to kdepimlibs. The
i don’t think DataEngines are well
On Monday, November 18, 2013 23:42:45 John Layt wrote:
On 18 November 2013 20:53, David Edmundson da...@davidedmundson.co.uk
There are 3 data engines and 2 runners which link to kdepimlibs. The
i don’t think DataEngines are well suited to the kind of data kdepimlibs
provides. what would be
On Monday 18 November 2013, John Layt wrote:
dataengine in Plasma 1)
- various runners
There are 3 data engines and 2 runners which link to kdepimlibs. The
Akonadi and RSS data engines are not used anywhere in the kde repos,
rss is used in kdeplasma-addons
Cheers,
Marco Martin
On Tuesday, November 19, 2013 09:08:13 Aaron J. Seigo wrote:
The idea being that if the user didn't configure any calendars on
first run, then we would know to disable events and so never wake
Akonadi up.
That would be fantastic. If there was a simple library call that could tell
what
On 19 November 2013 10:51, Marco Martin notm...@gmail.com wrote:
On Monday 18 November 2013, John Layt wrote:
dataengine in Plasma 1)
- various runners
There are 3 data engines and 2 runners which link to kdepimlibs. The
Akonadi and RSS data engines are not used anywhere in the kde
To plasma-devel, CC'ing KDE PIM.
Preparing for Plasma 2:
- KDE PIM is currently used in kde-workspace for:
- an Akonadi dataengine
- showing events in the calendar (which was C++ without the
dataengine in Plasma 1)
- various runners
- Tentative timeline for PIM:
- Plan is to
On 18 November 2013 20:53, David Edmundson da...@davidedmundson.co.uk wrote:
To plasma-devel, CC'ing KDE PIM.
A few small clarifications, for more details see some initial
documentation at http://community.kde.org/Frameworks/Epics/kdepimlibs
Preparing for Plasma 2:
- KDE PIM is currently
