On Wed, 2008-07-02 at 20:44 -0500, Srichand Pendyala wrote a reply to a
message on the java-gnome-developer mailing list; I have sent my reply
and invited follow ups to java-gnome-hackers:
> Just a thought:
>
> The gnome-keyring API is still in flux, as is mentioned at
> http://live.gnome.org/GnomeKeyring/StoringPasswords . Although the API
> is nice and small (3 meaty methods!)
From a first glance at the API pages, it seems that the real problem
would be working out how to handle all the async callbacks. We don't
have a terribly good mechanism for that at the moment
[and have only done it manually once - the hack that made
TreeModelFilter's setVisibleCallback() work by turning it into a signal]
so perhaps it's time that we worked that out in the architecture and
then extruded that design via the code generator.
> and could probably be re-written to
> match the upstream API as and when it changes,
Sure.
> would it make sense to
> hold off binding it until its a little more mature?
It's probably hardening. The degree of arterial sclerosis that occurs
once a library has been released out into the wilds is fairly insane.
While I have no objection at all to binding against unstable libraries,
the changing signature problem could cause us to have link failures if
the underlying library in question is iterating too fast.
{shrug}
That's life in the big city; and as I'm not into having java-gnome
support ancient versions of underlying libraries but rather have
stipulated the dependency as latest releases (ie, GTK 2.12, Cairo 1.6.4,
and for that matter, GNOME 2.22, etc) we shouldn't have too much problem
when the time comes.
AfC
Sydney
|
