OOo Status digest issue #6 - June 11th 2007

This is the weekly status digest of what the Novell
OpenOffice team is up to. It will relate changes made to
OpenOffice
(ooo-build or upstream) and list important work in
progress.

Week June-4 to June-10 2007:

- CJK features (see ht
tp://wiki.services.openoffice.org/wiki/CJK_Group)

- more EMF+ import

- created a cws-namespacefixes.diff (contains FastParser)
extract for SoC

- qatesttool work

- released ooo-build-2.2.0.2 and ooo-build-2.1.16 (SuSE
packages)

- wpg import: added support for importing of bitmap data
inside WPG files

- lxr migration suspended for now.


Still In progress:

- evaluating the use of git as a version control system for
OpenOffice.
Main obstacle: windows.
- OpenXML import / export (Excel and PowerPoint) in the
xmlfilter02 CWS:
the PPTX importer now import text with basic styling. 
- OpenXML (Word) in the writerfilter2 CWS.
- More VBA support (npower7 and npower8 CWS)
- SoC mentored by Michael for the new GUI layout code.
- SoC mentored by Jan (kendy) for the SVG import.

_______________________________________________
Openoffice mailing list
Openofficelists.ximian.com
h
ttp://lists.ximian.com/mailman/listinfo/openoffice

From: Hubert Figuiere <hfiguierenovell.com>
Subject: [Open Office] OOo Status digest issue #6 - June
11th 2007
Date: Mon, 11 Jun 2007 11:00:53 -0400

> - qatesttool work
I'd like to ask the developer what are done on qatesttool.
as I'm the qa project lead.

Thanks,
-- Nakata Maho (mahoFreeBSD.org)
_______________________________________________
Openoffice mailing list
Openofficelists.ximian.com
h
ttp://lists.ximian.com/mailman/listinfo/openoffice

Hi Maho,

On Tuesday 12 June 2007 07:17, Maho NAKATA wrote:
> From: Hubert Figuiere <hfiguierenovell.com>
> Subject: [Open Office] OOo Status digest issue #6 -
June 11th 2007
> Date: Mon, 11 Jun 2007 11:00:53 -0400
>
> > - qatesttool work
>
> I'd like to ask the developer what are done on
qatesttool.
> as I'm the qa project lead.

It was not really a work on qatesttool, but a work based on
qatesttool 
results  
qatesttool uncovered a 64bit problem here, and I fixed
that:

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


Regards,
Jan
_______________________________________________
Openoffice mailing list
Openofficelists.ximian.com
h
ttp://lists.ximian.com/mailman/listinfo/openoffice

On Tue, 2007-06-12 at 18:29 +0200, Jan Holesovsky wrote:
> It was not really a work on qatesttool, but a work
based on
> qatesttool 
> results  
qatesttool uncovered a 64bit problem here, and I fixed
> that:
> 
> http://www.openoffice.org/issues/show_bug.cgi?id=78198

> 

Which lead to the question:

Shouldn't we really change the container instead?

I know it is work, but typically this is the kind of bad
type cast that
should be avoided as much as possible.


Hub

_______________________________________________
Openoffice mailing list
Openofficelists.ximian.com
h
ttp://lists.ximian.com/mailman/listinfo/openoffice

Hi Hub

On Wednesday 13 June 2007 00:33, Hubert Figuiere wrote:
> On Tue, 2007-06-12 at 18:29 +0200, Jan Holesovsky
wrote:
> > It was not really a work on qatesttool, but a work
based on
> > qatesttool
> > results  
qatesttool uncovered a 64bit problem here, and I fixed
> > that:
> >
> > http://www.openoffice.org/issues/show_bug.cgi?id=78198

>
> Which lead to the question:
>
> Shouldn't we really change the container instead?
>
> I know it is work, but typically this is the kind of
bad type cast that
> should be avoided as much as possible.

Well, generally there's nothing bad with having the
possibility to be able to 
count to ULONG_MAX; it is just a bit too much in 64bit case
,
and that's 
why I thought we could change Container - on 32bit, 32bit
ULONG_MAX is 
sufficient as well.

OTOH - ULONG is OK there as long as it is used consistently,
and that is fixed 
by the patch, so - I don't think it is worth the effort 

Regards,
Jan
_______________________________________________
Openoffice mailing list
Openofficelists.ximian.com
h
ttp://lists.ximian.com/mailman/listinfo/openoffice