[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: Nepomuk as hard dependency in future?
From:       Mark Kretschmann <kretschmann () kde ! org>
Date:       2009-12-02 8:32:40
Message-ID: e93871060912020032n2230e2f3p7621bfacdfca9824 () mail ! gmail ! com
[Download RAW message or body]

On Sat, Oct 17, 2009 at 11:19 AM, Peter Penz <peter.penz@gmx.at> wrote:
> currently Nepomuk is an optional dependency. There are widgets that have
> extended functionality by using Nepomuk, but also can live without Nepomuk (e.
> g. Dolphin has a MetaDataWidget - without Nepomuk just less meta data are
> shown).
>
> One problem is that this requires a lot of #ifdef HAVE_NEPOMUK code. While
> this is just a nasty detail in the implementation, it gets to a real problem
> especially in header files for kdelibs, that use a Nepomuk interface like
> this:
>
> class MetaDataWidget : ...
> {
>    ...
>    public:
>        QList<Nepomuk::Tag> tags() const;
> };
>
> Using #ifdef HAVE_NEPOMUK code is no option as this would be BIC. If Nepomuk
> would be a hard dependency (but for sure can be turned off during runtime as
> always), this problem would be a no-brainer (-> tags() would just return an
> empty list if Nepomuk is turned off).
>
> Is there a chance that Nepomuk gets a hard dependency for KDE 4.4 or KDE 4.5

Personally I'm all for it. I think it's a good idea, and it might help
Nepomuk's acceptance and usage.

-- 
Mark Kretschmann
Amarok Developer
Fellow of the Free Software Foundation Europe
www.kde.org - amarok.kde.org - www.fsfe.org

[prev in list] [next in list] [prev in thread] [next in thread]