{
  "version": "https://jsonfeed.org/version/1.1",
  "title": "chem-bla-ics",
  "description": "Chemblaics (pronounced chem-bla-ics) is the science that uses open science and computers to solve problems in chemistry, biochemistry and related fields.",
  "home_page_url": "https://chem-bla-ics.linkedchemistry.info/",
  "feed_url": "https://chem-bla-ics.linkedchemistry.info/2006/06/25/kde4-keyword-support-mockups.json",
  "icon": "https://chem-bla-ics.linkedchemistry.info/assets/images/chem-bla-ics_logo.png",
  "language": "en",
  "authors": [
    {
      "name": "Egon Willighagen",
      "url": "https://orcid.org/0000-0001-7542-0286",
      "_orcid": "0000-0001-7542-0286"
    }
  ],
  "items": [

    {
      "id": "https://doi.org/10.59350/62e2c-ycj21",
      "url": "https://chem-bla-ics.linkedchemistry.info/2006/06/25/kde4-keyword-support-mockups.html",
      "title": "KDE4 keyword support mockups",
      "content_html": "<p>In reply to interesting comments to <a href=\"https://chem-bla-ics.linkedchemistry.info/2006/06/20/strigi-gets-kfile-plugin-support.html\">my previous blog <i class=\"fa-solid fa-recycle fa-xs\"></i></a>\non <a href=\"http://www.vandenoever.info/software/strigi/\">Strigi</a> and xAttr support in <a href=\"http://www.kde.org/\">KDE</a>4, I would like to suggest\nthe following mockups, which I would find very useful. The deal with the ability to store keywords, for example, not but necessarily\nusing xAttr. I have no idea on how to implement these mockups, so any help or pointers are appreciated.</p>\n\n<p>The first plot is an example of how these keyword markup could be used in KDE, other than searching itself. When showing the properties\nof a directory in KDE, it would show an overview of hottest keywords for that directory, such as used on social bookmark website like\n<a href=\"http://technorati.com/\">Technorati</a> too:</p>\n\n<p><img src=\"/assets/images/kfileXAttrSupport.png\" alt=\"\" /></p>\n\n<p>This example shows that the keyword ‘Strigi’ was used much inside the index_files directory (they are not just the keywords given for\nthat directory, but a summary of the directory content!). Now, these keywords could be stored as xAttr, but in a database too. The\nfirst requires a filesystem that supports xAttr, while the second requires a database daemon to be running. However, for speed\nperformance reasons this would be required anyway. Strigi indexes xAttr now (post 0.3.0 release), and basically allows both.</p>\n\n<p>Independent of the chosen/prefered way to store keywords, these keywords can be edited from the Properties dialog:</p>\n\n<p><img src=\"/assets/images/kfileXAttrSupport2.png\" alt=\"\" /></p>\n\n<p>Now comes the tricky part: though I would like to add this to KDE, I do not have the C++/KDE experience to actually do this.\nI’m already happy that I was able to extend the Strigi with support for KDE’s kfile architecture. Yes, the Strigi version in\nSVN will index all metadata extractable with kfile plugins installed on the KDE installation.</p>",
      "summary": "In reply to interesting comments to my previous blog on Strigi and xAttr support in KDE4, I would like to suggest the following mockups, which I would find very useful. The deal with the ability to store keywords, for example, not but necessarily using xAttr. I have no idea on how to implement these mockups, so any help or pointers are appreciated.",
      "image": "https://chem-bla-ics.linkedchemistry.info/assets/images/kfileXAttrSupport2.png",
      "date_published": "2006-06-25T00:00:00+00:00",
      "date_modified": "2024-12-29T00:00:00+00:00",
      "tags": ["kde","strigi","technorati"],
      
      
      
      
      
      
        "authors": [ { "name": "Egon Willighagen", "url": "https://orcid.org/0000-0001-7542-0286" } ]
      
    }

  ]
}