From kde-devel Tue Oct 30 21:54:52 2012 From: Vishesh Handa Date: Tue, 30 Oct 2012 21:54:52 +0000 To: kde-devel Subject: Nepomuk Tags kioslave - Please Review Message-Id: X-MARC-Message: https://marc.info/?l=kde-devel&m=135163343600548 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--===============3138288452091694385==" --===============3138288452091694385== Content-Type: multipart/alternative; boundary=f46d0447a09102da8b04cd4dab98 --f46d0447a09102da8b04cd4dab98 Content-Type: text/plain; charset=ISO-8859-1 Hey everyone I recently wrote a 'tags' kio slave, which allows one to browse nepomuk tags, and the files containing those tags. It is currently in kde-runtime/nepomuk/kioslaves/tags/, in the nepomuk/tagsKioSlave branch. Could someone please review it? I would like to merge it before the hard freeze. It has a custom url naming scheme - *tags:/tag1* => All the files tagged with 'tag1' and additional tags which can be used filter the results. *tags:/tag1/file_url_of_the_file* => This is the url of the file. Ideally I would just use the normal url of the file, but we need to have the 'tags' protocol, so that we can handle delete events. We don't want to delete the file, rather just remove that tag. This file_url_of_the_file is added as the UDS_NAME, and results in the search results looking slightly ugly if the file properties are checked. Is there a better way of handling this? *tags:/tag1/tag2 *=> Files tagged with both tag1 and tag2 Known problems - * You can move files into a tag folder thereby effectively loosing them * No automatic updates * It shows the tags with the nepomuk icon. We need a better 'tags' icon. -- Vishesh Handa --f46d0447a09102da8b04cd4dab98 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Hey everyone

I recently wrote a 'tags' kio slave, which allo= ws one to browse nepomuk tags, and the files containing those tags. It is c= urrently in kde-runtime/nepomuk/kioslaves/tags/, in the nepomuk/tagsKioSlav= e branch. Could someone please review it? I would like to merge it before t= he hard freeze.

It has a custom url naming scheme -

tags:/tag1 =3D> Al= l the files tagged with 'tag1' and additional tags which can be use= d filter the results.

tags:/tag1/file_url_of_the_file =3D>= This is the url of the file. Ideally I would just use the normal url of th= e file, but we need to have the 'tags' protocol, so that we can han= dle delete events. We don't want to delete the file, rather just remove= that tag.

This file_url_of_the_file is added as the UDS_NAME, and results in the = search results looking slightly ugly if the file properties are checked. Is= there a better way of handling this?
=A0
tags:/tag1/tag2 =3D&= gt; Files tagged with both tag1 and tag2

Known problems -
* You can move files into a tag folder thereby effe= ctively loosing them
* No automatic updates
* It shows the tags with = the nepomuk icon. We need a better 'tags' icon.


--
Vishesh Handa

--f46d0447a09102da8b04cd4dab98-- --===============3138288452091694385== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe << --===============3138288452091694385==--