KFileMetadataConfigurationWidget Exception

Vishesh Handa me at vhanda.in
Wed Jun 26 15:03:00 BST 2013


Hey guys

I know I've already asked my fair share of exceptions, but this one is
just to fix some bugs [1]

With the 4.10 release we moved the KFileMetadataWidget used in Dolphin
to the Nepomuk2::FileMetadataWidget. This all went really smoothly and
the user experience has been much better.

Unfortunately, I did not think about the widget that is used to
configure these settings - KFileMetadataConfigurationWidget. This
widget internally uses the KFileMetadaProvider (aka Strigi and
Nepomuk1).

In order to fix these bugs, I will need to copy the
KFileMetadataWidget from kdelibs/kio to nepomuk-widgets and make it
use the Nepomuk2::FileMetadataProvider.

The class will about a 90% copy of the KFileMetadataConfigWidget.

Non Technical Explanation of the Problem : This configuration widget
looks at the values being shown and shows a list of all the properties
and allows the user to choose which ones should be shown. The old
widget tries to extract the values from strigi and then allows the
user to filter them. As you people know, my indexer works rather
better than Strigi, so quite often more values are shown in the
sidebar and the user has no way to disable them or enable them (in the
case they are filtered by default)

If no one has any objections then I can create the class and make
dolphin use it when it is compiled with Nepomuk. Otherwise we can just
let these bugs stay till 4.12.

--
Vishesh Handa

[1] https://bugs.kde.org/show_bug.cgi?id=316334



More information about the kfm-devel mailing list