--===============6985714702004040615==
Content-Type: multipart/signed;
  boundary="nextPart4506313.1GYDBG8pBn";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart4506313.1GYDBG8pBn
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On Friday, 2012-02-24, Sebastian Sauer wrote:
> On 02/23/2012 05:59 PM, Boudewijn Rempt wrote:
> > On Thursday 23 February 2012 Feb, Smit Patel wrote:
> >> On Thu, Feb 23, 2012 at 3:36 PM, Sebastian Sauer<mail@dipe.org>  wrote:
> >>> **
> >>> On 02/23/2012 01:31 PM, Smit Patel wrote:
> >>>=20
> >>> Hi everyone,
> >>>=20
> >>> I'd like to propose a GSoC project. Here's the brief description about
> >>> project idea.
> >>> Provide a dbus API that provides an generic interface that can be used
> >>> by external bibliography engines (xbiblio, kbibtex, bibus)
> >>>=20
> >>>=20
> >>> dbus is optional[1] and so would be everything that depends on it. So,
> >>> why dbus? Why not just a plugin? If it should be in another process
> >>> (stability, long-running things, shared among Words-processes, etc)
> >>> then why not for example QLocalServer?
> >>=20
> >> If dbus is not available for windows and OSX then we can rule that out.
> >=20
> > Well, actually dbus _is_ available on both Windows and OSX.
>=20
> 1. re Windows; Not per default what means you need to ship your own
> version of it in the installer. If any app does that then it completely
> voids what dbus is for.

This is mainly a packaging question. I think even on Linux each D-Bus clien=
t=20
has an (indirect) dependency on the D-Bus daemon.

The Windows way of doing this kind of shared dependencies seems to be to=20
include an installer for the shared component which either checks if it has=
 to=20
perform its task or the main installer checks if it has to run the componen=
t=20
one.

> 2. re OSX; my knowledge is a few years old but back then when I hacked
> on dbus making it running at >=3DVista I did not found a single line of
> code that handles OSX. But I can imagine that it changed meanwhile. In
> any case I doubt it's well maintained and it definitively is not straith
> forward to work on that code-base.

My guess would be that it is the exact same code as on Linux, OSX does have=
=20
Unix domain sockets, doesn't it?

Cheers,
Kevin
=2D-=20
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

--nextPart4506313.1GYDBG8pBn
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iD8DBQBPR00nnKMhG6pzZJIRAoF5AKCAbYrT2jUYcJFCFalyXDstu56MRgCdGIVN
ZCK7w+idVwfETPvlgWAxdJY=
=8Zms
-----END PGP SIGNATURE-----

--nextPart4506313.1GYDBG8pBn--

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

_______________________________________________
calligra-devel mailing list
calligra-devel@kde.org
https://mail.kde.org/mailman/listinfo/calligra-devel

--===============6985714702004040615==--