Home > Krita > Why Nepomuk in Krita . . .

Why Nepomuk in Krita . . .

Hi KDE Folks,

      In my previous post, I mentioned about the implementation of Nepomuk and XML backends for Krita. Many asked me what’s the use of nepomuk or XML, which one is best and so on. I want to clear those doubts in this post . . .

     Coming to XML – We started implemented tagging in XML to get the opportunity of exchanging resources between Gimp and Krita. And later we moved on to nepomuk, so that with nepomuk we have the following advantages

  • Add and delete tags using kde apps containing nepomuk feature – these changes will be effected once you restart krita application.
  • Search resources by using tags in kde apps

 The following picture is adding tags for the resources in dolphin

     But the problem with nepomuk works only kde libraries, we can’t use this feature in Gnome environment. Xml can be used in both environments but not able to share tags with other kde apps.

    On the whole, both have its own advantages and disadvantages. I completed the implementation part of both backends and also sent for review to merge the code into the master. In few days, the nepomuk feature will be available to you . . . 😀

Advertisements
Categories: Krita
  1. m4db0b
    August 6, 2011 at 10:11 pm

    I admit I’ve not verified your code, but I think Nepomuk’s tags are not so different than Tracker’s tags (they use the same ontology, if I well remember that part have not diverted). API is different, but Tracker already has a Qt binding.
    It is a shame Xesam project for semantic backends interoperability has been killed, so you would have to provide your own abstraction layer for the two APIs, but at least it is possible to provide a Gnome-compatible tagging system in Krita.

  2. maninalift
    August 8, 2011 at 12:21 am

    Small UI suggestion: it would be nice if the “create new tag” input box also filtered the list of tags

  3. gonzalo
    August 8, 2011 at 12:44 am

    The first thing that neopomuk requires is a two sentence explanation that any intelligent person can understand. Second is a better name. Third is interoperability with other projects trying to achieve the same thing. This last part is the hardest, yet it is the one where most work should be done.

    Thanks for all the good work.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: