Hi Aravinda,
Aravinda Liyanage wrote:
Hi..!
No. I'm not familiar with C++. I am working with java. Since i don't have a
depth knowledge about the core of open office and due to the time limit
constrains , I'm trying to follow the second method.
So, Have you any suggestions to proceed in this
Hi Aravinda,
Aravinda Liyanage wrote:
@Ingrid Halama
Thank you for the consideration. Actually I want to implement a new chart
style for Open Office. Such as surface chart.
Am studying the developers guide these days. But i don't know weather
it(New chart type) is to develop as a add-
Hi,
Aravinda Liyanage wrote:
Hello everyone..
I want to create a *new chart style for open office*.
1.What is the *most suitable IDE, netbeans or ecipse for this
project*??? If that is eclipse, *How to integrate(install plugin or
something) open office into it*
2. I installed Open
On 06/23/10 15:57, Stephan Bergmann wrote:
[...]
By now, its probably too late to be able to extract information exactly
where the tests started to break on the various bots when DEV300_m80
became available end of May, right? :(
Bots Solaris-Intel and Ubuntu-9.04-i386 failed due to DISPLA
On 02/15/10 10:16, Stephan Bergmann wrote:
On 02/12/10 17:18, Christian Lippka wrote:
If you change code at one place, you may cause an assertion to
trigger at another place.
Since triggered assertions indicate programming errors, the above
sentence is equivalent to "If you change code at one
On 02/12/10 17:54, bjoern michaelsen - Sun Microsystems - Hamburg
Germany wrote:
On Fri, 12 Feb 2010 17:31:18 +0100
Christian Lippka wrote:
If we make the office crash in non pro than there will be never a
chance to get the qa to work on non pro again.
Depends. If we make the master crash on
On 02/12/10 15:05, bjoern michaelsen - Sun Microsystems - Hamburg
Germany wrote:
On Fri, 12 Feb 2010 14:38:18 +0100
Philipp Lohmann wrote:
The obvious optimization for that process would be leaving things as
they are and introduce an OSL_ASSERT_ABORT for those who really want
that.
still on
Hi Bernd,
That was cool fast! Thanks a lot for implementing this feature! :-)
By the way, I can confirm problems login into OOo-EIS at the moment. The
login mask does not return with any result. Thats maybe related to
Koheis problem?
Thanks again!
Ingrid
On 10/15/09 15:13, Bernd Eilers wrote
Hi Bernd,
On 10/13/09 18:07, Bernd Eilers wrote:
Hi there!
Just a quick reminder to specification writers:
Specification documents are parsed for creating "WhatsNew" information
included into ReleaseNotes HTML pages where some content from the
specifications is being extracted for the Relea
Hi André,
André Schnabel wrote:
Hi Ingrid,
Ingrid Halama schrieb:
Mathias Bauer wrote:
The problem is that the usual test runs obviously don't find the bugs
That is not obvious to me. Too often the mandatory tests haven't been
run. And if tests do not find an important problem
Mathias Bauer wrote:
Ingrid Halama wrote
Martin Hollmichel wrote:
Mathias Bauer wrote:
Ingrid Halama wrote:
This is not sufficient. Heavy code restructurings and cleanups are
not bound to the feature freeze date,
Perhaps they should? And at least as
Thorsten Ziehm wrote:
Hi Ingrid,
Ingrid Halama schrieb:
[...]
So I would like to see mandatory automatic tests that detect whether
the important user scenarios still work properly, whether files are
still rendered as they should, whether the performance of the office
has not significantly
Mathias Bauer wrote:
Ingrid Halama wrote:
This is not sufficient. Heavy code restructurings and cleanups are not
bound to the feature freeze date,
Perhaps they should? And at least as far as it concerns me they are.
but have a great potential to
introduce regressions also. I
Martin Hollmichel wrote:
Mathias Bauer wrote:
Ingrid Halama wrote:
This is not sufficient. Heavy code restructurings and cleanups are
not bound to the feature freeze date,
Perhaps they should? And at least as far as it concerns me they are.
yes, I also consider large amount or new
Hi Martin, all,
Martin Hollmichel wrote:
*Hi,
so far we have got reported almost 40 regression as stopper for 3.1
release, see query
http://tinyurl.com slash cgsm3y .
for 3.0 ( **http://tinyurl.com slash ahkosf ) we had 27 of these issues,
for 2.4 (**http://tinyurl.com slash c86n3u** ) we h
This is discussed on the graphics mailing list
d...@graphics.openoffice.org
Kind regards,
Ingrid
Daniel Garcia wrote:
Hi all,
Description of the problem
I am using odfdom in conjunction with my OpenOffice to create a Odf2Xhtml
compiler. This compiler will ha
Hi Xiuzhi Cheng,
These issues are altogether not reproducible with OOo 2.4.1. They were
in OOo 2.4 but are already fixed. So there is something wrong around the
version information.
Kind regards,
Ingrid
XiuzhiCheng wrote:
> Hi all,
> The issues are:
> 92427 reload empty chart Office crash w
Hi,
The bug with XTableChart::getRanges is issue i91212 and is fixed within
the upcoming version dev300m27.
Thanks Craig for providing the very good and detailed description of the
problem via separate mail!
Cheers,
Ingrid
Craig Johnson wrote:
Who do I need to contact to get some expert he
Hi Frank,
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Joerg,
We haven't identified the tests. The requirements was that they should
be "rock solid" and we have given those RESOURCE and MAIN FUNCTIONALITY
tests to customers and they were able to deal with them.
It makes sense to use
Hi Frank, all,
Frank Schönheit - Sun Microsystems Germany wrote:
[...]
I'm not voting against tests which finish in a reasonable time frame
(and fulfill other requirements said in the thread), but 3 days is quite
a lot of time ...
Given all the other requirements and granted all the other conc
Hi Frank,
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Ingrid,
Why is it a serious hurdle to wait let's say 3 days? For me this is not
so obvious.
Imagine your frustration what happens if the test fails after 2 days and
20 hours ... Or the turnaround times you have when the test fail
Hi Frank,
[...]
Those that run only several hours not weeks like the
current ones?
That's important indeed. If I have to wait several days betwen finishing
my builds and passing the CWS to QA, just "because" of the test, this
would certainly be a serious hurdle.
Why is it a serious hurdle to
Hi Jörg,
Jörg Jahnke wrote:
Hi,
one of the questions is whether it would be acceptable for everyone to
run a small regression test-suite prior to the QA-approval of a CWS.
These tests would probably run several hours, depending on the hardware
being used, and therefore cost time and hardware
Hi Joe,
Joe Smith wrote:
Ingrid Halama wrote:
...
You are welcome to download the latest developer snapshot containing
the new chart for evaluation and testing purposes:
...
Great news--congratulations! I've been waiting to give it a test drive;
I'm sure a lot of other users ha
-> issue 67179 http://www.openoffice.org/issues/show_bug.cgi?id=67179
Ingrid Halama schrieb:
Hi,
I would like to suggest to skip the systemintegration and the whole
installation process for the developer snapshot builds and instead
create a file archive (zip,gz) which simply extracts t
Hi,
I would like to suggest to skip the systemintegration and the whole
installation process for the developer snapshot builds and instead
create a file archive (zip,gz) which simply extracts to a ready to use
OpenOffice.
For the following reasons:
1) Installing a developersnapshot with sys
Hi Frank,
Frank Schönheit - Sun Microsystems Germany schrieb:
...
The point with the user installations is the only one I'd care to
address: I don't know how many reported bugs result from two dev builds
using the same user installation (there definately are some). But we
could easily eliminate
Hi Frank and Christian,
Frank Schönheit - Sun Microsystems Germany wrote:
Hi Christian,
2) The different installations may conflict in the user installation
directory as this is shared. So you might get strange bugs.
the dev-builds have a different user-installation than the stable one.
but
Hi all,
I would like to suggest some modifications for the OpenOffice_Dev
installations sets.
As far as I know the OpenOffice_Dev target was introduced to create
Builds that can be installed in parallel to a normal OpenOffice version
for testing and developing purposes.
But there are still
Hi,
I am including and using it having a member
::boost::function0 m_func;
Plus having code that invoces the function in a c++ file:
m_func();
Trying to compile that code I get a link error:
error LNK2001: unresolved external symbol [EMAIL PROTECTED]@@
This 'bad_function_call' is an excepti
30 matches
Mail list logo
