[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-imaging
Subject:    [Kde-imaging] Reg Libkipi attributes() function
From:       "Vardhman Jain" <vardhman () gmail ! com>
Date:       2006-07-17 20:30:03
Message-ID: a5f47ac00607171318w22f45904m1f73112cfc694ac2 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


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

[Attachment #5 (text/html)]

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>




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


[prev in list] [next in list] [prev in thread] [next in thread]