[api-dev] [EMAIL PROTECTED] GUIDE: important things to know about this mailing list

2005-10-17 Thread Michael Hoennig
Dear OpenOffice.org community, This is the monthly reminder of important things to know about the dev@api.openoffice.org mailing list. We, the project leads of the OOo API project, would like to give you some general information to help you with your questions. *** =

Re: [api-dev] Returnvalues from Macros

2005-10-17 Thread Alexandro Colorado
On Mon, 17 Oct 2005 19:04:44 +0100, Alexander Peters <[EMAIL PROTECTED]> wrote: Hello! I use OLE to connect to OpenOffice.org Writer and want to get Returncodes from Macros which i execute with a dispatcher. How can i make this? Or is there an other way to execute macros to get a returnv

[api-dev] PyUNO: importing modules in package directory

2005-10-17 Thread Jorge . Pelizzoni
Hi, all! It seems that the main python module of a UNO component cannot trivially load/import auxiliary modules shipped in the same package directory. Is that correct? How can I circumvent that? Thanks in advance. Cheers, Jorge. ---

[api-dev] TextTable: iterating over selected cells

2005-10-17 Thread Jorge . Pelizzoni
Hi, all! Is there a way to iterate over the cells of a TextTable that have been selected by the user? I already know of invoking getSelection for the controller. However, it seems that the best that the thus obtained XTextTableCursor can provide is RangeName, which appears useless in the case of

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Joerg Budischewski
Hi, But I think the most striking advantage a typeunsafe over a typesafe language has, is that you need to write less source code to do the same thing. If the language binding would be designed with an queryInterface, the advantage would vanish hurting you with nearly every line of uno code y

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Joerg Budischewski
Hi, If the language binding would be designed with an queryInterface, the advantage would vanish hurting you with nearly every line of uno code you write, so I would implement it again this way. The irony here is that UNO (and hopefully the OOo API) needs less queryInterface than it did in

[api-dev] Returnvalues from Macros

2005-10-17 Thread Alexander Peters
Hello! I use OLE to connect to OpenOffice.org Writer and want to get Returncodes from Macros which i execute with a dispatcher. How can i make this? Or is there an other way to execute macros to get a returnvalue? Any Codesnip in any language will help me. Greetings Alexander Peters ---

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Rony G. Flatscher
Sorry for my sluggish-like, out-of-sync-responses (for unknown reasons the turn-around-time of e-mails via this list is up to hours delayed for me, so I sometimes see postings that were sent earlier, *after* I sent an e-mail)! ---rony -

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Rony G. Flatscher
Stephan Bergmann wrote: Rony G. Flatscher wrote: ... cut ... Just curious: how do you write down in ooRexx calls to method bar on an object that implements the two interfaces   module m1 { interface XFoo { void bar(); }; };   module m2 { interface XFoo {

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Rony G. Flatscher
Probably it would be possible to do the same with OOo Basic, ie. add that behaviour there as well (and it should be possible without breaking existing code), e.g. uur.XUnoUrlResolver.resolve(unoURL) ... as an option to uur.resolve(unoURL) ...which could break existing code:

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Mathias Bauer
Rony G. Flatscher wrote: > > Mathias Bauer wrote: > >>>E.g., in the ooRexx support for UNO/OOo the connection-routine looks like: >>> >>>- cut here - >>>::routine UNO.connect public >>> parse arg unoURL -- retrieve the argument, if any >>> >>> xContext=.UNO~Bootstrap

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Stephan Bergmann
Rony G. Flatscher wrote: ... cut ... Just curious: how do you write down in ooRexx calls to method bar on an object that implements the two interfaces module m1 { interface XFoo { void bar(); }; }; module m2 { interface XFoo { void baz(); }; }; Hmm, good question. Could you please hin

Re: [api-dev] Xforms and API

2005-10-17 Thread Frank Schönheit - Sun Microsystems Germa ny
> - Instead of creating an empty text document, you need to create a text > document with a special parameter (which I don't remember right now > :-\) to create an XML form document private:factory/swriter?slot=21053 Urghs. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Stephan Bergmann
Rony G. Flatscher wrote: Mathias Bauer wrote: E.g., in the ooRexx support for UNO/OOo the connection-routine looks like: - cut here - ::routine UNO.connect public parse arg unoURL -- retrieve the argument, if any xContext=.UNO~Bootstrap~bootstrap -- ge

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Rony G. Flatscher
... cut ... Just curious: how do you write down in ooRexx calls to method bar on an object that implements the two interfaces module m1 { interface XFoo { void bar(); }; }; module m2 { interface XFoo { void baz(); }; }; Hmm, good question. Could you please hint how you would do that in

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Stephan Bergmann
Jörg Budischewski wrote: Hi, As Stephan pointed out such means do exist in Basic and they are described in our DevGuide. I don't know if PyUNO has means too so we must ask people knowing the binding. AFAIK Jörg Budischewski is reading the udk list so perhaps we should move the discussion there.

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Rony G. Flatscher
Mathias Bauer wrote: E.g., in the ooRexx support for UNO/OOo the connection-routine looks like: - cut here - ::routine UNO.connect public parse arg unoURL -- retrieve the argument, if any xContext=.UNO~Bootstrap~bootstrap -- get an initialize

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Stephan Bergmann
Rony G. Flatscher wrote: In principle we have the necessary mechanisms in Basic and PyUNO (see previous post by Jörg). However, since the existing mechanims are "heavy" and ugly, they are not used consistently in practice. That means that much of the code that is written in those language

Re: [api-dev] Xforms and API

2005-10-17 Thread Stephan Bergmann
Frank Schönheit - Sun Microsystems Germany wrote: [...] The IDL reference for OOo 2.0 does not seem to be online, yet - at least not at http://api.openoffice.org/docs/common/ref/com/sun/star/module-ix.html. Not sure if there's another place, else, you might need to read IDL files (ugly) or genera

Re: [api-dev] multiple-inheritance interafces and method name clashes

2005-10-17 Thread Mathias Bauer
Rony G. Flatscher wrote: > E.g., in the ooRexx support for UNO/OOo the connection-routine looks like: > > - cut here - > ::routine UNO.connect public > parse arg unoURL -- retrieve the argument, if any > > xContext=.UNO~Bootstrap~bootstrap -- get an initi