Re: [dev] Need expert help determining if bug with Chart.setRanges

[Cor Nouws]

Hi Craig,

Craig Johnson wrote (16-6-2008 21:01)


Who do I need to contact to get some expert help in determining if there 
is a bug

with Staroffice Basic macro usage of Chart.{getRanges,setRanges}?


Best is to post to [EMAIL PROTECTED]

Regards,
Cor
--
"The Year of 3" -2008- "Het jaar van 3"

Cor Nouws - Arnhem - Netherlands
  > marketing contact - http://nl.OpenOffice.org
  > Zeker van OpenOffice.org - www.nouenoff.nl


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] Need expert help determining if bug with Chart.setRanges

[Craig Johnson]

Who do I need to contact to get some expert help in determining if there is a 
bug
with Staroffice Basic macro usage of Chart.{getRanges,setRanges}?

Craig Johnson

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] fixing warnings in binfilter?

[Stephan Bergmann]

eric.bachard wrote:

Hi Stephan,

My apologies for the long delay before the answer, but I'm just back at 
home.



Stephan Bergmann a écrit :
: "I 
think we can start to fix warnings in binfilter."  When we started the 
warning-free endeavor, we deliberately left binfilter "unfixed."


Sorry, what means "we" ?  I was not aware something was decided 
"officially" about binfilter module.

Do you have a link ?


"We" here loosely means the group of people inside Sun that started to 
get the warning-free thing going back then.  I remember having discussed 
the binfilter issue in some face-to-face setting, but do not remember 
any further details, and also did not find anything written down 
regarding this.  My comment was not meant to imply an "officiality," I 
just wanted to give background information.


Don't get me wrong; I do not say you must not change binfilter (how 
could I?).  If you think it is a good idea, go ahead.


-Stephan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] fixing warnings in binfilter?

[eric.bachard]

Hi Stephan,

My apologies for the long delay before the answer, but I'm just back at 
home.



Stephan Bergmann a écrit :
: "I think we can start to fix warnings in binfilter."  When we started the 
warning-free endeavor, we deliberately left binfilter "unfixed."


Sorry, what means "we" ?  I was not aware something was decided 
"officially" about binfilter module.

Do you have a link ?

 The main motivation for making the code warning free was to offer a quality control tool for future code contributions/modifications (locating existing errors was only of subordinate interest).  But as binfilter is 
more-or-less dead code, it was deemed unrewarding to make that code warning free (a process with a non-trivial risk of introducing new 
errors, by the way).


Well, there are several things :

First, the idea was pedagogical. Means, I think this is helpfull for the 
Education Project (thus undirectly for OpenOffice.org Project), e.g. 
other could say fix warnings is one simple way to attract people 
interested to join, because :


- build OpenOffice.org is required (important prerequisite)
- create, apply/unapply patches is a daily task for all
- understand the code is mandatory
- discuss some warnings fixes on IRC is helpfull (and completmentary),
- this is good practice, and opens doors for other questions, ..etc


If I can, with the little experience I have, this is motivating: 
students have not an important experience with OpenOffice.org source 
code, and start slowly with a module like this one cannot cause too much 
of trouble. After some experiences like that, they become familarized 
with OpenOffice.org tree, and are less afraid with it's size.


Don't forget the main complain from the beginners:  too complicated and 
dark.


Continuying with the same goal, the idea to create cws is to show how 
things happen for true in the project, with a limited risk.


