Thomas McGuire
94aeda18dd
Remove the Tracker integration from the Akonadi port of KMail.
...
It needs to be ported to Akonadi anyway, but the more important reason is that
the Tracker integration can and should now be done with a seperate application,
which the design of Akonadi now allows.
This will only affect the Akonadi-based KMail, which is expected to be released
with KMail 2.
CCMAIL: philip@codeminded.be
svn path=/branches/work/akonadi-ports/kdepim/; revision=1066789
16 years ago
Laurent Montel
e8cc162ec7
kmfolder--
...
svn path=/branches/work/akonadi-ports/kdepim/; revision=1055005
17 years ago
Bertjan Broeksema
312e5a993d
Replace all usage of KMime::Message* with KMime::Message::Ptr and use
...
.get() on the Ptr on places where a KMime::Content* is expected.
svn path=/branches/work/akonadi-ports/kdepim/; revision=1050892
17 years ago
Laurent Montel
66efdbf6a9
Remove not necessary function
...
svn path=/branches/work/akonadi-ports/kdepim/; revision=1040585
17 years ago
Andras Mantia
7e3982c776
Trying to get rid of the rest of KMMessage and KMMsgBase usage and port it to KMime. Mostly only the interfaces are ported, the code is commented out, although in many cases the code is obsoleted by the akonadi resources. Also get rid of the different folder classes, as those are transparent, accessible via akonadi.
...
svn path=/branches/work/akonadi-ports/kdepim/; revision=1037186
17 years ago
Thomas McGuire
3340bdb187
Support the metadata-over-DBus API, as used by e.g. Tracker.
...
Patch by Philip Van Hoof, thanks!
http://reviewboard.kde.org/r/168/
BUG: 185331
svn path=/trunk/KDE/kdepim/; revision=934376
17 years ago