--===============1921729836==
Content-Type: multipart/alternative; 
	boundary="----=_Part_82293_29819975.1153167483750"

------=_Part_82293_29819975.1153167483750
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi folks,
       I have started breaking libkipi binary compatibility (:)). Just added
the HostSupportsTags feature in the enum list of features. Now Applications
can support this feature.
I would like to discuss some implementation issues here, which will come
during further feature addition to this attributes() set of functions.

The host application are expected to return a QMap <QString, QVariant> for
the attributes() function.
The map contents (key, value) need to be standardized so that plugins can
take out some attribute from the map using a well defined key. For the tags
feature I have used the String "tags" as the key.

I would look forward for other developers comment regarding this sort of
standardization. Where should guidlines regarding this be kept noted. I will
update the inline documentation.  For the time being I hope that should be
sufficient.


Vardhman
-- 
Blogs: http://vardhman.blogspot.com

------=_Part_82293_29819975.1153167483750
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

Hi folks,<br>&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; I have started breaking libkipi binary compatibility (:)). Just added the HostSupportsTags feature in the enum list of features. Now Applications can support this feature. <br>I would like to discuss some implementation issues here, which will come during further feature addition to this attributes() set of functions.
<br><br>The host application are expected to return a QMap &lt;QString, QVariant&gt; for the attributes() function.<br>The map contents (key, value) need to be standardized so that plugins can take out some attribute from the map using a well defined key. For the tags feature I have used the String &quot;tags&quot; as the key. 
<br><br>I would look forward for other developers comment regarding this sort of standardization. Where should guidlines regarding this be kept noted. I will update the inline documentation.&nbsp; For the time being I hope that should be sufficient.
<br clear="all"><br><br>Vardhman<br>-- <br>Blogs: <a href="http://vardhman.blogspot.com">http://vardhman.blogspot.com</a><br>

------=_Part_82293_29819975.1153167483750--

--===============1921729836==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
Kde-imaging mailing list
Kde-imaging@kde.org
https://mail.kde.org/mailman/listinfo/kde-imaging

--===============1921729836==--