On Tuesday 06 February 2007 14:07, Bruce D'Arcus wrote: > > Thomas Zander wrote: > >> 2) Create a technology specific RPC API. > >> In this case I'd say the different office suites can provide a dbus > >> [1] API > >> that provides an interface that is specifically geared towards > >> bibliographic > >> software. While still being generic enough that different > >> bibliographic tools > >> can all use it. > > > > As the start was "Zotero for Word" we surely must think about a > > solution > > that works with Word also. Having a single API for all would be great. > > > > I must confess that I'm not aware of the general availability (and > > implementation quality) of dbus on the different platforms supported by > > OOo. I assume that it works quite well on Linux, but what about > > Solaris, > > Windows and (hopefully soon!) Mac OSX? The Windows port of dbus seems > > to > > be "in progress", not done yet. Doesn't look like a viable option to > > me.
The dbus port on other platforms actually works pretty well and is being actively developed with a very clear goal in mind by various core-KDE people. To make dbus be a true cross-platform solution. I'm not upto-date on the latest development, but if its not yet there, I'm confident it will be soon. In other words; dbus is the newest technology on the block that is also the first that is fully open and interoperable. And, most important, in active development. I do think its the best technology for the job. Soap for example is a technology thats very old and has soo many different implementations you can't honestly call it interoperable. -- Thomas Zander
pgp5YaCXxpYS5.pgp
Description: PGP signature
