On Wed, 2008-04-23 at 15:09 -0400, Michael
Sorry for replying without context; I only joined
the mailing list
after the first few messages in this thread...
I'm particularly interested in the planning of this project and the
GNOME build service client, as I'm planning to implement similar
functionality in MonoDevelop, the Mono (C# etc) IDE. Hence if we
could share ideas, plans, designs and other information, that would
be great. It's a shame all three of us are using different runtimes,
as this means we can't share code directly :-/
yes, I think we should consider sharing the client implementation as
much as possible, so I see 2 solutions:
* write a C library and create bindings from it
* write a D-Bus daemon that can be contacted via any D-Bus bindings
for the GNOME client we were planning to use the OSC API, since we'll
be using pygtk, but since the Java and Mono clients are not able to use
it and so need to write their own client lib, I think we could use some
of the SoC student's time to work on this shared layer, couldn't we?
Reading this, I wonder why we need a standard library for the api at all.
Not that I am against it, but which functionality should go into it. I
think most should be implemented on the api.o.o side.
Pure http connect should be available in every development enviroment
Can you give some examples what kind of functionality makes sense to have
in a common application library ?