Second, I must admit 3MB of warnings at every build is a bit boring me 
(and I'm not alone), mainly when I know most of the problems do have a 
trivial fix ( say at least 95%), I think it cannot be bad to fix them.


I never said fix all ( I discussed some with Philipp recently, and 
obviously, some fixes will probably be tricky, or not possible), but 
again, I'm pretty sure it won't hurt anybody to eliminate 95% of those 
warnings.


Last but not least, Jan Holesovsky (alias Kendy) intelligently proposed 
to create patches with one objective only. e.g. one patch for 
uninitialized variables, one for bad Ctor initializations .. etc. More 
easy to verify the fixes are ok.


I hope you get what I thought starting such task.


Regards,
Eric

--
Education Project: 
http://wiki.services.openoffice.org/wiki/Education_Project


Blog : http://eric.bachard.free.fr/news


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: [dev] build cairo error

[Caolan McNamara]

On Mon, 2008-06-16 at 15:17 +0800, 黄新 wrote:
> Hi, The error is: *
>   ../../unxlngi6.pro/slo/cairo_spritehelper.o: In function
>  `cairocanvas::SpriteHelper::redraw(_cairo*, basegfx::B2DPoint const&,
>  bool&, bool) const': cairo_spritehelper.cxx:(.text+0x355): undefined
>  reference to
>  `cairocanvas::doPolyPolygonImplementation(basegfx::B2DPolyPolygon,
>  cairocanvas::Operation, _cairo*,
>  com::sun::star::uno::Sequence
>  const*, cairocanvas::SpriteCanvas*)'   collect2: ld returned 1 exit
>  status 

http://www.openoffice.org/issues/show_bug.cgi?id=88260

C.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] build cairo error

[黄新]

Hi,
Now ,I try to build  OOo2.4.0 in the ubuntu system.I input the "build  
--all" command in the "instsetoo_native" file.when it start build the "canvas" 
file,the "building" was interrupted .
The error is:
*
 ../../unxlngi6.pro/slo/cairo_spritehelper.o: In function 
`cairocanvas::SpriteHelper::redraw(_cairo*, basegfx::B2DPoint const&, bool&, 
bool) const': 
cairo_spritehelper.cxx:(.text+0x355): undefined reference to 
`cairocanvas::doPolyPolygonImplementation(basegfx::B2DPolyPolygon, 
cairocanvas::Operation, _cairo*, 
com::sun::star::uno::Sequence const*, 
cairocanvas::SpriteCanvas*)' 
 collect2: ld returned 1 exit status 
  
  
 dmake:  Error code 1, while making '../../unxlngi6.pro/lib/cairocanvas.uno.so' 
  
 ERROR: Error 65280 occurred while making 
/home/hook/openoffice-test/DEV300_m14/canvas/source/cairo 
*
I am lack of setting ? or the code is error?
I am confusing!
who can tell me why?
thank you very much!

   
-
 雅虎邮箱，您的终生邮箱！

Re: [dev] The evil that is cppu::getCaughtException

[Stephan Bergmann]

Stephan Bergmann wrote:

Stephan Bergmann wrote:

Stephan Bergmann wrote:
[...]
The interesting thing, however, is that if I re-build this test 
scenario from scratch, with a main.exe and first.dll and second.dll 
(corresponding to soffice.bin, soffice.dll, sal3.dll, resp.) built 
"by hand" (without many of the switches used in the OOo build 
env.)---then it works!  I then do not even need the MS runtime libs 
in the C:\TEST\sub directory, the process starts happily with the 
runtime libs just in the C:\TEST directory next to the executable, 
and the re-thrown exception is caught.


So, maybe there is still hope, if we can identify the critical 
difference in the build environments for the two scenarios, and adapt 
the OOo build env. correspondingly...


The magic difference appears to be the way the Windows SDK mt tool is 
called to include XXX.dll.manifest in XXX.dll itself.  The OOo build 
environment uses a resource_id of 2 (i.e., 
ISOLATIONAWARE_MANIFEST_RESOURCE_ID, cf. WinUser.h in the Windows 
SDK), while I used the default (CREATEPROCESS_MANIFEST_RESOURCE_ID, 
defined as 1).  There appears to be no particular reason to use 2 in 
solenv/inc/tg_shl.mk:1.98 and following revisions (and 
solenv/inc/_tg_shl.mk generated from it), so I am now doing a 
DEV300m11 wntmsci12.pro OOo built with those places changed to the 
default, hoping that the resulting application will work fine.  
(However, the sad truth is that such a build takes on the magnitude of 
days rather than hours for me, so it will be some time before we know 
for sure...)


...and the freshly built OOo indeed appears to work fine!

