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

List:       calligra-devel
Subject:    Re: GSoC idea
From:       Kevin Krammer <kevin.krammer () gmx ! at>
Date:       2012-02-24 8:41:10
Message-ID: 201202240941.15315.kevin.krammer () gmx ! at
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


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:
> >>> 
> >>> Hi everyone,
> >>> 
> >>> 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)
> >>> 
> >>> 
> >>> 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?
> >> 
> >> If dbus is not available for windows and OSX then we can rule that out.
> > 
> > Well, actually dbus _is_ available on both Windows and OSX.
> 
> 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 client 
has an (indirect) dependency on the D-Bus daemon.

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

> 2. re OSX; my knowledge is a few years old but back then when I hacked
> on dbus making it running at >=Vista 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 
Unix domain sockets, doesn't it?

Cheers,
Kevin
-- 
Kevin Krammer, KDE developer, xdg-utils developer
KDE user support, developer mentoring

["signature.asc" (application/pgp-signature)]

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


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