On Thursday, December 08, 2011 17:12:05 Kevin Kofler wrote:
Aaron J. Seigo wrote:
yes, i skipped the details. done properly it should be linking
libkactivities. this is an acceptable short term work-around given it's
in a branch, while doing it right requires the modularization to be
Aaron J. Seigo wrote:
yes, i skipped the details. done properly it should be linking
libkactivities. this is an acceptable short term work-around given it's in
a branch, while doing it right requires the modularization to be
complete for at least libkactivities dependencies.
Or it'd require
Aaron J. Seigo wrote:
yes, i skipped the details. done properly it should be linking
libkactivities. this is an acceptable short term work-around given it's in
a branch, while doing it right requires the modularization to be
complete for at least libkactivities dependencies.
Or it'd require
On Thursday 08 December 2011 17.12.05 Kevin Kofler wrote:
Aaron J. Seigo wrote:
yes, i skipped the details. done properly it should be linking
libkactivities. this is an acceptable short term work-around given it's
in a branch, while doing it right requires the modularization to be
Cool :)
When we are at it:
Apart from various changes in libkactivities, there is now a branch of
kdelibs called ivan/kparts-activities which provides all kparts-based
applications the ability to report resource events (document
open/close...) to the activity manager.
Since kdelibs are frozen,
On 5 December 2011 09:54, Aaron J. Seigo ase...@kde.org wrote:
On Monday, December 5, 2011 09:31:49 Ivan =?utf-8?B?xIx1a2nEhw==?= wrote:
Since kdelibs are frozen, this will never go into master, but will
need to wait for kf5.
to expand on why this is a bit more: it requires libkactivities,
On Monday, December 5, 2011 10:12:04 Ivan =?utf-8?B?xIx1a2nEhw==?= wrote:
On 5 December 2011 09:54, Aaron J. Seigo ase...@kde.org wrote:
On Monday, December 5, 2011 09:31:49 Ivan =?utf-8?B?xIx1a2nEhw==?= wrote:
Since kdelibs are frozen, this will never go into master, but will
need to wait