kwallet and QCA

[Aaron J. Seigo]

On Tuesday 03 June 2008, nf2 wrote:
> Actually - as i'm almost done with KIO-GIOBridge - my plan is to start
> coding such "thin" Qt/C++ bindings to several GLib based infrastructure
> libraries (GIO, keyring,...) soon - as working name i thought of
> "libkommodity"

if you are seriously hoping for buy in on this i would suggest explaining for 
each one why the particular library should be used, what the real world 
benefits would be, etc.

> I might disagree with Kevin here a bit - i don't think that trying to
> standardize D-Bus interfaces (the DAPI approach) and having multiple
> client and service implementations gets us any further.

it actualy gets us a lot further in that it would enable applications to use 
the desktop facilities of whatever the user is logged into. this is an obvious 
improvement over the current situation and very neatly covers the vast 
majority of cases.

(as such i'm not sure statements like these help your cause/credibility much 
=/)

what it doesn't get us is the ability to use App A on Desktop X, then switch 
into Desktop Y and still have the data stored in the wallet while in Desktop X 
still there. sharing an implementation would.

Kevin's probably quite right that standardizing the d-bus interface would get 
us there much faster. most importantly, it allows us to adjust the client side 
right now and then we can worry about the server side afterwards as a separate 
implementation detail.

we'd still need to write the API for the Qt/KDE side anyways, or adapt what is 
already there. so it's really not work lost, but work that needs to be done 
anyways.

> If libraries
> developed by GNOME fit our needs - lets just use them.

that can only be determined by defining our needs and then the capabilities of 
the library in question. while there are places we can share implementations, 
there are places we probably want something better than what is available.

additionally, we'd need to be able to trust the forward development of said 
libraries with regards to our needs.

sharing implementations really means a lot more than just writing wrappers 
around other people's libraries ad infinitum. it takes working together to 
ensure needs are known and addressed.

-- 
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 194 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20080603/80507833/attachment.sig>