On 09/29/10 22:54, Soohong Min wrote:
I am built Openoffice 3.2.1 and am trying to run it with macro.
BTW, I was in strange situation I cannot understand this.
My issue is that I got error message I run this code.
oUrl = private:factory/swriter
---oDoc = starDeskTop.loadcomponentFromUrl(Url,
On Thu, Sep 30, 2010 at 09:11:53AM +0200, Stephan Bergmann wrote:
Strange. Which platform are you on, and where did you get OOo from?
(The lr in deploymnetlr.uno.so indicates a platform, but it is none
of the standard ones.) What might give a clue is to call
Linux/ARM.
Grüße/Regards,
Hi Stephan,
So, I would be somewhat unhappy to throw all those they require a
running OOo instance tests into the same unreliable category.
See the list of sporadic failures at the end of
http://wiki.services.openoffice.org/wiki/Test_Cleanup#unoapi_Tests_2.
Many of them deal with
Am Thu, 30 Sep 2010 14:19:37 +0200
schrieb Frank Schönheit frank.schoenh...@oracle.com:
Hi Stephan,
[...]
The trick is to let writing tests guide you when writing an
implementation, so that the resulting implementation is indeed
(unit) testable. See for example
Hi Björn,
Well, this the trick is ... part is exactly why I think that
issueing a statement like from now on, we do tests for our code
won't work - this is a complex topic, with a lot of tricks to know,
so Just Do It! is an approach which simply doesn't work. But okay,
that's a different
