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

List:       kde-devel
Subject:    Re: KDE integration of OpenOffice
From:       CPH <cphennessy () openoffice ! org>
Date:       2003-08-19 21:28:19
[Download RAW message or body]

Hi Jan,
	cuckoo ( http://artax.karlin.mff.cuni.cz/~kendy/cuckooo ) looks like it's 
*very* interesting.
Interested in it becoming an incubator project within OpenOffice.org ?

A few other things worth considering include :
   using the Kde File dialog instead of the OOo one;
   allow OOo to use kio slaves;
   ability to use KAddressBook as a datasource;

I'm sure given enough time I can think of more :)

CPH

On Tuesday 19 August 2003 15:33, Jan Holesovsky wrote:
> Hi!
>
> On Tue, 19 Aug 2003, Willi Richert wrote:
> > is there some development/discussion ongoing integration OO via dcop? I
> > think it would be very powerful to script OO with any modern scripting
> > language.
>
> Please, could you be more verbose, what exactly do you need?
> OOo uses its own component architecture called UNO. The OOo Developer's
> Guide talks about "bridges" between UNO and other component architectures,
> which IMHO is what you are looking for. But I am not sure if DCOP <-> UNO
> bridge is worth programming.
>
> BTW, yesterday I posted an annoucement of OOo KDE integration based on
> KParts to kde-announce (but it did not appear there yet). You can have a
> look at
>   http://artax.karlin.mff.cuni.cz/~kendy/cuckooo
>
> > I'm not so familiar with all those KDE libs, but there should be
> > something like kxmlrpc, a mapper which maps dcop calls to OO's Basic
> > language.
> >
> > Is that in general technically possible?
> >
> > Just some thoughts,
> > wr
>
> Bye,
> Kendy
>
> >> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to
> >> unsubscribe <<

-- 
CPH : openoffice.org volunteer

Please reply *only* to users@openoffice.org, as your responses will be
answered more quickly, more correctly, and shared to help more people.
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]