However, one detail still puzzles me:  During the OOo build, the gperf 
tool is called.  In the Sun Hamburg build environment, it is available 
as a pre-built executable (r:\btw\DEV300\gperf.exe) that appears to be 
built with the .Net 2005 compiler (it links against msvcr80.dll) but 
also, for whatever reason, links against OOo's own sal3.dll.  However, a 
copy of the sal3.dll is not placed next to gperf.exe in r:\btw\DEV300, 
so, due to the PATH settings in the build environment, the sal3.dll 
produced during the OOo build itself is used (the one in the solver, at 
wntmsci12.pro\bin\sal3.dll).  Bad as that may be, it appears to have 
always worked fine (not too much of a surprise, given that sal has a 
stable interface).  But with my changes (sal3.dll containing 
sal3.dll.manifest with resource_id 1 instead of 2), the calls to gperf 
during the OOo build now fail:



Microsoft Visual C++ Runtime Library

Runtime Error!

Program: D:\shared\solar\r\btw\DEV300\gperf.exe

R6034
An application has made an attempt to load the C runtime library 
incorrectly.

Please contatct the application's support team for more information.


followed by


gperf.exe - Application Error

The application failed to initialize properly (0xc142). Click on OK 
to terminate the application.



So I thought maybe the redistributable runtime files (msvcr90.dll etc.) 
were missing from the location where sal3.dll is located, so I copied 
them there (solver's wntmsci12.pro\bin), but the failure remained.


Does that mean that my change would mean that the URE libraries now only 
work in an executable compiled with the exact same Microsoft compiler 
version as the URE libraries themselves?  Maybe someone else can help 
shed some light on this...


As nobody was able to shed enough light on this issue to clear the fog, 
it appears to be too brittle an approach to switch from 
ISOLATIONAWARE_MANIFEST_RESOURCE_ID to 
CREATEPROCESS_MANIFEST_RESOURCE_ID and wait for all sorts of unexpected 
anomalies to pop up over time.


The next worst thing is to remove the MS runtime files from the three 
OOo layers and instead install them into the system during OOo 
installation, so we will now go down that route (and see where we get).


-Stephan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[dev] Wishlist: Adopt the orphans, bring them a new ODT home.

[Marco]

Hello, all.
I'm new on this list and since I don't find a similar issue I will open this 
one.
MS Office 2003 and 2007 will refuse to open legacy file formats[1] using
"security reasons as justification for the move".
I think this "move" is wrong. It is user's files, not MS files.
I propose a final solution: adopt the "MS Office orphaned" files, care then,
bring them a new long and prosper life as an ODT file. A new life where nobody
will decide when or where they will be opened again.
I suggest to add a new check box, default checked, "All Legacy Docs" at the
installation dialog.
The affected file types: http://support.microsoft.com/kb/938810/en-us#tocHeadRef

1.
http://news.softpedia.com/news/Office-2003-SP3-Disables-Legacy-File-Formats-75235.shtml
-- 
Marco de Freitas



signature.asc
Description: OpenPGP digital signature

[dev] Contribution to the PDF Import filter for Writer

[arkarell]

Hello,

I'm an engineer specialist on documentary process, I worked nine years 
in Xerox company and I'm now freelance in my own society named Arkarell.
I worked a lot on xml related technologies (and even SGML at the 
beginning)  like xslt or xsl-fo.
I focused my work on publishing part of industrial system of production 
of technical documentation.
In this context, I used extensively the openoffice.org solution as 
"publishing desktop software" with its underlying format OpenDocument.
I've been working on a open source digital library named Castore 
 for a french engineering school ('/Ecole 
des Nines de Nantes/') for which I've implemented a conversion tool of
text documents into structured xml with use of OpenDocumentText as a 
pivot format. The input formats contain PDF and then my work on PDF 
includes a conversion of PDF into ODT format.
I've already begin this work which is based, for parser part, on xpdf 
library.
I keep reading the information about your pdf import filter and today I 
tested your very new extension of import PDF into draw dated June 11. I 
think I can help you for this feature
because I have motivation, time, some budget and, I hope, some knowledge 
to help moving forwards.


Could you explain to me how can I contribute to OpenOffice.org on this 
filter ?

Thanks in advance.

Arnaud Malguy
/Arkarell
Moëlan sur mer - France
/


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]