Re: Build fails in main/drawinglayer/source/texture/texture3d.cxx

2012-10-18 Thread Armin Le Grand

Hi Damjan,

On 17.10.2012 20:12, Damjan Jovanovic wrote:

On Wed, Oct 17, 2012 at 10:29 AM, Armin Le Grand armin.le.gr...@me.com wrote:

 Hi,



--snip--



It's most definitely NOT fixed, even in revision 1399319:

[ build CXX ] drawinglayer/source/texture/texture3d
/path/to/AOO/main/drawinglayer/source/texture/texture3d.cxx: In member
function 'sal_uInt8
drawinglayer::texture::GeoTexSvxBitmapEx::impGetTransparence(sal_Int32,
sal_Int32) const':
/path/to/AOO/main/drawinglayer/source/texture/texture3d.cxx:137:78:
error: call of overloaded 'Color(const BitmapColor)' is ambiguous
/path/to/AOO/main/drawinglayer/source/texture/texture3d.cxx:137:78:
note: candidates are:
/path/to/AOO/main/solver/350/unxlngx6.pro/inc/tools/color.hxx:120:7:
note: Color::Color(ColorData)
/path/to/AOO/main/solver/350/unxlngx6.pro/inc/tools/color.hxx:113:23:
note: Color::Color(const Color)
make: *** 
[/path/to/AOO/main/solver/350/unxlngx6.pro/workdir/CxxObject/drawinglayer/source/texture/texture3d.o]
Error 1
dmake:  Error code 2, while making 'all'


Sorry, but I'm normally building on Win (as I mentioned) and there the 
error does not happen. I had no access to a linux box yesterday, but I 
started a fresh checkoutbuild on linux one hour ago.





Attached is a possible patch (texture3d.patch) which gets it to
compile successfully but I don't want to apply it because it could be
semantically wrong.


Patches are automatically removed on the lists, as it seems.


Also attached is another patch (objectcontacttools.patch) for a
problem that breaks the build later on, because
drawinglayer::processor2d::canvasProcessor2D doesn't exist
(according to grep). Simply commenting out that section of code gets
it to compile. It seems that someone has already done similar
commenting for Windows in the #ifdef WIN32 just above my patch?
Since when was AOO a Windows-only project?


I will also check this; It's not a win-only project, but when developing 
it's not easy to build on all plattforms to check. This should certainly 
be done for bigger changes and a branch should be used, but even then 
there will be a time gap between this and the trunk integration.



Also it was necessary to use ld.gold for at least part of the build.

Please use those buildbots and keep AOO compiling on all platforms.


Yes, these build the trunk, so they check after checkin, too.
I'm on it...

Sorry again, but these implicit conversons seem to be triggered 
differently on different systems.



Regards
Damjan



Sincerely,
Armin
--
ALG


Re: Build fails in main/drawinglayer/source/texture/texture3d.cxx

2012-10-18 Thread Armin Le Grand

Hi Damjan,

On 18.10.2012 12:02, Damjan Jovanovic wrote:

On Thu, Oct 18, 2012 at 11:42 AM, Armin Le Grand armin.le.gr...@me.com wrote:

--snip--


Here they are in plain text then:

--snip--
Index: main/drawinglayer/source/texture/texture3d.cxx
===
--- main/drawinglayer/source/texture/texture3d.cxx  (revision 1399340)
+++ main/drawinglayer/source/texture/texture3d.cxx  (working copy)
@@ -134,7 +134,7 @@
  {
  const BitmapColor
aBitmapColor(mpReadBitmap-GetColor(rY, rX));

-if(maBitmapEx.GetTransparentColor() == Color(aBitmapColor))
+if(maBitmapEx.GetTransparentColor() ==
Color((ColorData)aBitmapColor))
  {
  return 255;
  }
--snip--


which could be simpler (combine it with your previous patch), if it's
even correct, and


..but will convert BitmapColor to sal_uInt8 (because there is a inline 
operator in the class BitmapColor), then casting to sal_uInt32 (since 
ColorData is a typedef to sal_uInt32) and thus would be wrong. Sigh.


Herbert is right, these operators are dangerous. I found two ways:
(a) extract RGB by feet from BitmapColor and construct a Color with it
(b) use the 'operator Color()' : '== aBitmapColor.operator Color()'

Where (a) will need more code, and (b) looks ugly.
I tend to (b) currently...

Build nearly finished...

Sincerely,
Armin



--snip--
Index: main/svx/source/sdr/contact/objectcontacttools.cxx
===
--- main/svx/source/sdr/contact/objectcontacttools.cxx  (revision 1399340)
+++ main/svx/source/sdr/contact/objectcontacttools.cxx  (working copy)
@@ -77,18 +77,18 @@
return new
drawinglayer::processor2d::VclPixelProcessor2D(rViewInformation2D,
rTargetOutDev);
  //}
  #else
-static bool bTryTestCanvas(false);
-
-if(bTryTestCanvas)
-{
-   // create test-cancas-Processor
-   return new
drawinglayer::processor2d::canvasProcessor2D(rViewInformation2D,
rTargetOutDev);
-}
-else
-{
+//static bool bTryTestCanvas(false);
+//
+//if(bTryTestCanvas)
+//{
+// // create test-cancas-Processor
+// return new
drawinglayer::processor2d::canvasProcessor2D(rViewInformation2D,
rTargetOutDev);
+//}
+//else
+//{
// create Pixel Vcl-Processor
return new
drawinglayer::processor2d::VclPixelProcessor2D(rViewInformation2D,
rTargetOutDev);
-}
+//}
  #endif
}
}
--snip--

Thank you and I appreciate your efforts
Damjan



--
ALG


Re: Build fails in main/drawinglayer/source/texture/texture3d.cxx

2012-10-18 Thread Armin Le Grand

Hi Damjan,

okay, done. Revisions are 1399608 and 1399610, so use the latter please.

Sincerely,
Armin

On 18.10.2012 14:14, Armin Le Grand wrote:

 Hi Damjan,

On 18.10.2012 12:02, Damjan Jovanovic wrote:

On Thu, Oct 18, 2012 at 11:42 AM, Armin Le Grand
armin.le.gr...@me.com wrote:

--snip--

--snip--

--
ALG


Re: Build fails in main/drawinglayer/source/texture/texture3d.cxx

2012-10-17 Thread Armin Le Grand

Hi,

On 17.10.2012 06:24, Pedro Giffuni wrote:



- Original Message -

From: Damjan Jovanovic

...


Hi

With the latest SVN, on Ubuntu 12.04 amd64, I am getting this error
when building:

[ build CXX ] drawinglayer/source/texture/texture3d
/path/to/AOO/main/drawinglayer/source/texture/texture3d.cxx: In member
function 'sal_uInt8
drawinglayer::texture::GeoTexSvxBitmapEx::impGetTransparence(sal_Int32,
sal_Int32) const':
/path/to/AOO/main/drawinglayer/source/texture/texture3d.cxx:135:70:
error: call of overloaded 'Color(BitmapColor)' is ambiguous
/path/to/AOO/main/drawinglayer/source/texture/texture3d.cxx:135:70:
note: candidates are:
/path/to/AOO/main/solver/350/unxlngx6.pro/inc/tools/color.hxx:120:7:
note: Color::Color(ColorData)
/path/to/AOO/main/solver/350/unxlngx6.pro/inc/tools/color.hxx:113:23:
note: Color::Color(const Color)
make: ***
[/path/to/AOO/main/solver/350/unxlngx6.pro/workdir/CxxObject/drawinglayer/source/texture/texture3d.o]
Error 1
dmake:  Error code 2, while making 'all'


I made some changes, got no errors on win (what means nothing as we 
know). It's strange since ColorData is just a typedef (to sal_Int32) and 
I see no way to auto-convert BitmapColor to it, so 'operator Color()' in 
class Color should be used.

Made that more explicit now in revision 1399148, please have a try.

Armin


FWIW,

I am also getting similar issues in drawinglayer today.

Pedro.



--
ALG


Re: Build fails in main/drawinglayer/source/texture/texture3d.cxx

2012-10-17 Thread Armin Le Grand

Hi Herbert,

On 17.10.2012 13:48, Herbert Duerr wrote:

On 17.10.2012 10:29, Armin Le Grand wrote:

I made some changes, got no errors on win (what means nothing as we
know). It's strange since ColorData is just a typedef (to sal_Int32) and
I see no way to auto-convert BitmapColor to it, so 'operator Color()' in
class Color should be used.


BitmapColor has implicit conversion operators for both
 BitmapColor::operator Color()
and
 BitmapColor::operator sal_uInt8()
Since Color has a constructor for an unsigned integer
 Color( sal_uInt32 nColor)
the conversion is ambiguous, even if the second alternative needs an
extra type conversion from sal_uInt8 to sal_uInt32.


Ah! That's the implicit one I've missed. That's really dangerous...


This shows again that implicit conversions are very tricky even for
experienced developers. So I suggest to prefer explicit constructors
over implicit ones. Unfortunately explicit conversion operators are only
available since C++11.

Things like e.g. the implicit conversion from BitmapColor to sal_uInt8
are too slick for my taste anyway and they should IMHO be made explicit
by replacing their uses by something like GetIndex(), so the C++11
feature of explicit conversion operators can be dispensed with.

Herbert



--
ALG


Re: OpenOffice SVG vector graphics

2012-10-08 Thread Armin Le Grand

Hi Ian,

On 07.10.2012 00:10, Ian Lynch wrote:

On 6 October 2012 22:23, Alexandro Colorado j...@oooes.org wrote:


On 10/6/12, Dennis E. Hamilton orc...@apache.org wrote:

I think the OP is asking about printed forms, as on a bumper sticker.

  Since

they are presumably enlarged, the provision of trademark information in
small but readable type at/around the margin would probably work.


Well this would be confusing in itself, doesnt it already has a printed TM?



One thing that immediately springs to mind is that Inkscape is getting used
for these drawings in preference to AOO Draw because it supports svg.  If
we are serious about a drawing component to AOO and to open standards we
must have a strategy to fully support svg. This has been an on-going issue
since the start of OOo but it is getting more and more urgent as time goes
on. Armin has done some great work, no doubt about it but we really need to
take it further. I only wish I had the know how.


It would be nice to fully support it, but don't forget that we need 
these things as OLE, MS-compatible CustomShapes and more stuff not 
supported by SVG, so there is no way to get a pure SVG editor from 
Draw/Impress.
We already have the good import (which creates an imported graphic 
containing the SVG) and a medium-quality export. Currently to do more 
than transformaing the SVG you need to 'break' it to draw objects 
(convert to our internal ODF data).
The easiest way to support this with more deph would be to go into a 
'Svg'-mode when a SVG graphic is selected (comparable from the theory to 
go to a bitmap editor UI when selecting a bitmap graphic).
Both would lead to writing new programs with new UI for these cases, a 
long lasting task to do, but possible. Woulöd also be nice for bitmap 
graphics, though. The quesion is if this would not already overburden 
our normal target users...
A good and logic way forward would be to write a SVG2.0 export, that 
could be used for playing presentations without AOO at all. Any 
volunteers...?


Sincerely,
Armin





  - Dennis

-Original Message-
From: acolor...@gmail.com [mailto:acolor...@gmail.com] On Behalf Of
Alexandro Colorado
Sent: Saturday, October 06, 2012 09:28
To: ooo-dev@incubator.apache.org
Subject: Re: OpenOffice SVG vector graphics

On 10/6/12, Guy Waterval waterval@gmail.com wrote:

Hi Alexandro,
Hi all,

2012/10/6 Alexandro Colorado j...@oooes.org


I upload the OpenOffice SVG logo on pure SVG, still needs some cleanup
on the nodes, but this is a 100% SVG logo.
The attachment is on the cWiki:



https://cwiki.apache.org/confluence/download/attachments/27834483/ApacheOpenOfficeTM.svg





https://cwiki.apache.org/confluence/pages/viewpageattachments.action?pageId=27834483sortBy=date;



Many thanks for your work, it's appreciated.
Please, could you tell me how to reuse properly your work or any free
logo
of this type ?.
In a book there is no problem, a noticeCredits can tell the author and
license of the work.
But in other cases of use, as a banner on a car or as poster, how to do
to
give credit of the reused work ? I see only the possibility to add a

line

with the corresponding informations.


SVG is an XML program and support Metadata, which is extra information
on the work.

Inkscape support such metadata including a series of documents.


http://wiki.creativecommons.org/images/4/47/Inkscape-0.44SVN-metadata.png



A+
--
gw




--
Alexandro Colorado
PPMC Apache OpenOffice
http://es.openoffice.org





--
Alexandro Colorado
PPMC Apache OpenOffice
http://es.openoffice.org









Re: Which See Gull is Our Logo?

2012-10-05 Thread Armin Le Grand

Hi,

On 04.10.2012 21:05, Rob Weir wrote:

On Thu, Oct 4, 2012 at 2:35 PM, Ariel Constenla-Haile
arie...@apache.org wrote:


snip



We went around in circles on this back when we revised the gull logo
for the website, last May.  All we could find was a high-res raster
image.  No vector version.  So that's what was used when Michael
Acevedo designed the logo that we're currently using on the website.
At that time there was talk of reverse-engineering an SVG from the
bitmap, but the consensus at the time was to defer that since we knew
we'd be updating the design of the logo for AOO 4.0.

Btw, one location for AOO logos, what I tried to encourage as the
central location, is here:

http://www.openoffice.org/images/AOO_logos/


I can offer http://imagebin.org/230962, not sure anymore where it came 
from, though. I remember to have another hires one of the orbseagulls, 
probably on my machine @home, I'll check in the evening.


HTH!


-Rob



Regards
--
Ariel Constenla-Haile
La Plata, Argentina




Sincerely,
Armin
--
ALG


Re: [VOTE][PMC] PMC Chair

2012-10-05 Thread Armin Le Grand

[X] Andrea Pescetti (pescetti)

Armin

On 05.10.2012 01:41, Andrew Rist wrote:

This is a call for vote on selecting the PMC Chair the Apache OpenOffice
PMC.
Per the IPMC's Guide to Successful Graduation [1] the Apache
OpenOffice podling needs to select a PMC to be listed in the TLP
resolution.


Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.

The balloting will be until UTC midnight Sunday, 7 October:
2012-10-07T24:00Z.


[ ] Andrea Pescetti (pescetti)
[ ] Drew Jensen (atjensen)


The [DISCUSS] for this vote can be found at [2] and [3].  Note: Andrea
has accepted the nomination - Drew has not responded.


[1] http://incubator.apache.org/guides/graduation.html#toplevel
[2]http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201210.mbox/%3c506a1e72.20...@oracle.com%3E

[3]http://mail-archives.apache.org/mod_mbox/incubator-ooo-dev/201209.mbox/%3c5064c859.9090...@oracle.com%3E







Re: [VOTE] [PMC] Starting Membership for Apache OpenOffice PMC

2012-10-02 Thread Armin Le Grand

Hi,

+1, no complaints

Sincerely,
Armin

On 02.10.2012 00:38, Andrew Rist wrote:

This is a call for vote on selecting the following list as the starting
membership for the Apache OpenOffice PMC, to be listed in the TLP
resolution.  The voting is for the entire slate as listed.

Apache OpenOffice PMC Starting Membership:
Andre Fischer (af)
Andrea Pescetti (pescetti)
Andrew Rist (arist)
Ariel Constenla-Haile (arielch)
Armin Le Grand (alg)
Dave Fisher (wave)
Donald Harbison (dpharbison)
Drew Jensen (atjensen)
Ian Lynch (ingotian)
Jürgen Schmidt (jsc)
Kay Schenk (kschenk)
Kazunari Hirano (khirano)
Louis Suarez-Potts (louis)
Marcus Lange (marcus)
Oliver-Rainer Wittmann (orw)
Pedro Giffuni (pfg)
Peter Junge (pj)
Raphael Bircher (rbircher)
Regina Henschel (regina)
RGB.ES (rgb-es)
Roberto Galoppini (galoppini)
Yang Shih-Ching (imacat)
Yong Lin Ma (mayongl)


The balloting will be until UTC midnight Thursday,
4 October: 2012-10-04T24:00Z.

Approval requires a majority of +1 over -1 votes cast by members of
the PPMC.

 [  ] +1 approve
 [  ]  0 abstain
 [  ] -1 disapprove, for the following reasons:


The [DISCUSS] for this vote was enthusiastically in favor. There
were no concerns expressed other than issues with the timeframe of
discussions, which were suitably extended.  (note: All members of this
list, except for Drew and Raphael, accepted their nomination to this
list.  I have left Drew and Raphael on the list as neither declined, and
they still have the ability to decline later)








Re: [Call for review] improvements for linear/axial gradients #120604 and #120957

2012-10-01 Thread Armin Le Grand

Hi Kevin,

On 01.10.2012 17:38, Kevin Grignon wrote:

Any impact on the UI here?


No, just corrections in painted representations :-)


On Sat, Sep 29, 2012 at 12:32 AM, Armin Le Grand armin.le.gr...@me.comwrote:


 Hi Regina,


On 26.09.2012 17:34, Armin Le Grand wrote:


  Hi Regina,

On 25.09.2012 20:50, Regina Henschel wrote:


Hi all,

I have attached patches to
https://issues.apache.org/ooo/**show_bug.cgi?id=120957https://issues.apache.org/ooo/show_bug.cgi?id=120957and
https://issues.apache.org/ooo/**show_bug.cgi?id=120604https://issues.apache.org/ooo/show_bug.cgi?id=120604

They change the blending so, that first color is start color, last color
is end color and they set the number of steps to 2 * number in UI in
case of style 'axial', as discussed here some time ago.



Good :-)

  My coding skills are not professional and the Draw module is confusing,

so please have a look.



You are doing really well in the meantime (really!).
I'll take a look and check it. Give me some time, patches are not small
:-)



I'm on it...


  Kind regards

Regina



Sincerely,
  Armin
--
ALG







Sincerely,
Armin
--
ALG


Re: [Call for review] improvements for linear/axial gradients #120604 and #120957

2012-09-28 Thread Armin Le Grand

Hi Regina,

On 26.09.2012 17:34, Armin Le Grand wrote:

 Hi Regina,

On 25.09.2012 20:50, Regina Henschel wrote:

Hi all,

I have attached patches to
https://issues.apache.org/ooo/show_bug.cgi?id=120957 and
https://issues.apache.org/ooo/show_bug.cgi?id=120604

They change the blending so, that first color is start color, last color
is end color and they set the number of steps to 2 * number in UI in
case of style 'axial', as discussed here some time ago.


Good :-)


My coding skills are not professional and the Draw module is confusing,
so please have a look.


You are doing really well in the meantime (really!).
I'll take a look and check it. Give me some time, patches are not small :-)


I'm on it...


Kind regards
Regina



Sincerely,
 Armin
--
ALG





Re: [proposed PMC] call for feedback: Are you willing to serve as a PMC member?

2012-09-27 Thread Armin Le Grand

Hi list,

On 26.09.2012 11:37, Oliver-Rainer Wittmann wrote:

Hi,

this is a call for feedback to the people who are (currently) on the
proposed PMC list.
Please provide feedback, if you are willing to serve as a PMC member.

The current (copied from initial post of thread [1]) proposed PMC list is:


Proposed Working List:

   Andre Fischer (af)
   Andrea Pescetti (pescetti)
   Andrew Rist (arist)
   Ariel Constenla-Haile (arielch)
   Armin Le Grand (alg)


I'm willing to serve, let's go!


   Dave Fisher (wave)
   Donald Harbison (dpharbison)
   Drew Jensen (atjensen)
   Ian Lynch (ingotian)
   Jürgen Schmidt (jsc)
   Kay Schenk (kschenk)
   Kazunari Hirano (khirano)
   Louis Suarez-Potts (louis)
   Marcus Lange (marcus)
   Oliver-Rainer Wittmann (orw)
   Pedro Giffuni (pfg)
   Peter Junge (pj)
   Raphael Bircher (rbircher)
   Regina Henschel (regina)
   RGB.ES (rgb-es)
   Roberto Galoppini (galoppini)
   Yang Shih-Ching (imacat)
   Yong Lin Ma (mayongl)



Jürgen already expressed his willingness in thread [1].

[1] http://markmail.org/message/erjdi3wbe4hsjhqx


Best regards, Oliver.





Re: build svtools with debug

2012-09-27 Thread Armin Le Grand

Hi Pedro,

On 26.09.2012 20:05, Pedro Giffuni wrote:




From: Armin Le Grand

...


I builded a lot of other modules in this working copy with debug=t, all
worked well except svtools...

The question is how long will we be able to live with not being able to
debug in svtools on windows? Not a good situation...

I just found out that svtlls part called hatchwindowfactory *can* be
linked when adding the following:

Index: Library_hatchwindowfactory.mk
===
--- Library_hatchwindowfactory.mk   (revision 1389804)
+++ Library_hatchwindowfactory.mk   (working copy)
@@ -43,6 +43,7 @@
  tk \
  tl \
  vcl \
+   stl \
  $(gb_STDLIBS) \
   ))

@Pedro: Is this a solution? Maybe when using debug, extra stuff using
stl to verify things (remember data in a vector?) gets compiled. I do
not know how bad it is to always link against stl for
hatchwindowfactory, even without debug build. What do You think?



Ah, I see. The problem is we would be adding a dependency to stlport
*always* and in theory we are hoping to get rid of it ;-).

There is no option to do --without-stlport or to skip for debug builds
in our Windows build, right? :(

I don't really have a problem. I have been considering two alternatives
instead of getting rid of stlport:
1) There are patches to build the latest version of stlport with clang.
2) a bugzilla issue suggests apache stdcxx.

Both are very difficult to implement but it's not clear that simply removing
stlport and replacing it with more dependencies on boost is the way to
go.

In sum... yes, go ahead and add the dependency but note it carefully
in the commit log so we are able to find it if we need to know later on.


I committed that change, commented in the commit message. That 
dependency is not too bad, it will be removed (has to be removed) when 
we will do the STL cleanup and use only system stl. Hopefully this is 
not too far in the future ;-)



Pedro.






build svtools with debug

2012-09-26 Thread Armin Le Grand

Hi List,

with current trunk I cannot build svtools with debug, e.g.

cd svtools
make clean
make clean debug=t
make -sr -j8 debug=t

- Lots of unresolved externals from stl. Yes, I'm using stlport, and 
I'm on windows.


I tried to also build stlport with debug and delivered it, but does not 
help.


Can someone help...?

Output is:

--8---8-
c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/CxxObject/svtools/source/hatchwindow/documentcloser.o 
c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/CxxObject/svtools/source/hatchwindow/hatchwindow.o 
c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/CxxObject/svtools/source/hatchwindow/hatchwindowfactory.o 
c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/CxxObject/svtools/source/hatchwindow/ipwin.o

c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/WinResTarget/hatchwindowfactory/default.res
   Creating library 
c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/LinkTarget/Library/ihatchwindowfactory.lib 
and object 
c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/LinkTarget/Library/ihatchwindowfactory.exp
documentcloser.o : error LNK2019: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::_Loc_init::_Loc_init(void) 
(__imp_??0_Loc_init@ios_base@_STL@@QAE@XZ) referenced in function void 
__cdecl _STL::`dynamic initializer for '_LocInit''(void) 
(??__E_LocInit@_STL@@YAXXZ)
hatchwindow.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::_Loc_init::_Loc_init(void) 
(__imp_??0_Loc_init@ios_base@_STL@@QAE@XZ)
hatchwindowfactory.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::_Loc_init::_Loc_init(void) 
(__imp_??0_Loc_init@ios_base@_STL@@QAE@XZ)
ipwin.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::_Loc_init::_Loc_init(void) 
(__imp_??0_Loc_init@ios_base@_STL@@QAE@XZ)
documentcloser.o : error LNK2019: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::Init::Init(void) (__imp_??0Init@ios_base@_STL@@QAE@XZ) 
referenced in function void __cdecl _STL::`dynamic initializer for 
'_IosInit''(void) (??__E_IosInit@_STL@@YAXXZ)
hatchwindow.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::Init::Init(void) (__imp_??0Init@ios_base@_STL@@QAE@XZ)
hatchwindowfactory.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::Init::Init(void) (__imp_??0Init@ios_base@_STL@@QAE@XZ)
ipwin.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::Init::Init(void) (__imp_??0Init@ios_base@_STL@@QAE@XZ)
documentcloser.o : error LNK2019: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::_Loc_init::~_Loc_init(void) 
(__imp_??1_Loc_init@ios_base@_STL@@QAE@XZ) referenced in function void 
__cdecl _STL::`dynamic atexit destructor for '_LocInit''(void) 
(??__F_LocInit@_STL@@YAXXZ)
hatchwindow.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::_Loc_init::~_Loc_init(void) 
(__imp_??1_Loc_init@ios_base@_STL@@QAE@XZ)
hatchwindowfactory.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::_Loc_init::~_Loc_init(void) 
(__imp_??1_Loc_init@ios_base@_STL@@QAE@XZ)
ipwin.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::_Loc_init::~_Loc_init(void) 
(__imp_??1_Loc_init@ios_base@_STL@@QAE@XZ)
documentcloser.o : error LNK2019: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::Init::~Init(void) (__imp_??1Init@ios_base@_STL@@QAE@XZ) 
referenced in function void __cdecl _STL::`dynamic atexit destructor 
for '_IosInit''(void) (??__F_IosInit@_STL@@YAXXZ)
hatchwindow.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::Init::~Init(void) (__imp_??1Init@ios_base@_STL@@QAE@XZ)
hatchwindowfactory.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::Init::~Init(void) (__imp_??1Init@ios_base@_STL@@QAE@XZ)
ipwin.o : error LNK2001: unresolved external symbol 
__declspec(dllimport) public: __thiscall 
_STL::ios_base::Init::~Init(void) (__imp_??1Init@ios_base@_STL@@QAE@XZ)
c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/LinkTarget/Library/hatchwindowfactory.uno.dll 
: fatal error LNK1120: 4 unresolved externals
/bin/cp: cannot stat 
`/cygdrive/c/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/LinkTarget/Library/ihatchwindowfactory.lib': 
No such file or directory

--8---8-

Sincerely,
Armin
--
ALG



Re: [Call for review] improvements for linear/axial gradients #120604 and #120957

2012-09-26 Thread Armin Le Grand

Hi Regina,

On 25.09.2012 20:50, Regina Henschel wrote:

Hi all,

I have attached patches to
https://issues.apache.org/ooo/show_bug.cgi?id=120957 and
https://issues.apache.org/ooo/show_bug.cgi?id=120604

They change the blending so, that first color is start color, last color
is end color and they set the number of steps to 2 * number in UI in
case of style 'axial', as discussed here some time ago.


Good :-)


My coding skills are not professional and the Draw module is confusing,
so please have a look.


You are doing really well in the meantime (really!).
I'll take a look and check it. Give me some time, patches are not small :-)


Kind regards
Regina



Sincerely,
Armin
--
ALG


Re: build svtools with debug

2012-09-26 Thread Armin Le Grand

On 26.09.2012 17:57, Regina Henschel wrote:

Hi Armin

Armin Le Grand schrieb:

Hi List,

with current trunk I cannot build svtools with debug, e.g.

cd svtools
make clean
make clean debug=t
make -sr -j8 debug=t

- Lots of unresolved externals from stl. Yes, I'm using stlport, and
I'm on windows.

I tried to also build stlport with debug and delivered it, but does not
help.

Can someone help...?


I've got a debug build with MSVC 9.0 Express of r1389055. That's from
Sunday 23.Sept. I've made a clean build, including cleaning
ext_libraries.


That's not the problem. I've checked out yesterday and built, works 
well. This is a non-pro build. The problems comes up when you wahnt to 
build svtools with 'debug=t' to enable it for source level debugging.


Thus, this is not a build breaker (as long as noone is building with 
debug=t for all modules) and would have not been found initially by 
working in a branch (implying that on a branch the diverse plattform 
build would have been done, noone will build single modules with debug=t 
there).


When finding something like this I think it is not wrong to evtl. revert 
on trunk, go back on a branch and try to find out why a concrete case 
does not work (as with svtools here).


I builded a lot of other modules in this working copy with debug=t, all 
worked well except svtools...


The question is how long will we be able to live with not being able to 
debug in svtools on windows? Not a good situation...


I just found out that svtlls part called hatchwindowfactory *can* be 
linked when adding the following:


Index: Library_hatchwindowfactory.mk
===
--- Library_hatchwindowfactory.mk   (revision 1389804)
+++ Library_hatchwindowfactory.mk   (working copy)
@@ -43,6 +43,7 @@
tk \
tl \
vcl \
+   stl \
$(gb_STDLIBS) \
 ))

@Pedro: Is this a solution? Maybe when using debug, extra stuff using 
stl to verify things (remember data in a vector?) gets compiled. I do 
not know how bad it is to always link against stl for 
hatchwindowfactory, even without debug build. What do You think?




Kind regards
Regina



Output is:

--8---8-

c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/CxxObject/svtools/source/hatchwindow/documentcloser.o

c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/CxxObject/svtools/source/hatchwindow/hatchwindow.o

c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/CxxObject/svtools/source/hatchwindow/hatchwindowfactory.o

c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/CxxObject/svtools/source/hatchwindow/ipwin.o


c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/WinResTarget/hatchwindowfactory/default.res


Creating library
c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/LinkTarget/Library/ihatchwindowfactory.lib

and object
c:/aoo/svn_trunk16/main/solver/350/wntmsci12/workdir/LinkTarget/Library/ihatchwindowfactory.exp


documentcloser.o : error LNK2019: unresolved external symbol
__declspec(dllimport) public: __thiscall
_STL::ios_base::_Loc_init::_Loc_init(void)
(__imp_??0_Loc_init@ios_base@_STL@@QAE@XZ) referenced in function void
__cdecl _STL::`dynamic initializer for '_LocInit''(void)
(??__E_LocInit@_STL@@YAXXZ)
hatchwindow.o : error LNK2001: unresolved external symbol
__declspec(dllimport) public: __thiscall
_STL::ios_base::_Loc_init::_Loc_init(void)
(__imp_??0_Loc_init@ios_base@_STL@@QAE@XZ)
hatchwindowfactory.o : error LNK2001: unresolved external symbol
__declspec(dllimport) public: __thiscall
_STL::ios_base::_Loc_init::_Loc_init(void)
(__imp_??0_Loc_init@ios_base@_STL@@QAE@XZ)
ipwin.o : error LNK2001: unresolved external symbol
__declspec(dllimport) public: __thiscall
_STL::ios_base::_Loc_init::_Loc_init(void)
(__imp_??0_Loc_init@ios_base@_STL@@QAE@XZ)
documentcloser.o : error LNK2019: unresolved external symbol
__declspec(dllimport) public: __thiscall
_STL::ios_base::Init::Init(void) (__imp_??0Init@ios_base@_STL@@QAE@XZ)
referenced in function void __cdecl _STL::`dynamic initializer for
'_IosInit''(void) (??__E_IosInit@_STL@@YAXXZ)
hatchwindow.o : error LNK2001: unresolved external symbol
__declspec(dllimport) public: __thiscall
_STL::ios_base::Init::Init(void) (__imp_??0Init@ios_base@_STL@@QAE@XZ)
hatchwindowfactory.o : error LNK2001: unresolved external symbol
__declspec(dllimport) public: __thiscall
_STL::ios_base::Init::Init(void) (__imp_??0Init@ios_base@_STL@@QAE@XZ)
ipwin.o : error LNK2001: unresolved external symbol
__declspec(dllimport) public: __thiscall
_STL::ios_base::Init::Init(void) (__imp_??0Init@ios_base@_STL@@QAE@XZ)
documentcloser.o : error LNK2019: unresolved external symbol
__declspec(dllimport) public: __thiscall
_STL::ios_base::_Loc_init::~_Loc_init(void)
(__imp_??1_Loc_init@ios_base@_STL@@QAE@XZ) referenced in function void
__cdecl _STL::`dynamic atexit destructor for '_LocInit''(void)
(??__F_LocInit@_STL@@YAXXZ

Re: Clipart library

2012-09-20 Thread Armin Le Grand

On 19.09.2012 17:19, Ian Lynch wrote:

On 17 September 2012 22:16, Rob Weir robw...@apache.org wrote:

On Thu, Aug 30, 2012 at 4:51 AM, Ian Lynch ianrly...@gmail.com wrote:

I'm organising the Open clipart library into categories. We could use
this then as a useful resource to complement AOO. Any thoughts about
the best way to implement making the categorised library available to
the community?



Taxonomies are limiting, especially if a given clipart can live in
only one place.  Tagging is more flexible.  And searching is even more
so.

I noticed they have a REST API for searching OCAL, which is based on
text queries, e.g.:

http://openclipart.org/api/search/?query=trombonepage=1

So one option might be to have a smaller, curated set of
top-quality/most-commonly-used clipart pre-included in the install,
but then also have an in-product interface for searching the complete
online collection.  Could also allow searching of other public domain
image sources, including Flickr Common, Wikipedia, etc.


That is exactly what I had in mind. For none technical users, seeing
some images in the gallery on installation provides confidence apart
from anything else. Few casual users will know how to use the search
facilities on OCAL and many would not even know what OCAL was. It
really has to be intuitive and simple for the most limited end users
:-). The quickest and simplest start is to provide a simple set on
install. Then look at adding search to the user interface. Snag I'm
thinking about at the moment is that ideally the curated included set
would be vectors but most are in .svg not .odg format so we lose the
editing which is a key reason to have them as vectors.


Indeed we cannot edit SVG directly and it would be hard to achieve this, 
but you can 'Break' SVG objects and work on the resulting SdrObjects. 
These can also be exported again in SVG format, but the roundtrip ist 
stil far away from being good enough to call it an SVG editor (I'm 
thinking about next steps :-))



We could just
use png but that's not ideal. Longer term it would be better for AOO
to support svg fully, but that is a big job.


Yes...

Sincerely,
Armin
--
ALG


Re: Clipart library

2012-09-16 Thread Armin Le Grand

Hi Ian,

On 14.09.2012 15:49, Ian Lynch wrote:

On 14 September 2012 03:23, Armin Le Grand armin.le.gr...@me.com wrote:

Hi Joost,


On 13.09.2012 15:43, Joost Andrae wrote:


Hi Armin,

I can still reproduce the behavior described:

Open eg.
http://openclipart.org/detail/172011/racing-helmet-by-gnokii-172011 in
Firefox and drag the SVG file to the Gallery in AOO. On my system (Win7
Pro 64 Bit) the resulting Gallery entry is a BMP file.



It is also a bitmap file when dragging it to Inkscae. This is because the
DD contains a bitmap already. To get the svg file, you need to right-click
on the helmet and use 'save link as' and save it somewher. From there, you
can drag the real SVG.

HTH!



Joost wrote somewhere in this thread that SVG dropped to the gallery is
converted to bitmap formats. I checked this and it is not true.

When using a SVG from the gallery and svaing the document, I checked the
SVG embedded into the ODF format - it's exactly (byte by byte) the
original SVG I was dropping to the gallery.

Works as intended/expected.



Kind regards, Joost





Hi Armin,

Do you know why drag and drop of files from the Nautilus filer to the
gallery works with complex svg with embeded bitmaps but not odg?

No, sorry. I'm not in the code, just tried myself with SVG and found out 
by experiment that it does not work directly. No idea about odg, but 
somewhere in the code fo rthe gallery there must be a file type detection.


Sincerely,
Armin
--
ALG


Re: Clipart library

2012-09-13 Thread Armin Le Grand

Hi Joost,

On 13.09.2012 15:43, Joost Andrae wrote:

Hi Armin,

I can still reproduce the behavior described:

Open eg.
http://openclipart.org/detail/172011/racing-helmet-by-gnokii-172011 in
Firefox and drag the SVG file to the Gallery in AOO. On my system (Win7
Pro 64 Bit) the resulting Gallery entry is a BMP file.


It is also a bitmap file when dragging it to Inkscae. This is because 
the DD contains a bitmap already. To get the svg file, you need to 
right-click on the helmet and use 'save link as' and save it somewher. 
From there, you can drag the real SVG.


HTH!


Joost wrote somewhere in this thread that SVG dropped to the gallery is
converted to bitmap formats. I checked this and it is not true.

When using a SVG from the gallery and svaing the document, I checked the
SVG embedded into the ODF format - it's exactly (byte by byte) the
original SVG I was dropping to the gallery.

Works as intended/expected.



Kind regards, Joost





Re: Problems with axial gradient and low color steps

2012-09-13 Thread Armin Le Grand

Hi Regina,

On 13.09.2012 22:43, Regina Henschel wrote:

Hi Armin,

comments inline.

Armin Le Grand schrieb:

Hi Regina,

On 08.09.2012 21:27, Regina Henschel wrote:

Hi Armin,

Armin Le Grand schrieb:

 Hi Regina,

On 06.09.2012 21:35, Regina Henschel wrote:

Hi all,

I see a lot of problems with axial gradients, but I'm not sure about
the
desired behavior.
Please have look at attachment
https://issues.apache.org/ooo/attachment.cgi?id=79324 in bug
https://issues.apache.org/ooo/show_bug.cgi?id=120604

Problem (1): How many color steps has an axial gradient, if the user
set
it to n steps in the UI? Old versions (SO5.2 to at least OOo2.4.3)
make
it in n steps, with n/2 steps blending color up and n/2 steps
blending
color down. Around OOo3.2.1 this behavior was changed so that (n-1)
steps up, 1 step in the middle and (n-1) steps down. In AOO we have
now (n-1) steps up and (n-1) steps down. The ODF does not specify
it.


How many stripes should the shape show, if the user sets the step count
to 5 ?
5 - old behavior, does not fit at all
8 - behavior in 3.4.1 and 3.5
9 - behavior in 3.2.1, only one middle strip
10 - I would prefer this; as in 3.2.1, but with double middle strip


I agree. I first thought about 9, but 10 is the exactly once mirrored
behaviour of 'linear'. Do we have a task for it?



I have written https://issues.apache.org/ooo/show_bug.cgi?id=120604.


Okay, I can use that.





Problem (2): What colors should the steps have? In the old version the
colors for up and down where different, what I think has been a
bug.


Yes. Also the step count was wrongly interpreted. There are numerous
errors in the old, VCL-based gradient painters.


In AOO 3.4.1 version neither the start not the end color is used, only
values between.


Start and end color should be used (if visible). In the Yellow/Green
example this seems to be okay.


Compare it with pure color green and pure color yellow and compare it
with a linear gradient with green - yellow and linear gradient with
yellow - green.

The linear gradient includes the start color and excludes the end color.
(I think that it would be better the other way round, because the start
color can be included via border. But that is a different problem.)

The axial gradient has neither start nor end color.


I see this both as errors. Start and end color should always be used. Do
we have tasks for this?



I think, that it can be handled together in
https://issues.apache.org/ooo/show_bug.cgi?id=120604, because it is all
in the same file.


Okay, agreed.






Problem (3): The old gradients are still used for presentation mode,


AFAIK presentation has its own gradient rendering, targeted at
system-specific canvases. If redoing this, it sould use the primitives
directly (one day). It's an export.


converting to bitmap,


Should use primitives nowadays. If not, should be changed to do so.


Indeed, that is fixed in AOO3.5. It is correct for export to png and jpg
too in AOO3.5.

Copy and Save as GDI metafile is better in AOO3.5 than in AOO3.4.1.
The gradient is the same as for the shape and the gradient rotates
together with the shape, as expected for a picture. But 'Break' and
'Convert to bitmap' are wrong. 'Convert to bitmap' looses the rotation
which comes from the shape rotation and 'Break' looses the step count in
addition. But that is not specific for axial gradient.




export to pdf


Yes, is based on and 'paints' metafiles (but not with the VCL
mechanisms). It's an export and should be changed to primitive usage
one
day.


Mh. If I export it to pdf using my build with my changes in
OutputDevice::ImplDrawLinearGradient, I can see exact this changes.


Okay, so export to metafile uses OutputDevice::ImplDrawLinearGradient.




and flash.


Not sure about this, also an export.


I think, that needs to be
fixed. I have looked around, and think, that it is in
OutputDevice::ImplDrawLinearGradient in
\main\vcl\source\gdi\outdev4.cxx. Is that right? If yes, are other
places effected as well? Should it be fixed or is someone working on a
more general solution?


It *could* be fixed there if really used. Have You tried to set breaks
(pr fprintfs) to check this? Most usages should not use it.


No. I have changed the colors and steps in
OutputDevice::ImplDrawLinearGradient and can see those changes using the
resulting build.


Good.



If it is used, it could be made to work using temp primitives
internally
to ensure equal rendering.


As far as I have tested, OutputDevice::ImplDrawLinearGradient is used in
presentation mode, export to pdf, swf, emf, and wmf. The exports to png
and jgp are OK in AOO3.5. I havn't tested other formats.



For all exports which are nowadays still based on metafiles the
solution
should be to rewrite/modify these exports to be based on primitives in
the future.



Do I understand you correct, that you think, it is not worth to correct
OutputDevice::ImplDrawLinearGradient? But the effort should be to make
it totally superfluous?


No. I

Re: Problems with axial gradient and low color steps

2012-09-12 Thread Armin Le Grand

Hi Regina,

On 08.09.2012 21:27, Regina Henschel wrote:

Hi Armin,

Armin Le Grand schrieb:

 Hi Regina,

On 06.09.2012 21:35, Regina Henschel wrote:

Hi all,

I see a lot of problems with axial gradients, but I'm not sure about the
desired behavior.
Please have look at attachment
https://issues.apache.org/ooo/attachment.cgi?id=79324 in bug
https://issues.apache.org/ooo/show_bug.cgi?id=120604

Problem (1): How many color steps has an axial gradient, if the user set
it to n steps in the UI? Old versions (SO5.2 to at least OOo2.4.3) make
it in n steps, with n/2 steps blending color up and n/2 steps blending
color down. Around OOo3.2.1 this behavior was changed so that (n-1)
steps up, 1 step in the middle and (n-1) steps down. In AOO we have
now (n-1) steps up and (n-1) steps down. The ODF does not specify
it.


How many stripes should the shape show, if the user sets the step count
to 5 ?
5 - old behavior, does not fit at all
8 - behavior in 3.4.1 and 3.5
9 - behavior in 3.2.1, only one middle strip
10 - I would prefer this; as in 3.2.1, but with double middle strip


I agree. I first thought about 9, but 10 is the exactly once mirrored 
behaviour of 'linear'. Do we have a task for it?




Problem (2): What colors should the steps have? In the old version the
colors for up and down where different, what I think has been a bug.


Yes. Also the step count was wrongly interpreted. There are numerous
errors in the old, VCL-based gradient painters.


In AOO 3.4.1 version neither the start not the end color is used, only
values between.


Start and end color should be used (if visible). In the Yellow/Green
example this seems to be okay.


Compare it with pure color green and pure color yellow and compare it
with a linear gradient with green - yellow and linear gradient with
yellow - green.

The linear gradient includes the start color and excludes the end color.
(I think that it would be better the other way round, because the start
color can be included via border. But that is a different problem.)

The axial gradient has neither start nor end color.


I see this both as errors. Start and end color should always be used. Do 
we have tasks for this?





Problem (3): The old gradients are still used for presentation mode,


AFAIK presentation has its own gradient rendering, targeted at
system-specific canvases. If redoing this, it sould use the primitives
directly (one day). It's an export.


converting to bitmap,


Should use primitives nowadays. If not, should be changed to do so.


Indeed, that is fixed in AOO3.5. It is correct for export to png and jpg
too in AOO3.5.

Copy and Save as GDI metafile is better in AOO3.5 than in AOO3.4.1.
The gradient is the same as for the shape and the gradient rotates
together with the shape, as expected for a picture. But 'Break' and
'Convert to bitmap' are wrong. 'Convert to bitmap' looses the rotation
which comes from the shape rotation and 'Break' looses the step count in
addition. But that is not specific for axial gradient.




export to pdf


Yes, is based on and 'paints' metafiles (but not with the VCL
mechanisms). It's an export and should be changed to primitive usage one
day.


Mh. If I export it to pdf using my build with my changes in
OutputDevice::ImplDrawLinearGradient, I can see exact this changes.


Okay, so export to metafile uses OutputDevice::ImplDrawLinearGradient.




and flash.


Not sure about this, also an export.


I think, that needs to be
fixed. I have looked around, and think, that it is in
OutputDevice::ImplDrawLinearGradient in
\main\vcl\source\gdi\outdev4.cxx. Is that right? If yes, are other
places effected as well? Should it be fixed or is someone working on a
more general solution?


It *could* be fixed there if really used. Have You tried to set breaks
(pr fprintfs) to check this? Most usages should not use it.


No. I have changed the colors and steps in
OutputDevice::ImplDrawLinearGradient and can see those changes using the
resulting build.


Good.



If it is used, it could be made to work using temp primitives internally
to ensure equal rendering.


As far as I have tested, OutputDevice::ImplDrawLinearGradient is used in
presentation mode, export to pdf, swf, emf, and wmf. The exports to png
and jgp are OK in AOO3.5. I havn't tested other formats.



For all exports which are nowadays still based on metafiles the solution
should be to rewrite/modify these exports to be based on primitives in
the future.



Do I understand you correct, that you think, it is not worth to correct
OutputDevice::ImplDrawLinearGradient? But the effort should be to make
it totally superfluous?


No. I appreciate and (more than) welcome when you correct the behaviour 
in OutputDevice::ImplDrawLinearGradient. This is the only (and probably 
best) short-term solution.


I just wanted to say that - if it would be a lot of work - it may be 
worth to think about fixing it by migragting more exporters to primitive 
usage. Doing so would in the optimal canse make

Re: Clipart library

2012-09-12 Thread Armin Le Grand

Hi,

just wanted to mention: I just tried it out, SVG graphics can now be 
part of the existing gallery due to the added SVG import support. DD 
SVG into gallery theme works like a charm. Thus, all SVG cliparts can be 
added to whatever form of clipart extension/builtin.


On 30.08.2012 16:51, Ian Lynch wrote:t

I'm organising the Open clipart library into categories. We could use
this then as a useful resource to complement AOO. Any thoughts about
the best way to implement making the categorised library available to
the community?





Re: Clipart library

2012-09-12 Thread Armin Le Grand

Hi,

Joost wrote somewhere in this thread that SVG dropped to the gallery is 
converted to bitmap formats. I checked this and it is not true.


When using a SVG from the gallery and svaing the document, I checked the 
SVG embedded into the ODF format - it's exactly (byte by byte) the 
original SVG I was dropping to the gallery.


Works as intended/expected.

On 12.09.2012 14:42, Armin Le Grand wrote:

Hi,

just wanted to mention: I just tried it out, SVG graphics can now be
part of the existing gallery due to the added SVG import support. DD
SVG into gallery theme works like a charm. Thus, all SVG cliparts can be
added to whatever form of clipart extension/builtin.

On 30.08.2012 16:51, Ian Lynch wrote:t

I'm organising the Open clipart library into categories. We could use
this then as a useful resource to complement AOO. Any thoughts about
the best way to implement making the categorised library available to
the community?








Re: Problems with axial gradient and low color steps

2012-09-07 Thread Armin Le Grand

Hi Regina,

On 06.09.2012 21:35, Regina Henschel wrote:

Hi all,

I see a lot of problems with axial gradients, but I'm not sure about the
desired behavior.
Please have look at attachment
https://issues.apache.org/ooo/attachment.cgi?id=79324 in bug
https://issues.apache.org/ooo/show_bug.cgi?id=120604

Problem (1): How many color steps has an axial gradient, if the user set
it to n steps in the UI? Old versions (SO5.2 to at least OOo2.4.3) make
it in n steps, with n/2 steps blending color up and n/2 steps blending
color down. Around OOo3.2.1 this behavior was changed so that (n-1)
steps up, 1 step in the middle and (n-1) steps down. In AOO we have
now (n-1) steps up and (n-1) steps down. The ODF does not specify it.

Problem (2): What colors should the steps have? In the old version the
colors for up and down where different, what I think has been a bug.


Yes. Also the step count was wrongly interpreted. There are numerous 
errors in the old, VCL-based gradient painters.



In AOO 3.4.1 version neither the start not the end color is used, only
values between.


Start and end color should be used (if visible). In the Yellow/Green 
example this seems to be okay.



Problem (3): The old gradients are still used for presentation mode,


AFAIK presentation has its own gradient rendering, targeted at 
system-specific canvases. If redoing this, it sould use the primitives 
directly (one day). It's an export.



converting to bitmap,


Should use primitives nowadays. If not, should be changed to do so.


export to pdf


Yes, is based on and 'paints' metafiles (but not with the VCL 
mechanisms). It's an export and should be changed to primitive usage one 
day.



and flash.


Not sure about this, also an export.


I think, that needs to be
fixed. I have looked around, and think, that it is in
OutputDevice::ImplDrawLinearGradient in
\main\vcl\source\gdi\outdev4.cxx. Is that right? If yes, are other
places effected as well? Should it be fixed or is someone working on a
more general solution?


It *could* be fixed there if really used. Have You tried to set breaks 
(pr fprintfs) to check this? Most usages should not use it.


If it is used, it could be made to work using temp primitives internally 
to ensure equal rendering.


For all exports which are nowadays still based on metafiles the solution 
should be to rewrite/modify these exports to be based on primitives in 
the future.



Kind regards
Regina




Sincerely,
Armin
--
ALG


Re: Duplicate code in module binfilter [was: Re: svn commit: r1379349 - in /incubator/ooo/trunk/main: offapi/com/sun/star/sheet/ offapi/type_reference/ oox/inc/oox/xls/ oox/source/xls/ sc/inc/ sc/sour

2012-09-07 Thread Armin Le Grand

Hi Andrew,

On 06.09.2012 14:45, Andrew Douglas Pitonyak wrote:


On 09/06/2012 12:41 AM, Juergen Schmidt wrote:


snip



Nevertheless do we have to look forward and should drop really old
stuff that makes more problems and blocks innovation than it helps.

Juergen

OK, thanks I will be intentional about finding older files and
converting them to a newer format soon. Older versions may be available,
but that assumes that the older versions will still run on the newer
platforms; which is not always the case.

Yes, I understand the reasons and will be able to help spread the word
(as it were). :-)



The binfilters and thus the old binary import/exports really are at EOL:

- It's an undocumented, non-open proprietary binary format (normally 
people complain about this loudly)
- All versions of AOO/SO/LO/Symphony since ODF1.0 support until today on 
all systems can be used to convert still existing old files (put a copy 
of your favourite office besides your old files; why archive only files?)
- Binfilter code is not really 'updated' and thus maybe/is open to known 
vulnerabilities
- As a preparation step, export to the old formats is deactivated since 
some time (no complains so far, thus not really used)
- Old formats get no new data format extensions; they can only hold 
something similar to ODF1.0. Newer features/data will be lost in transfer.
- Speed: Do not forget, for loading an old format, it is completely 
imported to an old core in binary format, exported to ODF1.0, converted 
to ODF1.2 and impotrted. Same for export, but vice-versa.

- Build environment/build time: Don't ask, it's a nightmare sometimes.
- As Juergen said: It's not free just to keep it around (as many think), 
it needs to be supported. New compilers, new systems, warning-free code, 
data types, ... Wouldn't it be better to set ressoures on new stuff...?


There are more, just a list from my mind...

Sincerely,
Armin
--
ALG


Re: [VOTE] Apache OpenOffice Community Graduation Vote

2012-08-20 Thread Armin Le Grand

+1, let's go!

Sincerely,
Armin

On 19.08.2012 17:52, Rob Weir wrote:

Per the IPMC's Guide to Successful Graduation [1] this is the
optional, but recommended, community vote for us to express our
willingness/readiness to govern ourselves.  If this vote passes then
we continue by drafting a charter, submitting it for IPMC endorsement,
and then to the ASF Board for final approval.   Details can be found
in the Guide to Successful Graduation.

Everyone in the community is encouraged to vote.  Votes from PPMC
members and Mentors are binding.  This vote will run 72-hours.


[ ] +1  Apache OpenOffice community is ready to graduate from the
Apache Incubator.
[ ] +0 Don't care.
[ ] -1  Apache OpenOffice community is not ready to graduate from the
Apache Incubator because...


Regards,

-Rob

[1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote






Re: Quickstarter

2012-08-10 Thread Armin Le Grand

Hi,

On 09.08.2012 09:38, Andre Fischer wrote:

Hi,

I am currently testing a fix for showstopper bug 120476.  I am doing
this on a 64 bit Ubuntu 12.04 (building install sets is an order of
magnitude faster than on windows.)  During that I observed a hang when
closing the office.  It is caused by the quickstarter: starting
OpenOffice with the command line option -quickstart=no lets me close the
office cleanly.

Now my question: did we activate the quickstarter on Linux on purpose?
If so, we may have a small problem at least on Ubuntu 12.04 and probably
on any Linux that uses a GTK based UI that is not Gnome-2: I have no
quickstarter button anywhere on the screen, that would a) indicate that
the quickstarter is active and that b) would allow me to deactivate it.

Regards,
Andre



Uhh, sounds like lots of system-dependent problems, even 
distrubution-dependent and desktop-manager dependent, and there, 
version-dependent probably.


I want to remind on the 'Should quickstarter be enabled or disabled by 
default?' discussion where we also discussed to completely remove it.


When it seems that the only advantage is on windows and for starting AOO 
after reboot and during the first (3-5) minutes I want to repeat the 
suggestion to remove it.


It's a problem that should be left to the instance which could best 
solve it: The systems which get smarter and faster every day.


Of course we should also do what is possible to make the first start 
experience better, but as Joost hinted in the discussion, there may be 
better possibilities today for the windows case; maybe the quickstart 
solution (whic was done when first startup took between 30-45 seconds) 
is not the best anymore.


(I also remember to have heard that Mozilla solves the problem by 
linking all libs to a single executable, is that true? Nothing I want to 
suggest, just curious.)


As can be seen, it has costs to keep it; we need people with 
system-specific knowledge and knowledge about quickstarter to keep it 
alive and to fix bugs there.


Just my 2 cent...

Sincerely,
Armin
--
ALG



Re: ODF angle problems continued

2012-08-09 Thread Armin Le Grand

Hi Regina,

good to start that. The definitions for draw:transform are correct AFAIS.

Concerning the coordinate system mess:

The two possible orientations of coordinate system are needed when you 
want to define 'clockwise' and 'counter-clockwise'.


Instead, speaking about 'positive orientation' and 'negative 
orientation' in the mathematical sense is independent from the 
orientation where mathematical 'positive orientation' means (in both 
cases) that the rotation starts on (1,0), goes through the first 
quadrant and ends at (0,1).


I would use the independent description. Together with the information 
that AOO uses (in all 2D cases) the screen orientation the result is 
that 'positive orientation' goes 'clockwise'.


This definitions are missing and adding them will be fine. They still do 
not describe the existing problem with angles (except the ones in 
draw:transform and 3D). They are numerically *mirrored*, independent 
from the definition of the orientation.


Thus the current state:
- Screen orientation is used in core, api and odf
- mathematically correct 'positive orientation' goes 'clockwise'
- draw:angle is 'wrong' because it is numerically mirrored, it goes 
'counter-clockwise', but resides in the same orientation


Example: draw:angle(300) (in 0.1 degrees, another problem, independent 
from orientation) is not for lines, but *if* applied to a line from 
(0,0) to (1,0) on the X-Axis the line would be rotated 30 degrees 
anti-clockwise (!) in the current offic(es). The line will point from 
bottom-left to up-right.


To get what you want (and what would be mathematically correct with the 
given definitions), an angle of -300 (or 3300 what is 3600 - 300) has to 
be used.


Example the other way around: A line from (0,0) to (1,1), thus from 
top-left to bottom-right on screen *should* have a rotation value of 45 
degrees. The API value for rotation (do not know the exact name right 
now) will not give you 450, but 3150, which is 3600-450. ARGH!


Thus the error(s) with draw:angle are:
- It's in 10th of degrees and not documented as that
- It's numerically mirrored, *independent* from the orientation

On 09.08.2012 15:39, Regina Henschel wrote:

Hi all,

I have written a mail to OASIS, that I think that a lot of angle
definitions are not clear enough. It seems that the committee is willing
to discuss the problem. I have therefore started with section 19.228
draw:transform in spec ODF 1.2 part 1.

You find my concerns and suggestions on
http://wiki.services.openoffice.org/wiki/User:Regina/MYDrafts4.

I plan to show that to the OASIS committee. But first I like to know
your ideas. So please have a look.

Kind regards
Regina






Re: ODF angle problems continued

2012-08-09 Thread Armin Le Grand

Hi Regina,

one more note: Translate is missing in your description...

On 09.08.2012 15:39, Regina Henschel wrote:

Hi all,

I have written a mail to OASIS, that I think that a lot of angle
definitions are not clear enough. It seems that the committee is willing
to discuss the problem. I have therefore started with section 19.228
draw:transform in spec ODF 1.2 part 1.

You find my concerns and suggestions on
http://wiki.services.openoffice.org/wiki/User:Regina/MYDrafts4.

I plan to show that to the OASIS committee. But first I like to know
your ideas. So please have a look.

Kind regards
Regina






Re: Definition of draw:angle in ODF1.2 does not fit to implementation

2012-08-02 Thread Armin Le Grand

Hi Dennis (and others),

On 01.08.2012 20:38, Dennis E. Hamilton wrote:

Hi Armin,

Thanks for your valuable comment.

I had thought that the description using clockwise was in reference to the page 
appearance and not the abstract treatment (with right-hand rule).  Perhaps I 
misunderstand where the origin is understood in the projection onto the page.


I do not think that you misunderstand. The X-Axis points to the right, 
the Y-Axis down, the origin is top-left (pretty standard, expected by 
everyone). Thus, mathematically, the positive orientation of angles goes 
clockwise.


Unfortunately someone did define it 'mirrored' in the cores for 
StarOffice (maybe more than 15 years ago), is used in the UI and this 
was copied to the UNO API and the ODF format for all angles (independent 
from usage for gradients or objects). This is not based on using the 2nd 
possible coordinate system with Y-Axis pointing up, but simply by using 
the 'wrong' (mirrored) values for angles throughout the office consequently.



MORE IMPORTANT CONCERN

I think you raise a more important question concerning changing for ODF 1.3 and 
understanding a transformation between ODF 1.0/1.1/1.2/IS 26300 and ODF 1.3.

I recommend that there be no breaking change of draw:angle between ODF 
versions.  It is probably best to deprecate it while clarifying the orientation 
of the angle-opening rotation and the units of the angle.  I think preventing 
down-level breakage is impossible without that and the support explanations 
will be a nightmare otherwise.  It seems to me that the ODF 1.2 description is 
best corrected in an Errata and the problem made immediately known in an OIC 
Advisory.


My first idea was to define the orientation (is not really defined now) 
for ODF1.2 and older, and to define it mirrored for ODF1.3, applying a 
xslt transformation to manage that.


You are right that for all products not immediately applying to this 
change rotations would break. This would speak for adding a new property.



To correct the geometry for transformations, I suggest that another, 
rigorously-defined gradient element be introduced, preferably one from SVG.


Transformations are okay and need no change, they contain the angle 
corresponding to the coordinate system.


As Michael Stahl wrote, svg:linearGradient and svg:radialGradient are 
already part of ODF1.2.


These are no replacement for draw:gradient, thus are no candidates for 
deprecating the draw:gradient (and draw:opacity, the transparence 
gradients) for ODF1.3. It is another kind of gradient with the pros and 
cons described by Michael Stahl.


(BTW: What to do if an object has draw:gradient AND svg:linearGradient 
defined at the same time (or even more, add svg:radialGradient)...?).


We should not mix up varios themes here (maybe I started doing so, I 
apologize). We have two things here:


(a) Non-SVG Gradient definitions (old ones)
(b) Angle definitions in various places

There is no general problem with (a), except the contained angle and 
it's orientation. Thus I talk more about (b) where (b) is about the old 
gradients with use draw:angle currently, but also start/end angles in 
circle/ellipse shapes.


The Object rotation does not have a direct and single rotation attribute 
(AFAIK, there is svg:x, svg:y, svg:width/height, but no svg:angle), but 
has to use (and does use) a transformation when rotation is needed 
(which uses angles correctly, no problem there).


Using a 2nd 'rigorously-defined' angle would be sufficient here. As 
mentioned in earlier mails, SVG has angle as basic data type (see SVG 
4.2). It is already listed in ODF 1.2, see 18.3.1 of ODF spec (Does this 
mean it could already be used?). It is even referenced as data type in 
draw:angle, draw:start-angle and draw:end-angle (!), see e.g. 19.112 
draw:angle in ODF1.2 which says: 'The draw:angle attribute has the data 
type angle 18.3.1'. When this would be true, draw:angle would not even 
be needed since it's identical to svg:angle already (which it is not, 
another error?).


Thus I suggest allowing both in draw:gradient and draw:opacity, with

---

draw:angle is the inverted rotation in 10th of a degree as integer 
value (no longer reference 18.3.1 and say it's equal).


svg:angle is the rotation as defined by SVG (including being float and 
supporting deg, rad and grad).


If svg:angle is present, it has precedence over draw:angle. For 
compatibility, please support both when creating ODF documents.


---

Other candidates wit this problem are (not sure when marked with '?'):

19.140 draw:end-angle
19.213 draw:start-angle

19.226 draw:text-rotate-angle (?)
20.95 draw:caption-angle (?)
20.339 style:rotation-angle (?)
20.375 style:text-rotation-angle (?)


If there is a down-level concern, I would define the new element such that, when it and 
draw:gradient are both present, the new element pre-empts draw:gradient in ODF 
1.3 and beyond.  This way, a down-level implementation will presumably

Re: Help me

2012-08-02 Thread Armin Le Grand
Hi all,

maybe we should add a 'Repair' entry to the Help menu which does that
deletion (after showing a warning and asking the user to press 'okay'? This
problem came up several times now.

Sorry for top posting, just a short suggestion...

Ji Yan yanji...@gmail.com wrote:
 Hi Jonathan,
 
 Try to delete the file org.openoffice.script.savedState. It is located
 this folder: /Users/user name/Library/Saved Application State
 The user/library folder is hidden in Lion. You can open it by Go- Go menu
 ~/Library
 
 2012/8/2 Jonathan Lee jonathan@hattengrp.com
 
 Dear All,
 
 I am headache with this problem now. can you help me to solve it ? thanks
 a lot…
 I click either one also no response.
 
 
 
 
 
 
 
 Thanks amp; Regards
 
 
 Jonathan Lee
 *Senior Graphic Designer - Aamp;P*
 *Hatten Group Sdn. Bhd.**
 *Office: +606-282 1828 *|* Fax: +606-283 1827
 Email: jonathan@hattengrp.com sin.shauk...@hattengrp.com *| *
 Website: www.hattengrp.com
 F3-96 *|* Hatten Square *| *Jalan Merdeka *|*
 
 Bandar Hilir *|* 75000 **Melaka**, **Malaysia**
 *Excellence in Growth*
 
 WARNING: This email may contain privileged and confidential information.
 If you receive this email by mistake, you should immediately notify the
 sender and delete the email. Unauthorised communication and disclosure of
 any information in the email is an offence.
 
 *P Please consider the environment before printing.*
 
 
 
 --
 
 Thanks amp; Best Regards, Yan Ji


-- 
ALG



Re: Definition of draw:angle in ODF1.2 does not fit to implementation

2012-08-01 Thread Armin Le Grand

Hi Dennis,

On 30.07.2012 22:21, Dennis E. Hamilton wrote:

There appear to be three considerations:

  1. What is type and unit of draw:angle in the draw:gradient element?
 In ODF 1.0, ODF 1.1, and ISO/IEC 26300:2006 (now aligned with ODF 1.1), 
the type is integer and there is no explanation of the scale of the unit.  ODF 
1.2 gives special attention to the integer case and observes that the unitless 
integer is all that works for down-level compatibility with ODF 1.1 consumers.

 If it is to be decreed that all/most implementations are correct and the 
specification has been left incorrect since 2005, that is a very difficult 
situation.  I assume the correct statement is that the unit for draw:angle is 
0.1 degree.

  2. Orientation?
 The orientation leaves much to be described, since it is a vector that is 
rotated, not an axis.  It appears that practice and what little is said in the 
specifications satisfy standard geometric practice, as follows:

 a. Consider a vector that lies along the X axis with orientation in the 
positive-X direction.
 b. A positive rotation of that vector by 90 degrees will place the vector 
along the Y axis with the positive-X points now at the same positions on the 
positive-Y axis, etc.  The draw-angle will be 90 degrees (however expressed).
 c. More generally, the angle is that of the positive-gradient vector (from 
the origin) with the positive-X vector (from the origin), as measured from the 
positive-X vector rotating toward (and through, if necessary) the positive-Y 
vector direction.

(This is anti-clockwise in the standard geometric orientation.  When projected 
onto the page, this appears to be clockwise because the origin tends to be in 
the upper left corner and the positive-Y direction is downward, the positve-X 
direction is rightward.)


It is consistent throughout all AOO/LO/OOo versions. Unfortunately, it 
is mathematically wrong oriented (thus, projected on the page, 
anti-clockwise).


Thus, when just want to stay compatible and extend/correct the 
definitions, defining it as integer, 0.1 degrees and mathematically 
(non-projected to page) clockwise rotation would describe the current 
behaviour.


Unfortunately this 'wrong' orientation is problematic. As long as it is 
only locally used it can simply be mirrored. The problem comes up when 
working with transformations; when receiving the transformation of an 
graphic object and decomposing it to extract rotation, that rotation 
will be mathematically correctly oriented. It has to be since else 
linear combination of transformations would not work.


This is not in the environment of gradients, but in general all angles 
in ODF have this problem (probably for historical reasons, the UIs use 
the same wrong orientation). Our competitor does not have that error.


Isn't this correctable for all angles e.g. for ODF1.3 and can be handled 
by a XML transformation ODF1.2 - ODF1.3 by mirroring all angle values 
easily? If yes, Shouldn't we take the chance to clean this up in ODF1.3?



I suspect this can be clarified easily in all of ODF 1.0 through ODF 1.2, since 
there seems to be no conflict with implementations.  Conversions to and from 
other formats need to be attentive to any difference in the reference 
orientation of axes and definition of the angle.

  3. Non-Integer Types and Values?

Allowing fractional values and units in draw:angle seems to be problematic and 
it does not directly deal with the integer type expression of 0.1-degree 
intervals.

I agree that should be done by switching to SVG cases when available (and there 
should be more alignment of that in ODF 1.3).

This means that draw:angle should probably continue to be expressed in plain 
integers with a clarification that the unit is 0.1-degrees.

That would at least limit the damage of this persistent discrepancy between 
practice and the specification.

  - Dennis

-Original Message-
From: Regina Henschel [mailto:rb.hensc...@t-online.de]
Sent: Monday, July 30, 2012 11:29
To: ooo-dev@incubator.apache.org
Subject: Re: Definition of draw:angle in ODF1.2 does not fit to implementation

[ ... ]

Using decimals or using units will be an incompatible change. Neither of
AOO, LO or MSO accept decimals or units. But the real problem is not the
type, but the fact, that currently a stored value of 300 is interpreted
as 30deg which is different from the spec.

   I would rather suggest to go with the SVG

definition and propose that. It's always good to get closer to other
graphic standards.


In general I would say yes. But wouldn't it better to leave
draw:gradient in our implementation as it is and implement for double
precision and for all the other nice features like multiple stop colors
svg:linearGradient and svg:radialGradient ? Those are already in the spec.



It also needs to be evaluated to which orientation The axis of
the gradient is specified with the draw:angle attribute clockwise to the

Re: trunk build fails, likely in python

2012-08-01 Thread Armin Le Grand

Hi Pedro,

after updating I can build again, Yay!
Thanks.

Sincerely,
Armin

On 31.07.2012 17:32, Pedro Giffuni wrote:

Thank you Tsutomu!

The other patches should also be used. I am not sure if dmake supports
the += operator so I just went back to the old patching method on
revision  1367616.

This is hopefully the last change there. Sorry to take you guys
as guinea pigs ;).

Pedro.





From: Tsutomu Uchino hanya.r...@gmail.com
To: ooo-dev@incubator.apache.org
Sent: Tuesday, July 31, 2012 8:57 AM
Subject: Re: trunk build fails, likely in python

Hi,

2012/7/31 Regina Henschel rb.hensc...@t-online.de:

Hi Pedro,

I still cannot build Python.

Messages are:
dmake:  Warning: -- Found file corresponding to virtual target
[./wntmsci12/misc/build/Python-2.7.3/PC/pyconfig.h].


Build started: Project: _ssl, Configuration: Release|Win32
Performing Pre-Build Event...
Can not find a suitable PERL:
   the following perl interpreters were found:
C:\cygwin\bin\perl.exe
   None of these versions appear suitable for building OpenSSL
   Please install ActivePerl and ensure it appears on your path
No Perl installation was found. Existing Makefiles are used.
Could not find an SSL directory in '('..\\..',)'
Project : error PRJ0019: A tool returned an error code from Performing
Pre-Build Event...

Project : warning PRJ0018 : The following environment variables were not
found:
$(UPDMINOREXT)

Kind regards
Regina


Pedro Giffuni schrieb:


Committed as Revision 1367398 . Please test.

Hopefully I learned from the error that Regina reported to
cleanup better the code.

Pedro.





From: Pedro Giffuni p...@apache.org
To: ooo-dev@incubator.apache.org ooo-dev@incubator.apache.org
Sent: Monday, July 30, 2012 8:34 PM
Subject: Re: trunk build fails, likely in python

Thank you.

I will use this as an opportunity to do some further cleanup

Pedro.





From: Lin Yuan yuanlin@gmail.com
To: ooo-dev@incubator.apache.org
Sent: Monday, July 30, 2012 8:26 PM
Subject: Re: trunk build fails, likely in python

I can reproduce this issue on my Win 7.
In Python-2.7.3\PCbuild\pcbuild.sln, there are two projects related to
sqlite3. One named sqlite3. Another named _sqlite3.  Both of them
need
to be remarked. But in python-2.7.3.patch, it only remark project
sqlite3. Need also remark project _sqlite3 in pcbuild.sln.

2012/7/31 Regina Henschel rb.hensc...@t-online.de


Hi Armin,

I have rebased and deleted all the wbtmsci12*, then started a new
build. I
now get the same error as you.

Kind regards
Regina

Armin Le Grand schrieb:

 Hi,



just checked out current version and build stopped in python (win7).
Message is as follows.

Where does sqlite3.h come from? There is a folder
main\python\wntmsci12\misc\**build\Python-2.7.3\Doc\**includes\sqlite3
but
no sqlite3.h in there. Should it be there...?

Can someone help please?

--8-

c:\aoo\svn_trunk13\main\**python\wntmsci12\misc\build\**
python-2.7.3\modules\_sqlite\**connection.h(33)
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such
file
or directory
statement.c
c:\aoo\svn_trunk13\main\**python\wntmsci12\misc\build\**
python-2.7.3\modules\_sqlite\**connection.h(33)
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such
file
or directory
row.c
c:\aoo\svn_trunk13\main\**python\wntmsci12\misc\build\**
python-2.7.3\modules\_sqlite\**connection.h(33)
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such
file
or directory
module.c
c:\aoo\svn_trunk13\main\**python\wntmsci12\misc\build\**
python-2.7.3\modules\_sqlite\**connection.h(33)
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such
file
or directory
microprotocols.c
c:\aoo\svn_trunk13\main\**python\wntmsci12\misc\build\**
python-2.7.3\modules\_sqlite\**connection.h(33)
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such
file
or directory
cursor.c
c:\aoo\svn_trunk13\main\**python\wntmsci12\misc\build\**
python-2.7.3\modules\_sqlite\**connection.h(33)
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such
file
or directory
connection.c
c:\aoo\svn_trunk13\main\**python\wntmsci12\misc\build\**
python-2.7.3\modules\_sqlite\**connection.h(33)
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such
file
or directory
Build log was saved at
file://C:\aoo\svn_trunk13\**main\python\wntmsci12\misc\**

build\Python-2.7.3\PCbuild\**Win32-temp-Release\_sqlite3\**BuildLog.htm

_sqlite3 - 7 error(s), 0 warning(s)
Build started: Project: _testcapi, Configuration: Release|Win32
_testcapi - up-to-date
Build started: Project: select, Configuration: Release|Win32
select - up-to-date
Build started: Project: unicodedata, Configuration: Release|Win32
unicodedata - up-to-date
Build started: Project: pyexpat, Configuration: Release|Win32
pyexpat - up-to-date
Build started: Project: _multiprocessing, Configuration: Release|Win32
_multiprocessing

Re: trunk build breaks in qadevOOo because of missing class TextFitToSizeType

2012-07-30 Thread Armin Le Grand
Hi,

Jürgen Schmidt jogischm...@googlemail.com wrote:
 On 7/28/12 11:57 PM, Ariel Constenla-Haile wrote:
 Hi Regina,
[..]
 IMHO besides of being incomplete, they are incompatible, and thus the
 API changes should be reverted: this kind of incompatible API changes
 should happen only on mayor versions, they should wait for AOO 4; in
 the meantime, the solution seems to be:
 
 in general yes and I would agree but in this case Armin told me that the
 implementation was always different and the IDL was wrong. We did such
 changes in the past as well but always very seldom and carefully.
 
 It doesn't help to keep wrong IDL types that never have worked and were
 not really used. The mistake that was made here is to forget a clean
 build from scratch and solve all code places accordingly. That has to be
 solved.

We discussed and agreed that this case is more a bugfix, the type is used
in ODF as bool and in core, too. Sven wrote the same in his description.
Thanks Juergen for explaining here, too.

I am sorry for the hassle, I *did* a complete clean build from trunk (I
would have never dared to checkin otherwise). What I forgot is e.g.
binfilter since my default flags disable it. Sorry for that inconvenice,
I'll have a look ASAP...

 Juergen
 
 
 * Removed: 
 incubator/ooo/trunk/main/offapi/com/sun/star/drawing/TextFitToSizeType.idl
   com.sun.star.drawing.TextFitToSizeType was removed from module
 offapi but it was published API, thus it shouldn't be removed, but
 deprecated
 
 * Modified:  
 incubator/ooo/trunk/main/offapi/com/sun/star/drawing/TextProperties.idl
   The type of TextFitToSize cannot be changed because it is a
 published service, it should be tagged as deprecated, and a new
 property should be introduced instead, something like [property]
 boolean FitTextToSize; tagged as optional, because the service is
 published.
 
 In order to fix the build breaker you'll have to do more than just
 reintroduce TextFitToSizeType.idl in offapi. The removal was also
 incomplete, opengroking TextFitToSizeType shows that:
 http://opengrok.adfinis-sygroup.org/source/search?q=TextFitToSizeTypedefs=refs=path=hist=project=aoo-trunk
 
 binfilter is breaking too (this module is built by default in trunk,
 until we decide to deprecate/remove it).
 
 In file included from
 /build/aoo/src/playground/trunk/main/binfilter/bf_svx/source/unoedit/svx_unotext.cxx:71:0:
 ../../../inc/bf_svx/unoshprp.hxx:76:54: fatal error:
 com/sun/star/drawing/TextFitToSizeType.hpp: No such file or directory
 compilation terminated.
 In file included from
 /build/aoo/src/playground/trunk/main/binfilter/bf_sch/source/ui/unoidl/sch_mapprov.cxx:40:0:
 ../../../../inc/bf_svx/unoshprp.hxx:76:54: fatal error:
 com/sun/star/drawing/TextFitToSizeType.hpp: No such file or directory
 compilation terminated.
 In file included from
 /build/aoo/src/playground/trunk/main/binfilter/bf_sch/source/ui/unoidl/sch_ChXDataPoint.cxx:36:0:
 ../../../../inc/bf_svx/unoshprp.hxx:76:54: fatal error:
 com/sun/star/drawing/TextFitToSizeType.hpp: No such file or directory
 compilation terminated.
 In file included from
 /build/aoo/src/playground/trunk/main/binfilter/bf_sch/source/ui/unoidl/sch_ChXDataRow.cxx:37:0:
 ../../../../inc/bf_svx/unoshprp.hxx:76:54: fatal error:
 com/sun/star/drawing/TextFitToSizeType.hpp: No such file or directory
 compilation terminated.
 In file included from
 /build/aoo/src/playground/trunk/main/binfilter/bf_sch/source/ui/unoidl/sch_ChXChartObject.cxx:36:0:
 ../../../../inc/bf_svx/unoshprp.hxx:76:54: fatal error:
 com/sun/star/drawing/TextFitToSizeType.hpp: No such file or directory
 compilation terminated.
 In file included from
 /build/aoo/src/playground/trunk/main/binfilter/bf_sch/source/ui/unoidl/sch_ChXChartAxis.cxx:59:0:
 ../../../../inc/bf_svx/unoshprp.hxx:76:54: fatal error:
 com/sun/star/drawing/TextFitToSizeType.hpp: No such file or directory
 compilation terminated.
 dmake:  Error code 1, while making
 '../../../../unxlngx6/slo/sch_ChXDataPoint.obj'
 dmake:  Error code 1, while making '../../../unxlngx6/slo/svx_unotext.obj'
 ERROR: error 65280 occurred while making
 /build/aoo/src/playground/trunk/main/binfilter/bf_svx/source/unoedit
 ERROR: error 65280 occurred while making
 /build/aoo/src/playground/trunk/main/binfilter/bf_svx/source/svdraw
 ERROR: error 65280 occurred while making
 /build/aoo/src/playground/trunk/main/binfilter/bf_sch/source/ui/unoidl
 
 
 Regards
 


-- 
ALG



Re: trunk build breaks in qadevOOo because of missing class TextFitToSizeType

2012-07-30 Thread Armin Le Grand

Hi Regina,

On 29.07.2012 02:17, Regina Henschel wrote:

Hi Ariel,

thanks for your work. But it is not urgent for me. I can wait till it is
fixed.


Could you please quickly post the build flags here you are using? Thanks 
in advance!



Kind regards
Regina


Ariel Constenla-Haile schrieb:

HI Regina,

On Sat, Jul 28, 2012 at 8:33 PM, Regina Henschel
rb.hensc...@t-online.de wrote:

just in case you need to work and can't wait until this is fixed,
disable building binfilter and qadevOOo, this works (at least on
Linux, with a clean build).



I have already --disable-binfilter in configure.
For qadevOOo it would be --disable-qadevOOo ?


I thought it was because I don't have JUnit, but it seems this is not
the case. Although build --all in instsetoo_native finished without
errors, build in qadevOOo tries to build the module, also a build
--all in toolkit...
There used to be a --disable-qadevooo (at least I see it on
DEV300_m79), but this is gone.

You will have to comment the code in
trunk/main/qadevOOo/runner/util/ValueChanger.java
(I'll try another build, though I'm sure I cleaned the whole source
tree with dmake clean).

Regards









Re: trunk build breaks in qadevOOo because of missing class TextFitToSizeType

2012-07-30 Thread Armin Le Grand


Hi,

On 30.07.2012 15:56, Jürgen Schmidt wrote:
 On 7/30/12 2:36 PM, Ariel Constenla-Haile wrote:
 On Mon, Jul 30, 2012 at 10:08:05AM +0200, Jürgen Schmidt wrote:
[..]

 It doesn't matter what the implementation did internally, API users
 don't care about implementation details. And it is a mistake to assume
 that no API clients are using this API. In fact, it is more justified to
 asume it is being used, as it's been documented in the SDK example:
 main/odk/examples/DevelopersGuide/Drawing/TextDemo.java

 It also seems logical to assume that people read the documentation and
 follow the examples

 We did such
 changes in the past as well but always very seldom and carefully.

 But this change is *not* carefully done: the change is not tracked in
 the IDL documentation; as API user, I would expect a @deprecated tag in
 the IDL, not simple removal without further information (besides the
 Developer's Guide being updated too
 
http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Drawings/General_Drawing_Properties)



 It doesn't help to keep wrong IDL types that never have worked and were
 not really used.

 This is a wrong assumption, see the example from the SDK quoted above.
 You cannot mesure how many API users are using this API, but assuming
 that some people actually read the examples and follow them seems more
 reasonable.


 I agree and apologize to not go deeper in this special case. Under this
 circumstance I would suggest that we revert the change and document it
 in IDL. The enum has no real effect and is obsolete. We can postpone
 this incompatible change for a 4.0 if we all agree that the change in
 general make sense.

I also apologize for not checking deeper, I thought it was a simple 
cleanup/fix (see task). I think the simplest is to revert it for now, 
document the missing adaptions (which I have ready now) in the task and 
note in the API doc that all values not NONE do the same, thus not 
really being used.


Is that okay..?

 Juergen



 Regards



--
ALG




Re: trunk build fails, likely in python

2012-07-30 Thread Armin Le Grand

Hi,

just checked out current version and build stopped in python (win7). 
Message is as follows.


Where does sqlite3.h come from? There is a folder 
main\python\wntmsci12\misc\build\Python-2.7.3\Doc\includes\sqlite3 but 
no sqlite3.h in there. Should it be there...?


Can someone help please?

--8-

c:\aoo\svn_trunk13\main\python\wntmsci12\misc\build\python-2.7.3\modules\_sqlite\connection.h(33) 
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such file 
or directory

statement.c
c:\aoo\svn_trunk13\main\python\wntmsci12\misc\build\python-2.7.3\modules\_sqlite\connection.h(33) 
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such file 
or directory

row.c
c:\aoo\svn_trunk13\main\python\wntmsci12\misc\build\python-2.7.3\modules\_sqlite\connection.h(33) 
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such file 
or directory

module.c
c:\aoo\svn_trunk13\main\python\wntmsci12\misc\build\python-2.7.3\modules\_sqlite\connection.h(33) 
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such file 
or directory

microprotocols.c
c:\aoo\svn_trunk13\main\python\wntmsci12\misc\build\python-2.7.3\modules\_sqlite\connection.h(33) 
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such file 
or directory

cursor.c
c:\aoo\svn_trunk13\main\python\wntmsci12\misc\build\python-2.7.3\modules\_sqlite\connection.h(33) 
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such file 
or directory

connection.c
c:\aoo\svn_trunk13\main\python\wntmsci12\misc\build\python-2.7.3\modules\_sqlite\connection.h(33) 
: fatal error C1083: Cannot open include file: 'sqlite3.h': No such file 
or directory
Build log was saved at 
file://C:\aoo\svn_trunk13\main\python\wntmsci12\misc\build\Python-2.7.3\PCbuild\Win32-temp-Release\_sqlite3\BuildLog.htm

_sqlite3 - 7 error(s), 0 warning(s)
Build started: Project: _testcapi, Configuration: Release|Win32
_testcapi - up-to-date
Build started: Project: select, Configuration: Release|Win32
select - up-to-date
Build started: Project: unicodedata, Configuration: Release|Win32
unicodedata - up-to-date
Build started: Project: pyexpat, Configuration: Release|Win32
pyexpat - up-to-date
Build started: Project: _multiprocessing, Configuration: Release|Win32
_multiprocessing - up-to-date
Build started: Project: _ssl, Configuration: Release|Win32
Project : warning PRJ0018 : The following environment variables were not 
found:

$(UPDMINOREXT)
_ssl - up-to-date

Build complete: 18 Projects succeeded, 1 Projects failed, 1 Projects skipped
dmake:  Error code 1, while making 
'./wntmsci12/misc/build/so_built_so_python'
ERROR: error 65280 occurred while making 
/cygdrive/c/aoo/svn_trunk13/main/python


--8-

On 28.07.2012 01:33, Regina Henschel wrote:

Hi,

I start a build on WinXP with MSVC Express. It fails with error message
dmake:  Error: -- `./Python-2.7.3-vc.patch' not found, and can't be made

What do I miss?

Kind regards
Regina






Re: trunk build fails, likely in python

2012-07-30 Thread Armin Le Grand

Hmmm..

looks as if noone before built a nonpro (debug) version. Regina, you 
build without debug, right?


Looking deeper at the tipp from Tsutomu Uchino...
Thanks for the hints so far. More are of course welcome...

On 30.07.2012 18:38, Pedro Giffuni wrote:

FWIW,

One hint: googling around it looks like it's and issue when building a debug 
python.

Pedro.




[..]



Re: Definition of draw:angle in ODF1.2 does not fit to implementation

2012-07-30 Thread Armin Le Grand

Hi Regina,

On 30.07.2012 18:34, Regina Henschel wrote:

Hi all,

I want to suggest OASIS to change the definition of draw:angle. The
draft mail follows below. What do you think about it?

Kind regards
Regina

Draft of the mail to OASIS:

For draw:gradient type 'Linear' section 19.218 defines The axis of
the gradient is specified with the draw:angle attribute clockwise to the
vertical axis.
It actually means, that in the internal coordinate system (that with an
upright y-axis), rotating this y-axis clockwise with the draw:angle
gives the gradient vector.

draw:angle section 19.122 repeats this in a less exact form. For the
angle itself it specifies:
The draw:angle attribute has the data type angle 18.3.1.

And in section 18.3.1 you read, An angle, as defined in §4.1 of [SVG].
An angle is a double value that may be followed immediately by one of
the following angle unit identifiers: deg (degrees), grad (gradiants) or
rad (radians). If no unit identifier is specified, the value is assumed
to be in degrees.

But that is wrong for the implementations in Apache OpenOffice,
LibreOffice, and Microsoft Office. All of them allow in draw:angle only
integers without unit and interpret them as 0.1deg. Calligra does not
use draw:gradient but uses svg:gradient. Microsoft Office can read
negative integers, but writes itself always non negative integers.
Apache OpenOffice and LibreOffice read and write only non negative
integers.

Therefore I suggest to alter the definition of draw:angle in this way:
Instead of the sentence

The draw:angle attribute has the data type angle 18.3.1.

use the text

The draw:angle attribute has the date type integer. A value of n is
interpreted as n*0.1 degrees.


Sorry, I would not do that. This would limit the possible precision 
without needs in a format definition. If the precision in the cores is 
limited or not does not play a role for the definition (it will 
increase, we are on it). I would rather suggest to go with the SVG 
definition and propose that. It's always good to get closer to other 
graphic standards.


It also needs to be evaluated to which orientation The axis of
the gradient is specified with the draw:angle attribute clockwise to the 
vertical axis. leads. What does this mean?


The Y-Axis goes down (X to the right), thus the correct mathematical 
orientation would go anti-clockwise, starting at 0.0 on the Y-Axis which 
is below the origin. It may be wrong, the same as the current object 
rotation (and shear) is wrong in this aspect, see our current UI and 
what it does for a 5 degree object rotation (and would need to be 
proposed to be changed, too).


Thus, when we are at it, we may need to correct the orientation of 
draw:angle, too. BTW: It is correct in the MS UI and their core data. Do 
the same 5 degree rotation there.


I am currently not sure where draw:angle is used, is it the object 
rotation or the gradient rotation, or is it used for both? If used for 
both, I would not want precision to be limited to 0.1 degrees for 
objects. I would evtl. accept this for gradients.


If it is used for both, we should think about the orientation (also for 
shear)...


Sincerely,
Armin
--
ALG



Re: Definition of draw:angle in ODF1.2 does not fit to implementation

2012-07-30 Thread Armin Le Grand

On 30.07.2012 19:14, Armin Le Grand wrote:

 Hi Regina,

On 30.07.2012 18:34, Regina Henschel wrote:

Hi all,

I want to suggest OASIS to change the definition of draw:angle. The
draft mail follows below. What do you think about it?

Kind regards
Regina

Draft of the mail to OASIS:

For draw:gradient type 'Linear' section 19.218 defines The axis of
the gradient is specified with the draw:angle attribute clockwise to the
vertical axis.
It actually means, that in the internal coordinate system (that with an
upright y-axis), rotating this y-axis clockwise with the draw:angle
gives the gradient vector.

draw:angle section 19.122 repeats this in a less exact form. For the
angle itself it specifies:
The draw:angle attribute has the data type angle 18.3.1.

And in section 18.3.1 you read, An angle, as defined in §4.1 of [SVG].
An angle is a double value that may be followed immediately by one of
the following angle unit identifiers: deg (degrees), grad (gradiants) or
rad (radians). If no unit identifier is specified, the value is assumed
to be in degrees.

But that is wrong for the implementations in Apache OpenOffice,
LibreOffice, and Microsoft Office. All of them allow in draw:angle only
integers without unit and interpret them as 0.1deg. Calligra does not
use draw:gradient but uses svg:gradient. Microsoft Office can read
negative integers, but writes itself always non negative integers.
Apache OpenOffice and LibreOffice read and write only non negative
integers.

Therefore I suggest to alter the definition of draw:angle in this way:
Instead of the sentence

The draw:angle attribute has the data type angle 18.3.1.

use the text

The draw:angle attribute has the date type integer. A value of n is
interpreted as n*0.1 degrees.


Sorry, I would not do that. This would limit the possible precision
without needs in a format definition. If the precision in the cores is
limited or not does not play a role for the definition (it will
increase, we are on it). I would rather suggest to go with the SVG
definition and propose that. It's always good to get closer to other
graphic standards.

It also needs to be evaluated to which orientation The axis of
the gradient is specified with the draw:angle attribute clockwise to the
vertical axis. leads. What does this mean?

The Y-Axis goes down (X to the right), thus the correct mathematical
orientation would go anti-clockwise, starting at 0.0 on the Y-Axis which
is below the origin. It may be wrong, the same as the current object
rotation (and shear) is wrong in this aspect, see our current UI and
what it does for a 5 degree object rotation (and would need to be
proposed to be changed, too).


Argh, mixed things up. Y-Axis down, X to the right, the correct 
mathematical orientation would be clockwise starting at (1.0, 0.0) on 
the X-Axis, right of the center.
Sorry for mixing things up. Fact is that we currently use the wrong 
orinetation in our Core, UI and file format, though. Make the experiment 
with a object, rotate it by 5 degrees, do the same in MS.



Thus, when we are at it, we may need to correct the orientation of
draw:angle, too. BTW: It is correct in the MS UI and their core data. Do
the same 5 degree rotation there.

I am currently not sure where draw:angle is used, is it the object
rotation or the gradient rotation, or is it used for both? If used for
both, I would not want precision to be limited to 0.1 degrees for
objects. I would evtl. accept this for gradients.

If it is used for both, we should think about the orientation (also for
shear)...

Sincerely,
 Armin
--
ALG







Re: trunk build breaks in qadevOOo because of missing class TextFitToSizeType

2012-07-30 Thread Armin Le Grand

Hi,

On 30.07.2012 16:02, Armin Le Grand wrote:


Hi,


[..]


Is that okay..?



I have reverted the change in revision 1366087.

[..]

Sincerely,
Armin
--
ALG



Re: trunk build fails, likely in python

2012-07-30 Thread Armin Le Grand

Hi,

looks as if pcbuild.sln does not get patched at all, need to lokk 
further tomorrow.


On 30.07.2012 18:58, Armin Le Grand wrote:

 Hmmm..

looks as if noone before built a nonpro (debug) version. Regina, you
build without debug, right?

Looking deeper at the tipp from Tsutomu Uchino...
Thanks for the hints so far. More are of course welcome...

On 30.07.2012 18:38, Pedro Giffuni wrote:

FWIW,

One hint: googling around it looks like it's and issue when building a
debug python.

Pedro.




[..]



Sincerely,
Armin
--
ALG



Re: Should quickstarter be enabled or disabled by default?

2012-07-27 Thread Armin Le Grand
Hi Joost,

- Begin Message - 
Group: gmane.comp.apache.incubator.ooo.devel 
MsgID: juqstl$5ph$1...@dough.gmane.org 

Joost Andrae joost.and...@gmx.de wrote: 
 Hi Armin, 
 
 
 This would mean that it gets slower again after some time. I just did not 
 use AOO, but worked on something else ca. 1 1/2 Hrs after rebooting. 
 Nonetheless AOO started (doubleclicking the test document, no quickstarter, 
 last used after reboot) instantly. There must be some least-recently-used 
 thingy involved, I doubt that all dlls get kicked out after 10 min. Well, 
 may depend on mem available and other things, though... 
 I could not see it getting slower after 1 1/2 hours. If someone else has 
 seen this (without quickstarter, on Win) please comment here. 
 
 
 how about to use available MS VC++ addons regarding GPU computing to compile 
 AOO like MS does with its own Metro apps for Win8 ? And how about to invest 
 some development resources into adding AOO libs to Win7/Win8 system cache at 
 install time instead of using the quickstarter ? 

Interesting to hear that this is possible, thus it could be a good replacement 
for quickstarter. It would (if I understand correctly) fill the only existing 
bad scenario without quickstarter, the first start directly after system reboot.

 
 On my notebook (without HR's quickstarter) a document opens in 11 seconds 
 without using the quickstarter and it starts immediately if the office once 
 started before. (Core2Duo 2.8 Ghz, 8 GB RAM, 512 GB SSD). 

Joost, thanks for the numbers. Not too bad, I think. Compared with some years 
ago the argument for quickstarter has scaled down accordingly, I guess.

 
 Kind regards, Joost 

Sincerely,
Armin
-- 
ALG 
-- End Message -- 



--
ALG (iPad)


Re: Should quickstarter be enabled or disabled by default?

2012-07-25 Thread Armin Le Grand
Hi all,

[..]
 
 +1 for turn it off by default.
 
 About set it on the help menu, there is no relation between help
 functions and the quickstart so IMO it will be completely out of place
 there.
 
 Most users I know do not even realize that the quickstarter is running
 and in fact I cannot remember anyone using the right click menu on
 it...

Just wanted to collect pros and cons, so...

Pros:
- (p1) Faster first program start after system boot (highly
system-dependent)
- (p2) Extra context menus over quickstart icon

Cons:
- (c1) Uses system memory even when AOO is never used
- (c2) System boot takes longer
- (c3) Code complexity is higher, more stuff to maintain
- (c4) Installation problems/conflicts with running quickstarter
- (c5) Users do not know about it and what it means

If someone knows more, please add these. We should then think about the
pros and if they are worth it.

p2: I myself never used it, it's hard to say if it is used or not. The
functionality would be better placed in a system menu (e.g. start menu on
Win which tries to hold the last used app starts automatically). My guess
is that it is rarely used.

p1: I rebooted my Win7 a view times to measure (roughly) the difference.
Opening a test document with standard text as test. Version used is AOO3.4
Without quickstarter:
-booting:
-first doubleclick on document: 17 seconds
-Second doubleclick: 1 second or less
With quickstarter:
-booting: The tray icons appear asynchonously, but with the 3.4 error
(office starts) good to detect. the quickstarter boot steals some runitme
ressources (feels not responsible until fully loaded)
-first doubleclick on document: 8 seconds
-Second doubleclick: 1 second or less

I can just guess, but the quickstarter seems to load roughly half of the
libs needed into memory (17 compared to 8), so it should use roughly 9 secs
on my system on booting/preparing desktop.

Could others evtl. add numbers for mac and win...?

It shows that the quickstarter still makes the first startup faster on
todays systems (at least on win7). The original reason to add it was
(AFAIR) a huge waiting time for first startup (more than 30 secs, years
ago) which was not tolerable. When looking at Win8 and (as it seems)
improved startup there (Herbert?) and the problems I would also opt for
removal for the future. It may also pay to invest time in further reduce
startup time tha in keeping the quickstarter alive.

It would be interesting to get infos about the behaviour on other systems
(I would guess quickstarter is most useful on Win anyways...?).

 Regards
 Ricardo


-- 
ALG



Re: Should quickstarter be enabled or disabled by default?

2012-07-25 Thread Armin Le Grand
Hi,

one interesting thing I just stumbled upon; when waiting after the boot
without quickstarter for some time (I left the system unattended after boot
and login for ca. 10 minutes) the first startup of AOO goes down to 8-9
seconds (without quickstarter!). Maybe Win7 already has some mechanism
which measures which dlls are most used and loads these after some time
when nothing was to do...? I was surprised, I will try to repeat this.

Armin Le Grand armin.le.gr...@me.com wrote:
 Hi all,
 
 [..]
 
 +1 for turn it off by default.
 
 About set it on the help menu, there is no relation between help
 functions and the quickstart so IMO it will be completely out of place
 there.
 
 Most users I know do not even realize that the quickstarter is running
 and in fact I cannot remember anyone using the right click menu on
 it...
 
 Just wanted to collect pros and cons, so...
 
 Pros:
 - (p1) Faster first program start after system boot (highly
 system-dependent)
 - (p2) Extra context menus over quickstart icon
 
 Cons:
 - (c1) Uses system memory even when AOO is never used
 - (c2) System boot takes longer
 - (c3) Code complexity is higher, more stuff to maintain
 - (c4) Installation problems/conflicts with running quickstarter
 - (c5) Users do not know about it and what it means
 
 If someone knows more, please add these. We should then think about the
 pros and if they are worth it.
 
 p2: I myself never used it, it's hard to say if it is used or not. The
 functionality would be better placed in a system menu (e.g. start menu on
 Win which tries to hold the last used app starts automatically). My guess
 is that it is rarely used.
 
 p1: I rebooted my Win7 a view times to measure (roughly) the difference.
 Opening a test document with standard text as test. Version used is AOO3.4
 Without quickstarter:
 -booting:
 -first doubleclick on document: 17 seconds
 -Second doubleclick: 1 second or less
 With quickstarter:
 -booting: The tray icons appear asynchonously, but with the 3.4 error
 (office starts) good to detect. the quickstarter boot steals some runitme
 ressources (feels not responsible until fully loaded)
 -first doubleclick on document: 8 seconds
 -Second doubleclick: 1 second or less
 
 I can just guess, but the quickstarter seems to load roughly half of the
 libs needed into memory (17 compared to 8), so it should use roughly 9 secs
 on my system on booting/preparing desktop.
 
 Could others evtl. add numbers for mac and win...?
 
 It shows that the quickstarter still makes the first startup faster on
 todays systems (at least on win7). The original reason to add it was
 (AFAIR) a huge waiting time for first startup (more than 30 secs, years
 ago) which was not tolerable. When looking at Win8 and (as it seems)
 improved startup there (Herbert?) and the problems I would also opt for
 removal for the future. It may also pay to invest time in further reduce
 startup time tha in keeping the quickstarter alive.
 
 It would be interesting to get infos about the behaviour on other systems
 (I would guess quickstarter is most useful on Win anyways...?).
 
 Regards
 Ricardo
 



-- 
ALG



Re: Should quickstarter be enabled or disabled by default?

2012-07-25 Thread Armin Le Grand
RGB ES rgb.m...@gmail.com wrote:
 2012/7/25 Armin Le Grand armin.le.gr...@me.com:
 Hi,
 
 one interesting thing I just stumbled upon; when waiting after the boot
 without quickstarter for some time (I left the system unattended after boot
 and login for ca. 10 minutes) the first startup of AOO goes down to 8-9
 seconds (without quickstarter!). Maybe Win7 already has some mechanism
 which measures which dlls are most used and loads these after some time
 when nothing was to do...? I was surprised, I will try to repeat this.
 
 To speed up windows startup (no matter what they do, it's still slow),
 some libraries are loaded AFTER you get control of the system. Maybe
 the problem is simply that the system is busy with it's own start
 routine, slowing down everything else. Maybe it is a good idea to
 repeat the test with and without quickstart but giving the system at
 least five minutes to get everything running: I think there will be no
 big difference on AOO startup.

You are right. I just repeated without quickstarter, waited for the first
time the blanker started (5 min), re-loggedin, started by double-clicking
on my test document: AOO starts under 4 seconds.
Looks like an argument against quickstarter...

 
 Regards
 Ricardo


-- 
ALG



Re: Should quickstarter be enabled or disabled by default?

2012-07-25 Thread Armin Le Grand
Hi Rory,

Rory O'Farrell ofarr...@iol.ie wrote:
[..]
 
 Armin: as far as I remember, Windows will remove any previously loaded
 DLL files from memory after about 10 minutes of un-use.  
 

This would mean that it gets slower again after some time. I just did not
use AOO, but worked on something else ca. 1 1/2 Hrs after rebooting.
Nonetheless AOO started (doubleclicking the test document, no quickstarter,
last used after reboot) instantly. There must be some least-recently-used
thingy involved, I doubt that all dlls get kicked out after 10 min. Well,
may depend on mem available and other things, though...
I could not see it getting slower after 1 1/2 hours. If someone else has
seen this (without quickstarter, on Win) please comment here.

-- 
ALG



Re: Should quickstarter be enabled or disabled by default?

2012-07-25 Thread Armin Le Grand
Hi Rob,

Rob Weir robw...@apache.org wrote:
 On Wed, Jul 25, 2012 at 8:03 AM, Armin Le Grand armin.le.gr...@me.com wrote:
 Hi Rory,
 
 Rory O'Farrell ofarr...@iol.ie wrote:
 [..]
 
 Armin: as far as I remember, Windows will remove any previously loaded
 DLL files from memory after about 10 minutes of un-use.
 
 
 This would mean that it gets slower again after some time. I just did not
 use AOO, but worked on something else ca. 1 1/2 Hrs after rebooting.
 Nonetheless AOO started (doubleclicking the test document, no quickstarter,
 last used after reboot) instantly. There must be some least-recently-used
 thingy involved, I doubt that all dlls get kicked out after 10 min. Well,
 may depend on mem available and other things, though...
 I could not see it getting slower after 1 1/2 hours. If someone else has
 seen this (without quickstarter, on Win) please comment here.
 
 
 
 Also keep in mind the impact of multi-core.  In theory multi-core
 systems should be less slow at system start, since it could run the
 AOO quickstart task in parallel with other start up tasks. However,
 without quick start, the normal startup of AOO does not take advantage
 of multi-core.  So I'd expect a greater performance boast with modern
 hardware.

I guess only when we could manage to make AOO booting more multithreaded.

 But from user's perspective, I think the benefit depends on whether
 AOO is a key tool that they use several times a day, every day.  Or
 whether it is something they use only occasionally.

If used every day and quickstarter removed: Only when the first start is
done in the first five minutes (or less) after reboot the office will take
twice to three times as long as with quickstarter, after first start seems
no difference. When booting Win all three days may be acceptable. Remember
that with quickstarter system boot itself takes longer (what would be not
counted on our bill, though :-))

If used occasionally: Implies not used in the first 5 minutes, very small
(if at all) difference for first start, no system boot time and/or
ressources wasted (will the day come users of that type will com,plain
about this...?).

 --
 ALG
 


-- 
ALG



Re: [UI] ColorPicker - entering hex color code

2012-07-23 Thread Armin Le Grand
Hi Kevin,

Kevin Grignon kevingrignon...@gmail.com wrote:
 KG01 - See comments inline
 
 On Jul 20, 2012, at 4:57 PM, Armin Le Grand armin.le.gr...@me.com wrote:
 
 [..]
 It depends on what we mean by expected.   I suspect the typical user
 does not touch hexadecimal.  Programmers who are not web developers
 probably expect this to be treated like a number, i.e., they are
 entering the three least significant digits and it will be padded with
 zeros to the left.  Some users, those who are web developers, might
 know (but it is not guaranteed) that CSS3 defines what this means:
 
 The format of an RGB value in hexadecimal notation is a #
 immediately followed by either three or six hexadecimal characters.
 The three-digit RGB notation (#rgb) is converted into six-digit form
 (#rrggbb) by replicating digits, not by adding zeros. For example,
 #fb0 expands to #ffbb00. This ensures that white (#ff) can be
 specified with the short notation (#fff) and removes any dependencies
 on the color depth of the display.
 
 See:   http://www.w3.org/TR/css3-color/#rgb-color
 
 Thanks. I think we should stick to that definition.
 
 KG01 - Agreed. The W3 definition and rules should be supported. Perhaps
 our popup help and documentation should include a reference to the W3 
 material. 

+1

 
 Thus I suggest:
 - Allow Field as Input (see comments from Regina)
 - Ignore when not three or six valid hexadecimal signs
 
 KG01 - From a UX perspective, let's focus on error prevention vs error 
 recovery.

Always good to do so.

 
 - Apply HelpID
 - Adapt Help entries
 
 I will write a task for it when discussion led to a consensus.
 
 Regards,
 
 -Rob
 
 
 
 Regards
 --
 Ariel Constenla-Haile
 La Plata, Argentina
 
 Sincerely,
Armin
 -- 
 ALG
 


-- 
ALG



Re: [UI] ColorPicker - entering hex color code

2012-07-20 Thread Armin Le Grand
[..]
 It depends on what we mean by expected.   I suspect the typical user
 does not touch hexadecimal.  Programmers who are not web developers
 probably expect this to be treated like a number, i.e., they are
 entering the three least significant digits and it will be padded with
 zeros to the left.  Some users, those who are web developers, might
 know (but it is not guaranteed) that CSS3 defines what this means:
 
 The format of an RGB value in hexadecimal notation is a #
 immediately followed by either three or six hexadecimal characters.
 The three-digit RGB notation (#rgb) is converted into six-digit form
 (#rrggbb) by replicating digits, not by adding zeros. For example,
 #fb0 expands to #ffbb00. This ensures that white (#ff) can be
 specified with the short notation (#fff) and removes any dependencies
 on the color depth of the display.
 
 See:   http://www.w3.org/TR/css3-color/#rgb-color

Thanks. I think we should stick to that definition. Thus I suggest:
- Allow Field as Input (see comments from Regina)
- Ignore when not three or six valid hexadecimal signs
- Apply HelpID
- Adapt Help entries

I will write a task for it when discussion led to a consensus.

 Regards,
 
 -Rob
 
 
 
 Regards
 --
 Ariel Constenla-Haile
 La Plata, Argentina

Sincerely,
Armin
-- 
ALG



Re: Testing of SVN Bugzilla Robot enabled (was: [Bug 25920] test issue)

2012-07-16 Thread Armin Le Grand
Hi Herbert,

Herbert Duerr h...@apache.org wrote:
 Testing is enabled now for the robot [1] that watches out for commits
 into our SVN-tree and updates then updates the corresponding bugzilla
 entry if an issue was referenced in the commit summary.
 
 [1] https://issues.apache.org/jira/browse/INFRA-5004
 
 At the beginning of the commit summary classic issue references such as
 #i123456# are recognized. Some committers demanded that issue reference
 such as #123456# (without the 'i') are also accepted, so they are
 recognized too. Should we ever switch to another tracker like JIRA this
 will have to be revisited, though.
 
 If the test is successful there is a good chance that the automatism will
 be deployed in the apache infrastructure.
 
 Currently the robot adds a one-line comment to an issue, e.g.
   hdu committed SVN revision 1234567: #i25920# a test commit
 Would it be helpful if the comment was more or less verbose? E.g. it
 could mention whether trunk or a branch was updated, which sub-projects
 (e.g. sw, sc) were touched, whether a commit into the release branch had
 a matching release-blocker flag, etc.

Nice Idea! But why not simply take all the comment instead of trying to
'guess' the first line? I often try to provide a brief description for the
commit on the command line and a longer one on the task (including the
shorter from the commit plus extra infos). With your change I could simply
add a single, more extensive description when comitting. Maybe the 'Patch
by:', etc. fields should be filtered out though (by identifyingb them using
the ':' or 'by*:'. Just my 2 cent...

 
 Herbert


-- 
ALG



Re: [QE]About bug 119337 is reproduced in AOO3.4.1 snapshot build

2012-06-25 Thread Armin Le Grand

Hi,

On 25.06.2012 11:45, Jürgen Schmidt wrote:

On 6/25/12 10:19 AM, Oliver-Rainer Wittmann wrote:

Hi,

On 25.06.2012 08:33, Ji Yan wrote:

It's release blocker defect for AOO 3.4.1, so should some one merge ALG's
fix from trunk to branch stream.



Yes, the fix should be merged into branch AOO34 from my point of view.


indeed the fix was proposed for 3.4.1 but is not yet integrated.

In my role as release manager I expect that the developers who take
responsibility for issues will take care of the integration.


Thanks for pointing out, I somehow lost this one from my radar. Merged 
and comitted to AOO34 as r1353458.



Juergen



Best regards, Oliver.


2012/6/25 Xue Fei Duanduanx...@gmail.com


Hi,
For bug 119337[1], it's marked as AOO3.4.1 blocker flag. I can
reproduce it
on Mac 10.7 version using AOO 3.4.1- 1351960. Anyone can tell me if
the bug
has been fixed in this build?

[1]https://issues.apache.org/ooo/show_bug.cgi?id=119337











Sincerely,
Armin
--
ALG



Re: Commit message summaries

2012-06-21 Thread Armin Le Grand

Hi,

On 21.06.2012 14:10, Jürgen Schmidt wrote:

On 6/21/12 11:47 AM, Herbert Duerr wrote:

[..]

good point and I agree.

That means we use something like

###
issuenumber + 1_line_summary/description

longer description_on_demand

patch_by_on_demand
...
###

where

issuenumber is

- either the plain number + :
- or #number#
- or #inumber#

I can live with all but we should agree on one notation. My preference
is the first and then the second. I don't think we need the lower case
'i' anymore.


For me in the order of preference I would use:
- #number# (we have only one tracker, no need for flags like 'i')
- #inumber#

I would not like plain number + :, it is just too hard to recognize 
(also to grep for). Maybe it's years of training, but I can simply 
immediately scan if in a task and/or description a Task-ID is included 
or not, just because of the #-usages.


Removal of older tokenized values will depend on being able to identify 
those reliable 100% which I doubt being possible. I sometimes just enter 
a found ID to bugracker, if it does not exist, it's old. If it does 
exist, a short look at it normally makes clear if it is related or not 
(because it was from another tracker). Inconvenient, but better than 
nothing *sigh*.



Older commit messages can be interpreted by knowing the older
conventions and today we have only one bugtracker.

Issues from other bugtracker systems should be ideally duplicated in our
system. The other systems can be public or private bug tracking systems
and issue numbers of the latter ones don't help anybody.


+1


I would like to hear other opinions of people who actually work with our
code.

Juergen



I'm also against using a bare issue number, because having a number that
can be reliably parsed by eventual tools (e.g. a tool that updates
bugzilla with the revision number, a tool that links the revision commit
to the corresponding bug URL, etc.) is no extra effort whereas it opens
a whole world of opportunities. I prefer that computers do such work
that can be automated because they are rather good at that.


fix:short description/summary


I like the commit conventions used in the linux kernel. Browse some
commit links of the kernel shortlog at

http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=shortlog
to see some examples.


A common notation used by all would be of course helpful


+1

Herbert










Re: a question of Export custom file format?

2012-06-07 Thread Armin Le Grand

Hi ,

On 07.06.2012 02:24,  wrote:

hi Armin

  can i modify the SDK to achieve my need.


Not the SDK, but the UNO API definition and imlementation for primitives.

You could do that in principle, but it is a lot of work and requires 
knowing the UNO API and it's principles, Primitives and their 
principles, some of the AOO code and it's functionalities and a lot of 
AOO-specific data types and how to handle them over the API. It also is 
a region where first design and then open discussion will be needed to 
guarantee a good API design; it would be intended to be used by everyone 
and (in principle) should never need to be changed (and needs to stay 
backward compatible from there on since it would be a public API).



  achieve  demo code as below:


  Reference  XRenderable  xRenderable( mxSrcDoc, UNO_QUERY )
VCLXDevice* pXDevice = new VCLXDevice;
..
PDFWriter*  pPDFWriter = new PDFWriter(
aURL.GetMainURL(INetURLObject::DECODE_TO_IURI), PDFWriter::PDF_1_4,
eCompressMode );
OutputDevice*  pOut = pPDFWriter-GetReferenceDevice();
pXDevice-SetOutputDevice( pOut );
..
GDIMetaFile aMtf;
const MapMode   aMapMode( MAP_100TH_MM );
const Size  aMtfSize( aPageSize.Width, aPageSize.Height );

pOut-Push();
pOut-EnableOutput( FALSE );
pOut-SetMapMode( aMapMode );

aMtf.SetPrefSize( aMtfSize );
aMtf.SetPrefMapMode( aMapMode );
aMtf.Record( pOut );

xRenderable-render( nSel - 1, aSelection, aRenderOptions );
aMtf.Stop();
aMtf.WindStart();

if( aMtf.GetActionCount() )
 bRet = ImplExportPage( *pPDFWriter, aMtf, nCompressMode ) || bRet;

pOut-Pop();

just provide the output of the VCL. To meet my needs.
  If this idea can be.
How do I do?

Regards

On 06.06.2012 12:23,  wrote:

hi  Armin

 could you give me  a example of  use your Way doing a new
exporter, assuming that the file format is pdf?


It would be more or less the same as every UNO API based export, iterate
over the document, the pages and the shapes. Instead of getting a
MetaFile from the shape (using Graphicxporter) you would get the
sequence of primitives and use that as base geometry information.

You cannot use this when you want to develop an extension, the UNO API
for primitives is minimal currently and thus you would have to link
against office components (what the definition of extension does not
allow). To do this, the most needed primitives would need to get an UNO
API implementation first.


   Regards


Sincerely,
Armin
--
ALG



/:includetail


Sincerely,
Armin
--
ALG



Re: Shape/Form control alt text import and export for Excel 2003

2012-06-07 Thread Armin Le Grand

Hi Jianyuan Li,

On 07.06.2012 10:08, Jianyuan Li wrote:

Hi, All,

In Excel 2003, for shape and form control, there is an attribute named alt
text. But Aoo shape and form control do not have an attribute similar like
it. So when Aoo import them, this attribute will be omitted. And on
exporting it as an Excel 2003 file, this attribute will not be exported. So
on opening the export file in Excel 2003, incorrect attribute value will be
shown. There is a bug related to it:
https://issues.apache.org/ooo/show_bug.cgi?id=119659

To fix this issue, is there someone having a good solution? How about
import alt text as the title(in shape description dialog) in Aoo? And then
export the Aoo title as Excel 2007 alt text?



There are 'Title', 'Description' and 'Name' properties for each shape. 
alt text sounds more like many lines, so I would suggest to use 
'Description' for it, maybe there is also a good fit for 'Title'. The 
property 'Name' should be a short string and is shown in the navigator, 
maybe also a good candidate to add something useful.


HTH!

Sincerely,
Armin
--
ALG



Re: a question of Export custom file format?

2012-06-06 Thread Armin Le Grand

Hi  (had to copy-paste, cannot read, hope it's correct)

On 06.06.2012 06:23,  wrote:

HI:

I need to develop an extension program of openoffice's write,
the extended function is export a custom file format
, the file format similar as PDF file format ,
But not the PDF file format.

I analyzed the export of PDF files ,the Function  through VCL output.
I have two question as below:

1)Such  need can be achieved in extension of openoffice's write?


Yes, when You use the UNO API. This means to get the document, iterate 
over pages and objects and export them.



2) Can I use
calss VirtualDevice
calss GDIMetaFile
interface---   ReferenceXRenderable  xRenderable (mxSrcDoc, UNO_QUERY)
in openoffice's write?


I do not know too much from it by heart, but a starting point is to get 
the document as handle.
More important: Using VirtualDevice and GDIMetaFile will work, but is 
somehow the older way to do things. With the current state of the core i 
would suggest to use primitives for SdrObjects when you need to export 
graphical representations (as in PDF export, and not the model data as 
in PPT export). Primitives give you all the geometry data in double 
precision and in a tree structure with some automatisms. For each 
SdrObject you may get a sequence of primitives (over UNO API from 
xShape). Examples how to proccess them can be found in 
drawinglayer/source/processor2d. E.g. vclmetafileprocessor2d is the 
instance which currently is used in the core to create GDIMetaFiles from 
primitives (these are not created from 'painting' SdrObjects since some 
time, this already shows that primitives contain more information than 
the GDIMetaFIles). Or e.g. vclpixelprocessor2d is the current renderer 
for pixel output (screen display).
In principle all exporters using geometry information as base data 
can/should be rewritten to use primitives. Thus, when doing a new 
exporter, I would recommend using them from the beginning.
To see how to get primitives from xShape grep for XPrimitiveFactory2D 
and createPrimitivesFromXShape.


HTH!
Sincerely,
Armin
--
ALG



Re: a question of Export custom file format?

2012-06-06 Thread Armin Le Grand

Hi ,

On 06.06.2012 12:23,  wrote:

hi  Armin

could you give me  a example of  use your Way doing a new
exporter, assuming that the file format is pdf?


It would be more or less the same as every UNO API based export, iterate 
over the document, the pages and the shapes. Instead of getting a 
MetaFile from the shape (using Graphicxporter) you would get the 
sequence of primitives and use that as base geometry information.


You cannot use this when you want to develop an extension, the UNO API 
for primitives is minimal currently and thus you would have to link 
against office components (what the definition of extension does not 
allow). To do this, the most needed primitives would need to get an UNO 
API implementation first.



  Regards


Sincerely,
Armin
--
ALG



Re: how Get Bitmap file from SVG module?

2012-06-04 Thread Armin Le Grand
Hi jianlizhao,

jianlizhao jianlizh...@hotmail.com wrote:
 Hi Armin:
 
 I send an Email to Texmaths's author ,  asked he some questions, communicate
 with each other as follows:
 
 My question:
 LaTeX will equations can be inserted as images (SVG or PNG formats) and
  the LaTeX, code is saved into the image attribute for further editing.
 
 His reply:
 Image attributes are not stored directly in the png file but in LibreOffice
 data that are attached to the image.
 
 
  attached the image attribute in openOffice data  below:( basic code)
 ,,,
 Sub SetAttributes( oShape as Variant, iEqSize as Integer, sEqType as String,
 sCode as String) 
  'Add the Latex attribute to the image.
  Dim oAttributes as Variant, oLatexAttribute as Variant
  oAttributes = oShape.UserDefinedAttributes
  oLatexAttribute = createUnoStruct(
 ;com.sun.star.xml.AttributeDataquot; )
  oLatexAttribute.Type =  
  oLatexAttribute.Value = 
  oAttributes.insertByName( ) 
  oShape.UserDefinedAttributes = oAttributes
 End Sub
 ,,,
 
 My question is:
 When the image attribute very long, example 10M bytes, if it  will  wrong.

I cannot tell you, I never used this. You will have to just try it out. I
would guess that it will work, I see no reason someone should have added a
size limitation to it.

 The image attribute can  as a zip file saved in the odf?

I do not know about internals, but saving image attributes with the image
is done internally at save/export time from the AOO code. I see no way to
do it yourself whithout changing this (e.g. implement callbacks which may
be used in an external module if needed). I think it is also not necessary.
Just try out if it works when you add that data and if it will be there
again after reading it.

  Look forward to your reply.
  Best Regards!

HTH!
Sincerely,
Armin
-- 
ALG



Re: how Get Bitmap file from SVG module?

2012-06-01 Thread Armin Le Grand

Hi jianlizhao,

On 01.06.2012 06:22, jianlizhao wrote:

Hi Armin:
You say this I understanding.
I would  insert original image aoo's write and display, I do not how to do it 
with zip file?


I am not sure I understand what you need to know. The method described 
is just a possibility to check the file content of ODF files.


If you insert the reduced Bitmap as GraphicObject in a ODF document and 
save it, it will be contained.


I understood from your last comments that including the raw data 
directly to ODF is not needed. Instead it is set as kind of comment to 
the inserted GraphicObject and thus evtl. indirectly saved and included 
in the ODF. How this may happen I have no idea, sorry.


HTH!


Look forward to your reply.
  Best Regards!


-邮件原件-
发件人: Armin Le Grand [mailto:armin.le.gr...@me.com]
发送时间: 2012年5月31日 22:28
收件人: ooo-dev@incubator.apache.org
主题: Re: how Get Bitmap file from SVG module?

Hi jianlizhao,

much more simple, only a trick to look at the contents of a ODF file.

Example: Save the file (e.g. foo.odf), extend filename (e.g. in explorer
on windows) by *.ziz (-  foo.odf.zip). You can the open the odf file as
zip archive and inspect/check it's contents.

HTH!


[..]

Sincerely,
Armin
--
ALG



Re: how Get Bitmap file from SVG module?

2012-05-31 Thread Armin Le Grand

Hi jianlizhao,

much more simple, only a trick to look at the contents of a ODF file.

Example: Save the file (e.g. foo.odf), extend filename (e.g. in explorer 
on windows) by *.ziz (- foo.odf.zip). You can the open the odf file as 
zip archive and inspect/check it's contents.


HTH!

On 31.05.2012 13:54, jianlizhao wrote:

Hi Armin:
You reply said  Another way is to add a '.zip' to
the AOO file name and to open it as archive.
how to do it?

Can you give a simple and complete example, Programming languages ​​using C++ 
,runtime environment for Microsoft Windows.

Look forward to your reply.
Best Regards!

-邮件原件-
发件人: Armin Le Grand [mailto:armin.le.gr...@me.com]
发送时间: 2012年5月30日 23:46
收件人: ooo-dev@incubator.apache.org
主题: Re: how Get Bitmap file from SVG module?

Hi jianlizhao,


[..]

Sincerely,
Armin
--
ALG



[BLOCKER] Issue 119337

2012-05-30 Thread Armin Le Grand

Hi,

I would like to nominate issue 119337 ([1]) as show stopper/blocker bug.

It's a regression, Mac only. It was a blocker already, set back to major 
from marcus, but I see no reason for this. It's fixed on trunk now, 
patch added to task.


I think it's severe enough for AOO3.4.1 and since it was an API 
implementation problem more UNO API stuff may be concerned (e.g. draw 
object im/export uses this API) in the Mac version.


Sincerely,
Armin

[1] https://issues.apache.org/ooo/show_bug.cgi?id=119337



Re: how Get Bitmap file from SVG module?

2012-05-30 Thread Armin Le Grand

Hi jianlizhao,

On 30.05.2012 16:29, jianlizhao wrote:

Hi Armin:

I find  TexMaths extension is very like my needs. Described as follows:

TexMaths is an extension designed to provide LaTeX support into LibreOffice.
LaTeX equations can be inserted as images (SVG or PNG formats) and the LaTeX
code is saved into the image attribute for further editing.

My question as follows:
The new type picture can be inserted as images (PNG formats) and the
Original picture is saved into the image attribute for further used.
the image attribute can be saved with a file?


I have no idea, I never used something like this. If the example 
extension does it currently and it is allowed to save any binary data at 
the PNG then you can do the same (probably).


To find out if it is saved with the file I would check if it is saved 
currently with the TexMaths extension. Another way is to add a '.zip' to 
the AOO file name and to open it as archive. There you can check for the 
contained single files and data, your binary data should be there somewhere.



The difference between them is
LaTeX equations is small and short, The new type picture is large.
can  This method rigth?


If it serves your needs and works it is right. You need to check if the 
files you create are loadable by a standard office (the AOO3.4 release 
version for example). It should load and show the PNG. I cannot say if 
it will strip your binary data when saving changed, you have to find out 
yourself.


The only possible drawback is when you or other people using your 
extension would spread files generated this way and these files are very 
big. This may cause high eMail loads and similar effects. People may ask 
'why is this file so big, there is only one picture in it'. I would 
suggest to not spread such files with extra data in them too much, maybe 
you only need to use them inhouse or privately anyways. It is a very 
specialized usage of ODF files.



The benefits of the treatment is:
do not have to program  a import filter,
without considering the compatibility of the file ,
Only insert a  picture into openoffice's write.


Yes, looks reasonable.


Look forward to your reply.
Best Regards!


Thanks, same to You. And good luck with it!


  Hi Armin:

Receipt of your reply, I modified my needs.


[..]

Sincerely,
Armin
--
ALG



Re: Drawing layer performance issue

2012-05-29 Thread Armin Le Grand
Hi Clarence,

On 28.05.2012 08:11, Clarence GUO wrote:
 HI~ Armin,
 May I know after aw80 is done, will we have much perfomance improvement on
 rendering?

Some, but not much. aw080 is about security and basic paradigm changes
(I'm preparing documentation, could be ready later today). It is
aprerequisite to some needed stuff. One of the next steps will then be
to create system-specific renderes.

 If we will have, how much improvement can we get from it? Do we
 have some performance test result data or estimation number?

Not yet, aw080 is on progress but will need time and stabilisation. I
did not build the pro version for some time (needed for performance),
but of course feel free to do so (it's on
https://svn.apache.org/repos/asf/incubator/ooo/branches/alg/aw080/)

 Thanks  regards,
 Clarence
 
 
 2012/5/15 王��kingwise...@gmail.com
 
 Hi,
 Currently the performance of drawing layer is not good enough.
 Does anybody know that is it possible to use a mature third-party graphic
 component to replace drawing laywer for improving performance?


 Antonio.Wang

 
Sincerely,
Armin
--
ALG



Re: how Get Bitmap file from SVG module?

2012-05-29 Thread Armin Le Grand
Hi jianlizhao,

I still have to guess what you want to do, but it sounds like:
- Insert raw data file to draw/Impress
- A special extension uses that data to proccess something and outputs a
text file
- That extension creates a Bitmap/BitmapEx AOO can display

If this is correct I see no real reason to implement/embed this
internally in AOO. If you only need the raw data in your extension, why
use AOO for it and create a file format which is potentially very big?
Why not load the raw data from an app which needs it and processes it
(the extension itself)? It seems so specialized that I would think about
a specialized solution. When you already put a *.txt file with results
next to the ODF, why not also let the raw data be aside the ODF file?
Why do you need Draw/Impress at all?

Maybe I'm wrong, still guessing your needs and plan.

On 25.05.2012 03:27, jianlizhao wrote:
 Hi Armin:
 Receipt of your reply, I modified my needs.
 
 The original picture I do not need to display and modify,only to provide
 data to the extension,used for data analysis and processing. This process
 does not need to show only need end result, the end result is saved to a TXT
 file.
 
 All requirements are summarized as follows:
 1)On screen Display bmp or png file, the bmp or png converted from the
 original pictures.

Yes. Who converts this? Which instance?

 2) In the save file include two files, one is the original file.
 In order to achieve compatibility.

Only useful when the extension is installed, no extra use for the
standard user, but much bigger files?

 3)on screen when the user delete the BMP file,in the save file, the file
 related to this BMP files do not save,that is also deleted.
 
 4)In the extension, the original file for data analysis and processing, and
 processing the results are saved to txt file.
 It should be based on the screen select the BMP file,access to the
 corresponding original file.
 
 Do you have any good suggestions.

See above!

 Thanks...
 Best Regards!
 
 
[..]

Sincerely,
Armin
--
ALG



Branch aw080

2012-05-29 Thread Armin Le Grand

Hi List,

due to the increasing number of requests concerning the aw080 branch I 
started to write some documentation and have put it here:


http://wiki.services.openoffice.org/wiki/Aw080_documentation

Short overview: It's a branch I'm working on for some time which will 
cleanup, simplify and make better functional basic parts of the 
DrawingLayer component. More to be read under the link.


Sincerely,
Armin
--
ALG



Re: how Get Bitmap file from SVG module?

2012-05-24 Thread Armin Le Grand

Hi Eric,

On 24.05.2012 03:43, Yong Lin Ma wrote:

Let me try to translate the message below.


Thanks, that helped. Ansering below...


Hi Armin,
I see two interfaces XSVGPrinter and XSVGWriter in svg mdoule

Could they be used for graphic in Bitmap format?


No.


For function extractFromGraphic in svgimagenode

void extractFromGraphic (
 const Graphic  rGraphic
 drawinglayer :: primitive2d :: Primitive2DSequence  rEmbedded,
 basegfx :: B2DRange  rViewBox,
 BitmapEx  rBitmapEx)

What is parameter rBitmapEx work for?


This is a helper method in module svxio. It is not exported from the 
svgio module to make that clear. It should not be called directly and 
may change in the future.


Instead, use the classes Graphic and GraphicObject and work with the 
SvgData class used there if you want to do something in the environment 
of the office core code.


From outside you may use the service XSvgParser to convert from 
io::XInputStream to uno::Sequence uno::Reference 
::graphic::XPrimitive2D   (the imported primitive representation of 
the SVG). Then use the service XPrimitive2DRenderer to convert such a 
primitive to a rendering::XBitmap. Grep the code to find usage examples.


HTH!


On Wed, May 23, 2012 at 5:06 PM, jianlizhaojianlizh...@hotmail.com  wrote:

Hi Armin:
I ask you some question as below:
In  module svg, have two Interfaces, one is  XSVGPrinter, the other is
XSVGWriter.

1) Can I use these interfaces, output Bitmap file?

2) under the module svg, in the file of svgimagenode.cxx,

void extractFromGraphic (
const Graphic  rGraphic
drawinglayer :: primitive2d :: Primitive2DSequence  rEmbedded,
basegfx :: B2DRange  rViewBox,
BitmapEx  rBitmapEx)

is the  parameters rBitmapEx get Bitmap file?

Thanks...
Best Regards!








Re: how Get Bitmap file from SVG module?

2012-05-24 Thread Armin Le Grand
Hi jianlizhao,

On 24.05.2012 10:57, jianlizhao wrote:
 Hi Armin:
 Read your letter, I know my idea is stupid.
 
 I would like to achieve an ADDON expansion in openoffice's write,
 The extension function is plug a new type of picture into openoffice's
 write, need following requirements
 
 1) There were also ODF-compatible File Format adaptions needed.That is to
 say,
 That is not installed the extended  on the openoffice's write  can open
 the saved file.
 2) If the extension is installed, can use the extended functionality to deal
 with the inserted picture.
 
 This function is very similar to  your SVGIO, so I need to look deeper
 SVGIO.

Sorry, it is not similar and I would not suggest svgio as an example to
extend for picture formats. The way to extend picture formats is to look
at how e.g. png, jpeg and others are handled in the office and to extend
these by a filter. Be warned, this is a complex (and fragile) system
which will need a lot of care.

Your raw format is pixel data, so this will fit much better than svgio.
Svgio needed an exception to be hold at Graphic/GraphicObject at all,
this will not be needed for another pixel-based format and thus is a
very bad example for your case.

All this would need to be done in the core, there are deep vcl- and
tools-based mechanisms behind this, including the GraphicManager who
will automatically buffer the picture data and import/export it on
demand to rduce mem footprint. I think it cannot be done as an extension.

What you could do in an extension is to implement the loader (raw data
to Bitmap/BitmapEx) and insert that pixel data using API to the writer
somehow. It will then not be embedded as the original raw bitmap data,
but it will be in the system in a compatible way.

HTH!

 Then modeled this idea, realization my needs.
 
 I have installed openoffice's SDK.Debugging through a simple C++ example of
 the addon.
 Do you have any good suggestions.
 
 Thanks...
 Best Regards!
 
 
 
 -邮件原件-
 发件人: Armin Le Grand [mailto:armin.le.gr...@me.com]
 发送时间: 2012年5月23日 20:51
 收件人: ooo-dev@incubator.apache.org
 主题: Re: how Get Bitmap file from SVG module?
 
   Hi jianlizhao,
 
 On 23.05.2012 11:06, jianlizhao wrote:
 Hi Armin:
 I ask you some question as below:
 In  module svg, have two Interfaces, one is  XSVGPrinter, the other is
 XSVGWriter.
 
 Both are interfaces, XSVGPrinter is not used at all and XSVGWriter is
 the current SVG export which has nothing to do with the new import.
 There also is no module svg, the module I added for the new SVG import
 is svgio.
 
 1) Can I use these interfaces, output Bitmap file?
 
 No.
 
 2) under the module svg, in the file of svgimagenode.cxx,

 void extractFromGraphic (
   const Graphic   rGraphic
   drawinglayer :: primitive2d :: Primitive2DSequence
 rEmbedded,
   basegfx :: B2DRange   rViewBox,
   BitmapEx   rBitmapEx)

 is the  parameters rBitmapEx get Bitmap file?
 
 I am not sure what you want to do. To work with imported SVGs you need a
 Graphic (see vcl and GraphicObject, too) where it is loaded. From
 Graphic you may try
 
   const SvgDataPtr  getSvgData() const;
 
 If getSvgData().is() there is a SVG graphic. At the contained SvgData
 you can use
 
   const BitmapEx  getReplacement() const;
 
 to get the BitmapEx of the SVG. There is no need to work with stuff from
 svgio directly. All usages work with it are using the service XSvgParser
 and do the work for you, where XSvgParser is implemented in svgio.
 
 I still do not understand what you want to do, please explain this, else
 I cannot really help you.
 
 Thanks...
 Best Regards!


 
 Sincerely,
   Armin
 --
 ALG
 
 
 




Re: how Get Bitmap file from SVG module?

2012-05-24 Thread Armin Le Grand
Hi jianlizhao,

On 24.05.2012 16:07, jianlizhao wrote:
 Hi Armin:
 I am very glad to receipt your letter,
 
 I see the following content in your blog:
 There were also ODF-compatible File Format adaptions needed, more concrete
 the in ODF already contained and described multi-image support. In ODF, the
 original SVG is now embedded to the 'Pictures' folder inside the ODF file as
 one would expect from such a feature and can be easily extracted (unzip the
 ODF file and there you are). There is also a Png file written as replacement
 image. The draw:frame is now multi-image capable (as the spec allows). In
 the case of a SVG it writes a good quality Png and the original SVG as
 draw:image elements. Since older (and other) office versions are only
 capable of loading a single (and thus the first) image, the Png is written
 first. This allows file exchange with other and older offices without
 breaking backward compatibility and/or ODF file exchange.
 
 I have two questions :
 1) I would also like to use this method to insert the picture, so that in
 document will retain the original file, the original file  is there are
 other useful.

To achieve this you have to add the needed code to the core (similar as
jpeg and png are added). This includes import code to get the data into
a Bitmap/BitmapEx. This is uniquely held (using a unique ID calculated
based on the bitmap data, there is one calculation defined for each
format) at the GraphicManager and can be accessed using
Graphic/GraphicObject.
AFAIK it is also possible to hold the original raw data at the entry in
the GraphicManager (to be able to write the original again in unchanged
form without needing to export it to it's format).
The feature you mentioned above is needed for file formats which differ
in content, in Your case this is not needed since a e.g. reduced data
BitmapEx can be recreated without data loss from your raw data. It makes
no sense to write both, so no need for this feature.

 2) How do I access the original file.

The Graphic holding it (and the contact with the GraphicManager) may
have it as raw data, but also has a link to a temporary storage (using
the temp on your system) where it is swapped out.
To Access, use Graphic/GraphicObject. I repeat here: It is no easy task
to add a graphic format to the core. I'm also not the specialist for
that, maybe someone else knows in more details about exactly what steps
have to be done to implement it.

HTH!

 Thanks...
 Best Regards!
 
 
 -邮件原件-
 发件人: Armin Le Grand [mailto:armin.le.gr...@me.com]
 发送时间: 2012年5月24日 18:10
 收件人: ooo-dev@incubator.apache.org
 主题: Re: how Get Bitmap file from SVG module?
 
   Hi jianlizhao,
 
[..]

Sincerely,
Armin
--
ALG



Re: how Get Bitmap file from SVG module?

2012-05-23 Thread Armin Le Grand

Hi jianlizhao,

On 23.05.2012 11:06, jianlizhao wrote:

Hi Armin:
I ask you some question as below:
In  module svg, have two Interfaces, one is  XSVGPrinter, the other is
XSVGWriter.


Both are interfaces, XSVGPrinter is not used at all and XSVGWriter is 
the current SVG export which has nothing to do with the new import. 
There also is no module svg, the module I added for the new SVG import 
is svgio.



1) Can I use these interfaces, output Bitmap file?


No.


2) under the module svg, in the file of svgimagenode.cxx,

void extractFromGraphic (
 const Graphic  rGraphic
 drawinglayer :: primitive2d :: Primitive2DSequence  rEmbedded,
 basegfx :: B2DRange  rViewBox,
 BitmapEx  rBitmapEx)

is the  parameters rBitmapEx get Bitmap file?


I am not sure what you want to do. To work with imported SVGs you need a 
Graphic (see vcl and GraphicObject, too) where it is loaded. From 
Graphic you may try


const SvgDataPtr getSvgData() const;

If getSvgData().is() there is a SVG graphic. At the contained SvgData 
you can use


const BitmapEx getReplacement() const;

to get the BitmapEx of the SVG. There is no need to work with stuff from 
svgio directly. All usages work with it are using the service XSvgParser 
and do the work for you, where XSvgParser is implemented in svgio.


I still do not understand what you want to do, please explain this, else 
I cannot really help you.



Thanks...
Best Regards!




Sincerely,
Armin
--
ALG



Re: svx/source/svdraw/svdfmtf.cxx

2012-05-21 Thread Armin Le Grand

Hi,

On 21.05.2012 11:34, Andre Fischer wrote:

On 20.05.2012 13:30, Armin Le Grand wrote:

Hi Pavel,

[..]

Who will check in the changes?


Already did, Pavel is informed.



-Andre








Sincerely,
Armin
--
ALG



Re: WaE: cui

2012-05-21 Thread Armin Le Grand

On 21.05.2012 14:28, Pavel Janík wrote:

Compiling: cui/source/tabpages/tpline.cxx
cc1plus: warnings being treated as errors
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/tabpages/tpline.cxx: In member 
function ‘virtual void SvxLineTabPage::Reset(const SfxItemSet)’:
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/tabpages/tpline.cxx:1021: 
warning: unused variable ‘pPageView’
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/tabpages/tpline.cxx: In 
member function ‘long int SvxLineTabPage::MenuCreateHdl_Impl(MenuButton*)’:
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/tabpages/tpline.cxx:1753: 
warning: unused variable ‘pPageView’
dmake:  Error code 1, while making '../../unxmacxi.pro/slo/tpline.obj'
ERROR: error 65280 occurred while making 
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/cui/source/tabpages

Indeed, adaptions from Regina using MarkAll(), so the SdrPageView 
pointer is no longer used. Adaped, comitted.


Sincerely,
Armin
--
ALG



Re: WaE: chart2

2012-05-21 Thread Armin Le Grand

On 21.05.2012 14:31, Pavel Janík wrote:

Compiling: chart2/source/view/main/ShapeFactory.cxx
cc1plus: warnings being treated as errors
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/chart2/source/view/main/ShapeFactory.cxx: In 
function ‘com::sun::star::drawing::PolyPolygonShape3D 
chart::createPolyPolygon_Symbol(const com::sun::star::drawing::Position3D, const 
com::sun::star::drawing::Direction3D, sal_Int32)’:
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/chart2/source/view/main/ShapeFactory.cxx:1329:
 warning: unused variable ‘fMaxSize’
dmake:  Error code 1, while making '../../../unxmacxi.pro/slo/ShapeFactory.obj'
ERROR: error 65280 occurred while making 
/Users/pavel/BUILD/BuildDir/ooo_trunk_src/chart2/source/view/main

Just commenting out this variable helped (the same applies in cui case in 
previous mail).

Yes. Do you commit yourself...?

Sincerely,
Armin
--
ALG



Re: svx/source/svdraw/svdfmtf.cxx

2012-05-20 Thread Armin Le Grand
Hi Pavel,

Pavel Janík pa...@janik.cz wrote:
 Hi,
 
 WaE = Warning as Error.
 
 or Warnings Are Errors.
 
 Gcc option -Werror: Make all warnings into errors.
 
 With this option turned on, all warnings are made into errors. Our long
 term goal is to make gcc silent.

Ah, yes, I remember now. We spent some time on this years ago, but never
coud make the whole code WaE-safe. Despite that, it's good to work on it;
sometimes this gives good hints at weird code.

 These issues are not errors per se, but e.g.:
 
 @@ -1330,6 +1331,7 @@
  
  void ImpSdrGDIMetaFileImport::DoAction(MetaWallpaperAction rAct)
Please just comment /*rAct*/
  {
 +(void) rAct;
  OSL_ENSURE(false, Tried to construct SdrObject from
 MetaWallpaperAction: not supported (!));
  }
  
 This means that rAct is unused in the method. gcc warns about it.
 
 This change:
 
 @@ -1384,6 +1388,7 @@
  case GRADIENT_ELLIPTICAL: aXGradientStyle = 
 XGRAD_ELLIPTICAL; break;
  case GRADIENT_SQUARE: aXGradientStyle = XGRAD_SQUARE; break;
  case GRADIENT_RECT: aXGradientStyle = XGRAD_RECT; break;
 +   default: break;
Hmm. I do not have the code at hand right now, cannot tell until monday.
  }
  
  const XFillGradientItem aXFillGradientItem(
 
 means that some enum value is forgotten in the switch.
 
 This change:
 
 -for(sal_uInt32 y(0); y  pOld-Height(); y++)
 +for(sal_Int32 y(0); y  pOld-Height(); y++)
Please change to sal_uInt32
 means that we were comparing signed and unsigned value.
 
 I do not know if these changes are OK, thus I send the patch as I used to
 make the module WaE free.

I have not seen a patch. If you have one, please send again (maybe
directly) and I'll happily take a look on monday. I'm currently not
compiling on gcc, so I will not be able to guarantee, though.

 Hope this helps.
 
 P.S. Of course warnings differ between compilers and sometims the changes 
 look weird etc.

Yes, I remember now. Do you have a good solution for swich..case where not
all missing entries would have to be listed? 


-- 
ALG



Re: Need guide for my first 'push'

2012-05-20 Thread Armin Le Grand
Regina Henschel rb.hensc...@t-online.de wrote:
 Hi Ariel,
 
 Ariel Constenla-Haile schrieb:
 On Sat, May 19, 2012 at 03:43:49PM -0300, Ariel Constenla-Haile wrote:
 Hi Regina,
 
 On Sat, May 19, 2012 at 04:39:31PM +0200, Regina Henschel wrote:
 Hi all,
 
 I'm ready to push my first patch. But it is the first time and I
 need a guide how to do it.
 
 I have cloned from trunk by 'git svn clone ...'
 I have made all the changes, compiled and tested.
 I have done 'git commit -am' and controlled the changes with 'git
 format-patch git-svn'.
 
 But now I do not know how to continue.
 
 First, make sure you have committed everything:
 
 git status
 
 Then check out the last changes, so that your tree is up to date:
 
 git svn rebase
 
 If there was a merge, make sure your changes are still working.
 Once ready to push your changes to the Apache SVN repo, simply do:
 
 * check what will be committed:
 
 git svn dcommit --dry run
 
 typo: --dry-run
 
 * commit it:
 
 git svn dcommit
 
 
 More info:
 
 - git help svn
 - http://trac.parrot.org/parrot/wiki/git-svn-tutorial
 - http://blog.tsunanet.net/2007/07/learning-git-svn-in-5min.html
 - http://www.reasonablyopinionated.com/2009/06/git-svn-workflow.html
 - ...
 
 
 DOne, but it seems to fail. I get
 $ git svn dcommit
 Committing to https://svn-master.apache.org/repos/asf/incubator/ooo/trunk ...
 Authentication realm: https://svn-master.apache.org:443 ASF Committers
 Password for 'pppregin':
 Authentication realm: https://svn-master.apache.org:443 ASF Committers
 Username: regina
 Password for 'regina':
 M 
 main/chart2/source/controller/chartapiwrapper/WrappedSymbolProperties.cxx
 No such file or directory: Can't create temporary file from template
 '/cygdrive/c/AOO_2012_05_g
 it/trunk/C:/cygwin/tmp/svn-XX': No such file or directory at
 /usr/lib/git-core/git-svn line
  579
 
 What is wrong?

I made the following experience: After using 'source winenv.set.sh' on win
there is the variable TMPDIR which still uses a DOSstyle path. I usually
chnage it to 'TMPDIR=/cygdrive/a/TEMP' (choose your own path of course) to
fix that.

HTH!

 Kind regards
 Regina


-- 
ALG



Re: about openoffice support on SVG ?

2012-05-20 Thread Armin Le Grand
Hi jianlizhao,

jianlizhao jianlizh...@hotmail.com wrote:
 Hello my friend,
 
 I ask you some question as below:
 1) source code with support for SVG code, What programming language is used?

It's C++.


 IS   C + + or JAVA?
 2) In order to support SVG features, which files additions and modifications
 to those source code?

The code is in the main/svgio module, I wrote it. What do you want to do?
Maybe I can help you or just support your needs. Have you read the blog
entry on it
(https://blogs.apache.org/OOo/entry/native_svg_support_for_apache), it
explains some basic principles about it and how it is added to the office
processing (primitive usage).

 Thanks...
 
  Best Regards!

Sincerely,
Armin
-- 
ALG



Re: [Build] build problem in svx

2012-05-19 Thread Armin Le Grand
Hi,

yes, xbitmap is gone. The problems you describe happen when you update a
local copy of trunk and do not cleanup the output trees, in that case the
prebuilt dependencies still contain references to the file. There are two
alternatives: build fresh with a new checkout or delete all build
dependencies. The 2nd can be done in several ways, I usually rm -rf
trunk/main/solver* and rm -rf trunk/main/*/wntmsci12* (for windows,
corresponding for other plattforms).

HTH!

Regina Henschel rb.hensc...@t-online.de wrote:
 Hi all,
 
 I get the build error
 make: *** No rule to make target
 `/cygdrive/c/AOO_2012_5_git/main/svx/inc/svx/xbitmap.hxx', needed by
 `/cygdrive/c/AOO_2012_5_git/main/solver/340/wntmsci12/workdir/CxxObject/svx/source/engine3d/obj3d.o'.
  Stop.
 dmake:  Error code 2, while making 'all'
 
 I need a hint, where to search for the reason.
 
 Kind regards
 Regina


-- 
ALG



Re: svx/source/svdraw/svdfmtf.cxx

2012-05-19 Thread Armin Le Grand
Hi Pavel,

I worked on it. What do you mean with WaE? I googled, but couild not find
explanations. I know there was something, but I do not want to rely on
guessing.

Pavel Janík pa...@janik.cz wrote:
 Hi,
 
 this file in the trunk has several WaE issues:
 
 http://tmp.janik.cz/AOOo/svx-WaE.diff


-- 
ALG



Re: svx/source/svdraw/svdfmtf.cxx

2012-05-19 Thread Armin Le Grand
Marcus (OOo) marcus.m...@wtnet.de wrote:
 Am 05/19/2012 01:22 PM, schrieb Armin Le Grand:
 Hi Pavel,
 
 I worked on it. What do you mean with WaE? I googled, but couild not find
 explanations. I know there was something, but I do not want to rely on
 guessing.
 
 WaE = Warning as Error.

Ah, okay, thanks. So, what aspect of that file should be different? It
wants to warn for non-impemented actions, but it does not need to be an
error. If the result looks weird, the issued warnings in a debug version
may help as a hint for what went wrong.

What should be different? 

 HTH
 
 Marcus
 
 
 
 Pavel Janíkpa...@janik.cz  wrote:
 Hi,
 
 this file in the trunk has several WaE issues:
 
 http://tmp.janik.cz/AOOo/svx-WaE.diff


-- 
ALG



Re: Drawing layer performance issue

2012-05-17 Thread Armin Le Grand
Hi Antonio,

Antonio.Wang kingwise...@gmail.com wrote:
 Hi Armin,
 What you've done is a pretty great work.
 
 Here is my focus area about drawing layer:
 1. Refreshment
  #Currently, when refresh the window (for example, just minise and then
 restore), many primitives will be created again. That will cause some
 effort waste during this process. I wonder why we could not keep the
 primitive unchanged and just repaint it?

That's one of the paradigm changes I've made in aw080 already. Background:
When doing primitives this was my first concept, but it showed that the
other needed mechanism - to detect core changes and ensure recreation of
the primitive - did not work reliably. Thus, the safest was to create the
most high-level primitive, compare it with the existing one and detect
every evtl. change reliably. Remark that the old primitive is used in the
most no-change case, thus all the decompositiopns and the low-level
primitives are reused most of the time.
Done in aw080, plus the needed ensurement of invalidations.

But anyways, that's not where the time is spent, see
https://issues.apache.org/ooo/show_bug.cgi?id=118984

 2. System-specific renderers
 #This is the most intreset point of my care,  since different base
 renderers especially hardware releated ones works in different ways, if the
 drawing layer become more universal for high level APIs, it'll need more
 work to seperate the universal items into specific items and process, and
 then it could use the best performance of those System-specific renderers.
 That's really a render engine work should do.

That's true, but a lot of preps need to be done for that. The idea is to
not use sal/vcl at all, but to use UNO API renderer modules on surfaces
(API will hand over handle to window (however) the sequence of primitives
and info (transformation, etc.)). For each  OS a UNO API module should be
implemented containing a renderer implementation (see drawinglayer module).
To be able to do so, the surfaces which are created from vcl as Window need
to be controlled, too. E.g. on win ther will not be the fastest renderiung
when the Window implementation creates just any HDC-type, but not e.g. a 3d
surdace one. OTOH Vcl will always have to work on that surfaces, too
(EditEngine paints, controls, ...) and the rendering will me a mixture of
both accesses.

   As far as I know a render engine contains 6 basic parts at least:
 Primitives, GraphicObjects, GraphicTree, Universal Rendering Process,
 Universal rendering APIs to encapsulate Specific plantform rendering APIs.
 The primitive is the most base items for a render engine, if our work now
 is focus on the primitive converting, I think it is still a long long
 way to reach the final target.

It is, but I'm on it. We should evtl. clarify the terms you used, they do
not match 1005 of the stuff in the source and/or the current mechanisms
work.

  What we mainly focus is the office production, and the the rendering
 engine is a module which function is very independent, so why don't we just
 to use a mature third party ones, and save lots of time and effort to do
 our professional things? Professional ones do professional things is my
 view, we are not a render engine group after all. :-)

Also true. Do you have any idea what renmderer would be best to use under
Linux? AA is needed, speed of course, and it should be able to paint
PolyPolygons (what X is not,, argh...). I see no big problems of choosing
on Win and Mac, and we still have the Vcl fallback which is used today...

HTH!

Sincerely,
Armin

 Antonio
 
 2012/5/16 Armin Le Grand armin.le.gr...@me.com
 
Hi Liang and Antonio,
 
 
[..]
 --
 ALG
 
 


-- 
ALG



Re: Drawing layer performance issue

2012-05-16 Thread Armin Le Grand

Hi Liang and Antonio,

On 16.05.2012 03:00, Liang Weike wrote:

Hi,

On 2012-5-15 22:31, Armin Le Grand wrote:

Hi Antonio Wang,

On 15.05.2012 10:44, 王喆 wrote:

Hi,
Currently the performance of drawing layer is not good enough.


Yes, that's true :-)

And what is the percentage it takes within the whole performance?



Does anybody know that is it possible to use a mature third-party
graphic
component to replace drawing laywer for improving performance?


Yes, I know that it's not s easy. I'm preparing this for years. Do not
forget that DrawingLayer has many components (model, viewer to which
you probably refer, controller) and is used hardcoded from 14 users
(not only the visible apps, also dialogs, helpers, etc.). Also it's
used on (at least) five systems. It's going in the right direction,
but is ongoing work which will need some more time. I'm on it...

HTH!

I'm interested in it,too. Could you please introduce the work that you
have done and the plan in the future? Thanks!


I am working on the code for 15 years, concentrating on the 
DrawingLayer. I have added primitives (see 
http://wiki.services.openoffice.org/wiki/DrawingPrimitives) and e.g. the 
new SVG import based on them. All graphic rendering is done using 
primitives now (leaded to AntiAliasing). I am currently working on aw080 
which will make further deep core changes (preparing some docu on it 
currently, will send a note if done) the code is at 
https://svn.apache.org/repos/asf/incubator/ooo/branches/alg/aw080/. This 
will bring us closer to more safe DrawingLayer core objects.


The future plan is to:
- convert as many as possible components to primitive usage, e.g. 
SlideShow, exports (PDF, SVG, printing, ...)
- Implement generic system-specific renderers for visualisation of 
primitives


Of course the prerequisite is to have all graphical output based on 
primitives. Draw/Impress is, Chart is, DrawingLayer objects in Writer 
and Calc are. Missing is EditEngine in edit mode, cells and text in 
calc, text in writer.


HTH!





Antonio.Wang



Sincerely,
Armin
--
ALG



Sincerely,
Armin
--
ALG



Re: Drawing layer performance issue

2012-05-15 Thread Armin Le Grand

Hi Antonio Wang,

On 15.05.2012 10:44, 王喆 wrote:

Hi,
Currently the performance of drawing layer is not good enough.


Yes, that's true :-)


Does anybody know that is it possible to use a mature third-party graphic
component to replace drawing laywer for improving performance?


Yes, I know that it's not s easy. I'm preparing this for years. Do not 
forget that DrawingLayer has many components (model, viewer to which you 
probably refer, controller) and is used hardcoded from 14 users (not 
only the visible apps, also dialogs, helpers, etc.). Also it's used on 
(at least) five systems. It's going in the right direction, but is 
ongoing work which will need some more time. I'm on it...


HTH!



Antonio.Wang



Sincerely,
Armin
--
ALG



Re: Build broken at SVX ?

2012-05-11 Thread Armin
Hi Pedro,

xbitmap.hxx is gone, you have old dependencies. use 'make clean' in svx and
be sure to build incompatible from svx.

Sincerely,
Armin

Pedro Giffuni p...@apache.org wrote:
 Doesn't look like one of my changes ;)
 
 
 gmake: *** No rule to make target
 `/usr/ports/editors/openoffice-3-devel/work/ooo/main/svx/inc/svx/xbitmap.hxx',
  needed by
 `/usr/ports/editors/openoffice-3-devel/work/ooo/main/solver/340/unxfbsdx.pro/workdir/CxxObject/svx/source/engine3d/obj3d.o'.
  Stop.
 gmake: *** Waiting for unfinished jobs
 dmake:  Error code 2, while making 'all'
 
 
 
 Cheers,
 
 Pedro.


-- 
ALG



Re: APPR is enabled with AOO3.4 on Ubuntu 11.04

2012-05-08 Thread Armin Le Grand

Hi Chao Huang,

On 08.05.2012 10:04, Chao Huang wrote:

hi, Armin

The layout of text in Aoo 3.4 is better than that in FireFox. Here are
snapshots. Thanks!


Thanks for the feedback! Yay!

[..]

Sincerely,
Armin
--
ALG



Re: [CODE] build breaks with commit r1334023 in drawinglayer

2012-05-05 Thread Armin
Hi Regina and others,

sorry, I forgot to add and commit newly added files. Argh! I'll try to add
these ASAP...
I apologize; I should always 'svn add ...' immediately for new files...

Sincerely,
Armin

Regina Henschel rb.hensc...@t-online.de wrote:
 Hi,
 
 build breaks in drawinglayer with error
 /usr/bin/cp: cannot stat
 `/cygdrive/c/AOO_2012_5_git/main/drawinglayer/inc/drawinglayer/primitive2d/objectinfoprimitive2d.hxx':
 No such file or directory
 
 Kind regards
 Regina


-- 
ALG



Re: [CODE] Build breaks with r1334023 in svgio

2012-05-05 Thread Armin
Hi Regina,

sorry, I forgot to add new files and thus these are missing for the commit.
I have to be more careful in the future and 'svn add ...' new files
immediately/sooner. I tried to access my develop machine in the office tbis
aftrenoon, but it's locked, could not access it. Thus you should use the
last revision before r1334023. I will fix this asap on Monday.

Sorry for the inconvenience (a good lesson to take the machine home on
weekends...)

Armin

Regina Henschel rb.hensc...@t-online.de wrote:
 Hi,
 
 build breaks with error
 /usr/bin/cp: cannot stat
 `/cygdrive/c/AOO_2012_5_git/main/svgio/inc/svgio/svgreader/svgtitledescnode.hxx':
  No such
 file or directory
 
 Kind regards
 Regina


-- 
ALG



Re: APPR is enabled with AOO3.4 on Ubuntu 11.04

2012-05-04 Thread Armin Le Grand

Hi Chao Huang,

just one remark; when you are at it, could you also take the chance to 
open the SVG results in AOO3.4 directly, not only in firefox? I guess 
these would be very good test files for seeing if all works well with 
the new SVG feature. I'm always interested when there should be problems...


On 04.05.2012 11:18, Chao Huang wrote:

hi, all

I'm working on adapting APPR against the latest OpenOffice - Apache
OpenOffice 3.4 on Ubuntu 11.04. At right now, APPR can work with AOO 3.4 on
Ubuntu to get performance data, such as Startup, LoadFile and
PlaySlide.

In general, the following 3rd parts should be installed to run APPR.

- gawk
- bash
- libperl-dev
- libyaml-perl
- SVG
- XML::Mini
- XML::Simple

The patch file for sal\rtl\source\makefile should be updated, due to the
change on the original file. I replaced svgdisplay with firefox to show
the result in SVG file. If you have a recommended one, please update the
wiki
http://wiki.services.openoffice.org/wiki/How_to_enable_APPR_with_Apache_OpenOffice_3.4_on_Ubuntu_11.04#Run_APPR_for_Apache_OpenOffice_3.4.
Thanks!

Another thing in todo list is to find resource about *VTune*. If I can get
the installation package for VTune, I will try to enable it and test it in
APPR.

The next step for me is to run APPR against AOO 3.4 with sample file to
generate performance report. It may be the performance baseline in AOO 3.4.
But I know nothing about how to use APPR in OO's formal test. Is there
anyone who can share the guide/script/expereince?

Any feedback will be appreciated. Thanks!



Sincerely,
Armin
--
ALG



Re: Release Notes: missing screenshots

2012-05-02 Thread Armin
Andrea Pescetti pesce...@apache.org wrote:
 Paolo is now coordinating volunteers that are translating the Release
 Notes into Italian, and while quickly reviewing the original document
 https://cwiki.apache.org/OOOUSERS/aoo-34-incubating-release-candidate.html
 I have the impression that some paragraphs would be much clearer with a
 screenshot or a sample document. For example, does anyone have more
 information on the following items?
 
 - Further development/bug fixes for DOCX import filter
 (a sample DOCX to test, or a screenshot showing the progress in import
 would be very useful)
 
 - Enhanced chart visualization
 (is this backend only or user-visible? if it's the latter, is there an
 ODF available to test?)

It basically means that internally the graphic objects are not exchanged
using a metafile in old metafile format with integer coordinates, but
primitves are used directly with all their possibilities. This removes two
transformation steps and avoids losing quality, thus being faster and
qualitatively better, e.g. when having charts with more than 65535 data
points (the maximum for polygons in metafiles). Also positions are better
due to double precision when zooming in or needing high resolutions. The
main advantage is that 3d charts do not need to be visualized as bitmaps
(metafiles do not know 3d at all, thus they need to be transported as
bitmap), but stay in 3d geometry for visualisation. To see the advantages,
try to zoom into a 3d chart in OOO3.3 and AOO3.4. This also gives enhanced
printing and exports, too. One of the features which were forgotten to be
mentioned in some publications recently...

 
 - Formula: Automatic baseline for Math objects
 (while it is well explained, again having a sample ODF file or
 screenshots would help, since Math isn't the most popular module)
 
 Thanks,
   Andrea.


-- 
ALG



Re: After AOO 3.4?

2012-04-30 Thread Armin Le Grand

On 30.04.2012 14:35, Rob Weir wrote:

On Mon, Apr 30, 2012 at 12:55 AM, Juergen Schmidt
jogischm...@googlemail.com  wrote:

[..]

I don't think so, I would do it exactly in the other direction. Fixes for 
critical issues or issues that are assigned for a 3.4.1 should be fixed on the 
related stable branch and also merged into trunk.



I thought Armin ran into some performance-related issues with merging.
  Do we know what direction that was, and what we need to do to avoid
this problem in the future?


It happened due to having a branch for aw080 before quite some header 
changes and file attribute changes were made, plus some exchange and 
movement of binary blobs. This should not happen with working branches 
in the future as long as the changes to the source will not get extreme 
(as in this case). Anyways, there are two distinct branch usages here:


(1) What I called 'work branch': Something branched from trunk, but with 
the medium or long time goal to reintegrate to trunk. This makes 
resyncing with trunk necessary; thus may be expensive with big changes 
on trunk


(2) Release branches: These are here to 'freeze' a release and to 
continue development of a bugfixed version (no features) .e.g. a 3.4.1 
from a 3.4. These are from the principle not intended to be merged back 
to trunk ever, thus no danger to run in performance issues here.



-Rob



But we can discuss if we want code reviews for fixes going into the stable 
branch before they are committed.

Juergen



Pedro.






Sincerely,
Armin
--
ALG



Re: [VOTE] Release Apache OpenOffice 3.4 (incubating) RC1

2012-04-24 Thread Armin Le Grand

Hi,

Fetched r1327774, built and checked win pro version and mac version, 
played around with both.

Looks fine, no bigger problems found

+1

On 21.04.2012 02:58, Jürgen Schmidt wrote:

Hi all,

this is a call for vote on releasing the following candidate as Apache
OpenOffice 3.4 (incubating). This will be the first incubator release
for Apache OpenOffice and a key milestone to continue the success of
OpenOffice.org.



[..]


[ ] +1 Release this package as Apache OpenOffice 3.4 (incubating)
[ ] 0 Don't care
[ ] -1 Do not release this package because...




Sincerely,
Armin
--
ALG



Re: [USER EXPERIENCE DESIGN] Hello

2012-04-13 Thread Armin Le Grand

Hi Kevin,

welcome to the project!

On 13.04.2012 09:37, Kevin Grignon wrote:

Hello All,

I joined the AOO project a few weeks ago and wanted to take a moment to
formally introduce myself to the project.

My name is Kevin Grignon, I'm a user experience designer with 15 years of
experience in product research, interaction design and usability
evaluation. I'm a Certified User Experience Professional who is currently
working for IBM, based out of Shanghai, China.

I'm very excited to be joining this effort, and look forward to
contributing to the design direction moving forward.

My area of interest are related to product design and user experience
design. I feel that successful products are those that are designed for
people. I feel that technology should compliment, rather thank disrupt,
people's lives. I like to balance incremental enhancements to the existing
user experience, with explorations of future design direction and
innovation.


I'm looking forward to suggestions for enhancing the user experience. 
I'm more on the technical side, but may help discussing if, how and for 
what effort suggested changes may be doable.



Within the Apache OpenOffice community, I'm looking to work with others who
are interested in researching and understanding how people use our products
to accomplish their goals. More specifically, I'd like to determine how
might we understand how people use our tools today, what works? what
doesn't? I'd also like to understand how people will use our tools in the
future? I'd like to understand the customer journey and the document life
cycle in the age of social networks, mobile devices and cloud computing.


These are very important questions to answer and discuss; the best 
feature is worthless when people do not find or not understand them (we 
have examples in AOO :-))



There has been some really great UX work done in past on this project, I'd
like to build of this strong base and bring AOO to the next level.


Looking forward to suggestions and discussions in this area!


Please contact me if you are interested in working together to
re-invigoratethe UX effort on Apache OpenOffice moving forward. I'd like to
work with development to learn how I can contribute to feature design and
direction. I'd like to work with users to understand what OpenOffice means
in the context of their world.

Best regards,
Kevin

Kevin Grignon
User Experience Designer
kevingrignon...@gmail.com



Sincerely,
Armin
--
ALG



Re: [RELEASE]: showstopper Bug 119215 - save operation fail and prompt continuing to save endlessly on r1309668-Chinese China (zh-CN) version

2012-04-13 Thread Armin Le Grand

On 13.04.2012 11:54, Jürgen Schmidt wrote:
[..]


Here a short update on the topic. My fix solve the problem and also
solve the translation problem that Claudio pointed out before for pt-BR.


updated trunk, rebuilt en-US and zh-CN, both work as expected. Task is 
fixed.



I am already building MacOS based on revision 1325589 and I would like
to propose this one now for our first RC. And Oliver is building Windows.

@Ariel: I hope you are also able to build the linux packages soon and
sorry that this further showstopper comes up. For the future we should
work on a build bot solution that builds the binary releases with our
preferred configuration and on our defined base Linux version. And the
same for windows and Mac if possible.
You should only provide full install sets for now, no language packs.

Juergen






Re: ooo large commit breaks mirror sync !!

2012-04-11 Thread Armin Le Grand

Hi Gavin,

On 21.02.2012 00:21, Gavin McDonald wrote:

If anyone wants to do large commits like below link shows [1] (over 8000
paths changed and lots of zips and tar files.)

PLEASE notify infra first and schedule it for a WEEKEND.

People have been struggling to commit to the EU mirror since this large
commit was started 5 hours ago.

Thanks

Gav...

[1] -
http://svn.apache.org/viewvc?view=revisionsortby=revsortdir=downrevision=
1291394


sorry to come back to this one, but I've re-synched and built aw080 
branch 
(https://svn.apache.org/repos/asf/incubator/ooo/branches/alg/aw080) 
which contains all the changes which lead to the first problems. Worse, 
this time even more changes are involved.


I see no other chance to resync my branch (containing 1 1/2 years of 
work on OOo code) than to commit it to the branch. Please give advice 
when and how to do that, I'll be ready to commit in the next days.


Sincerely,
Armin
--
ALG



Re: ParagraphData copy constructor not found

2012-04-05 Thread Armin Le Grand

On 05.04.2012 11:29, Jean-Louis 'Hans' Fuchs wrote:

Hello

I get an undefined symbol error for ParagraphData::ParagraphData(const 
ParagraphData). I checked that the library libediteng.so is included, that the 
symbol is there and that it really demangles to the signature. See below.

Has anybody an idea what I could try next?
Is it possible to disable that module? Since this is a debug build that I need 
soon and in the release build this doesn't happen.


ParagraphData is not used in dlgedfunc.cxx (in reportdesigner), it is 
also not exported from libediteng (see paragraphdata.hxx). Seems to be a 
solaris compiler thingy; somehow (maybe includes and inlines) he wants 
that constructor.


ParagraphData is not used outside editengine module, thus it is okay not 
to export it (each single export makes the startup slower, thus this was 
optimized once). If you find no solution, you may add EDITENG_DLLPUBLIC 
to the ParagraphData definition in paragraphdata.hxx, rebuild and 
deliver editeng module and try again.


Should look like this:

class EDITENG_DLLPUBLIC ParagraphData
{
...


Please do not check this in, it's only a workarund.

HTH!

Sincerely,
Armin



Best,
Jean

oobuild@sundev: ~/aoo-build-debug/ooo/main/reportdesign/unxsols4 $ 
/opt/solarisstudio12.3//bin/CC -w -mt -z combreloc -PIC -temp=/tmp -norunpath 
-library=no%Cstd -R'$ORIGIN:$ORIGIN/../ure-link/lib' -z text -G -Bdirect -z 
defs -M ../unxsols4/misc/component_rptui.map -L../unxsols4/lib -L../lib 
-L/build/aoo-build-debug/ooo/main/solenv/unxsols4/lib 
-L/build/aoo-build-debug/ooo/main/solver/340/unxsols4/lib 
-L/build/aoo-build-debug/ooo/main/solenv/unxsols4/lib 
-L/build/aoo-build-debug/ooo/main/solenv/unxsols4/libsolaris.2.6 -L/lib 
-L/usr/lib -L/usr/local/lib -L/usr/dt/lib -L/usr/openwin/lib 
-L/usr/jdk/instances/jdk1.6.0/lib -L/usr/jdk/instances/jdk1.6.0/jre/lib/sparc 
-L/usr/jdk/instances/jdk1.6.0/jre/lib/sparc/xawt 
-L/usr/jdk/instances/jdk1.6.0/jre/lib/sparc/native_threads -L/usr/X11/lib 
../unxsols4/slo/rptui_version.o -o ../unxsols4/lib/librptui.so 
../unxsols4/slo/RptUndo.o ../unxsols4/slo/ColorListener.o 
../unxsols4/slo/UITools.o ../unxsols4/slo/rptuiservices.o 
../unxsols4/slo/toolbox

controller.o ../unxsols4/slo/statusbarcontroller.o 
../unxsols4/slo/FunctionHelper.o ../unxsols4/slo/dlgpage.o 
../unxsols4/slo/Condition.o ../unxsols4/slo/CondFormat.o 
../unxsols4/slo/GroupExchange.o ../unxsols4/slo/PageNumber.o 
../unxsols4/slo/DateTime.o ../unxsols4/slo/AddField.o 
../unxsols4/slo/Navigator.o ../unxsols4/slo/GroupsSorting.o 
../unxsols4/slo/Formula.o ../unxsols4/slo/uistrings.o 
../unxsols4/slo/DefaultInspection.o ../unxsols4/slo/ReportComponentHandler.o 
../unxsols4/slo/GeometryHandler.o ../unxsols4/slo/DataProviderHandler.o 
../unxsols4/slo/metadata.o ../unxsols4/slo/SectionWindow.o 
../unxsols4/slo/ReportController.o ../unxsols4/slo/ReportControllerObserver.o 
../unxsols4/slo/FormattedFieldBeautifier.o ../unxsols4/slo/FixedTextColor.o 
../unxsols4/slo/ReportSection.o ../unxsols4/slo/SectionView.o 
../unxsols4/slo/ViewsWindow.o ../unxsols4/slo/ScrollHelper.o 
../unxsols4/slo/StartMarker.o ../unxsols4/slo/EndMarker.o 
../unxsols4/slo/dlgedfunc.o ../unxsols4/slo/dlgedfac.o ../u
nxsols4/slo/dlgedclip.o ../unxsols4/slo/ReportWindow.o 
../unxsols4/slo/DesignView.o ../unxsols4/slo/propbrw.o -lediteng -lsvxcore 
-lsvx -lsfx -lsvt -ltk -lvcl -lsvl -lsot -lutl -ltl -ldbtools -lcomphelpC52 
-luno_cppuhelperC52 -luno_cppu -lfwe -li18nisolang1C52 -luno_sal -ldbu -lrpt 
-lfor -lforui -Bdynamic -lpthread -lCrun -lm -lc -Bdynamic 
-lstlport_sunpro_debug

Undefined   first referenced
  symbol in file
ParagraphData::ParagraphData(const ParagraphData)
../unxsols4/slo/dlgedfunc.o
ld: fatal: symbol referencing errors. No output written to 
../unxsols4/lib/librptui.so
oobuild@sundev: ~/aoo-build-debug/ooo/main/reportdesign/unxsols4 $

oobuild@sundev: ~/aoo-build-debug/ooo/main/reportdesign/unxsols4 $ nm 
../unxsols4/slo/dlgedfunc.o | grep ParagraphData | grep UNDEF
[772]   | 0| 0|FUNC |GLOB |0|UNDEF  
|__1cNParagraphData2t6Mrk0_v_

oobuild@sundev: ~/aoo-build-debug/ooo/main/reportdesign/unxsols4 $ nm 
/build/aoo-build-debug/ooo/main/solver/340/unxsols4/lib/libediteng.so | grep 
__1cNParagraphData2t6Mrk0_v_
[1584]  |   1875448|28|FUNC |LOCL |2|11 
|__1cNParagraphData2t6Mrk0_v_

oobuild@sundev: ~/aoo-build-debug/ooo/main/reportdesign/unxsols4 $ echo 
__1cNParagraphData2t6Mrk0_v_ | /build/aoo-build-debug/demangle/demangle
ParagraphData::ParagraphData(const ParagraphData)







Re: After AOO 3.4, attracting new contributors

2012-03-22 Thread Armin Le Grand

On 20.03.2012 11:09, Armin Le Grand wrote:

Hi Rob,


[..]

Extendign after Reginas eMail:

- refactoring
- featues
- bugfixing
- tutoring



The tradeoffs are hard, but splitting time in
- refactoring
- featues
- bugfixing
is the key, the ratio is hard to determine, maybe everyone has to find a
balance for himself.



[..]

Sincerely,
Armin
--
ALG



Re: Rat scan vs SGA

2012-03-22 Thread Armin Le Grand
\pentaho\parser\style-mapping.txt
GR reportbuilder\java\com\sun\star\report\pentaho\smil.css
GR reportbuilder\java\com\sun\star\report\pentaho\star-office.css
GR reportbuilder\java\com\sun\star\report\pentaho\star-report.css
GR reportbuilder\java\com\sun\star\report\pentaho\star-rpt.css
GR reportbuilder\java\com\sun\star\report\pentaho\svg.css
GR reportbuilder\java\com\sun\star\report\pentaho\xsl-fo.css
GR reportbuilder\license\THIRDPARTYREADMELICENSE.html
GR reportbuilder\license\readme_en-US.html
GR reportbuilder\license\readme_en-US.txt
GR reportbuilder\prj\rpt.xml
GR reportbuilder\template\manifest.xml
GR reportbuilder\template\post.xml
GR reportbuilder\template\pre.xml
GR reportbuilder\util\component.txt
GR reportbuilder\util\description.xml
GR reportbuilder\util\manifest.xml

// originally from XConsortium, mkdepend.man contains license info 
(permission)

// and looks like MIT1.1 - should be added to rat excludes
// A case for https://issues.apache.org/jira/browse/LEGAL-130
OK soltools\mkdepend\collectdircontent.cxx
OK soltools\mkdepend\collectdircontent.hxx
OK soltools\mkdepend\cppsetup.c
OK soltools\mkdepend\def.h
OK soltools\mkdepend\ifparser.c
OK soltools\mkdepend\ifparser.h
OK soltools\mkdepend\imakemdep.h
OK soltools\mkdepend\include.c
OK soltools\mkdepend\main.c
OK soltools\mkdepend\mkdepend.man
OK soltools\mkdepend\parse.c
OK soltools\mkdepend\pr.c

// No license info, filtername lists probably written by testing, thus 
probably SUN/Oracle, should be added to grant
GR 
testautomation\framework\optional\input\filternames\Oracle_Open_Office_Filternames_add_en-US.txt
GR 
testautomation\framework\optional\input\filternames\Oracle_Open_Office_Filternames_en-US.txt


// No license info, test scripting lists probably written by testing, 
thus probably SUN/Oracle, should be added to grant
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_help_applications_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_help_content_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_help_topics_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_headings_and_whole_words_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_headings_only_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_whole_words_only_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_without_filter_en-US.txt


// Copyright (C) 2007 TWAIN Working Group, e.g. available under 
www.twain.org/devfiles/twain.h
// uses The TWAIN License, see http://www.twain.org/license.shtm, as 
required there it is mentioned

// already in our NOTICE file - should be added to rat excludes
OK twain\inc\twain.h

// Open Document Managment API, uses OPEN DOCUMENT MANAGEMENT API 
LICENSE 1.0
// defined in the file. Text is equal to BSD license without advertising 
- should be added to rat excludes

// A case for https://issues.apache.org/jira/browse/LEGAL-130
OK ucb\source\ucp\odma\odma.h

// orw: dual license: GPL and BSD, BSD license without advertising - 
should be added to rat excludes

OK unixODBC\inc\iodbcunix.h
OK unixODBC\inc\sql.h
OK unixODBC\inc\sqlext.h
OK unixODBC\inc\sqltypes.h
OK unixODBC\inc\sqlucode.h

// in progress, see #119097#
// ydario solved this, now relicensed under ALv2
AL vcl\inc\os2\wingdi.h
AL vcl\inc\os2\xwphook.h

// (C) 1988, 1989, 1990 by Adobe Systems Incorporated, hdu is taking a look
?? vcl\unx\generic\fontmanager\parseAFM.cxx
?? vcl\unx\generic\fontmanager\parseAFM.hxx

// mixed file, (C) SUN/Oracle and Copyright (C) 2002 William Lachance
// May be GPL prtially
?? writerperfect\source\wpdimp\wpft_genericfilter.cxx

// Copyright © 2000 SuSE, Inc., license from text (see files)
// equal to MIT1.1 - should be added to rat excludes
// A case for https://issues.apache.org/jira/browse/LEGAL-130
OK x11_extensions\inc\Xrender.h
OK x11_extensions\inc\randr.h
OK x11_extensions\inc\randrproto.h
OK x11_extensions\inc\render.h
OK x11_extensions\inc\renderproto.h

Sincerely,
Armin
--
ALG






BSD (without advertisiong) Category A

2012-03-22 Thread Armin Le Grand

Hi List,

in http://www.apache.org/legal/resolved.html BSD (without advertising 
clause) is part of Category A. I found no information in which category 
BSD *with advertising clause* maybe? Does someone know this?


Sincerely
Armin
--
ALG



Re: Rat scan vs SGA files which should be in SGA grant

2012-03-22 Thread Armin Le Grand

Hi all,

these are the files (63) which are not covered by the RAT output but 
should be part of a third SGA from Oracle:




connectivity\com\sun\star\sdbcx\comp\hsqldb\StorageNativeOutputStream.java
mysqlc\source\mysqlc_connection.cxx
mysqlc\source\mysqlc_connection.hxx
mysqlc\source\mysqlc_databasemetadata.cxx
mysqlc\source\mysqlc_databasemetadata.hxx
mysqlc\source\mysqlc_driver.cxx
mysqlc\source\mysqlc_driver.hxx
mysqlc\source\mysqlc_general.cxx
mysqlc\source\mysqlc_general.hxx
mysqlc\source\mysqlc_preparedstatement.cxx
mysqlc\source\mysqlc_preparedstatement.hxx
mysqlc\source\mysqlc_propertyids.cxx
mysqlc\source\mysqlc_propertyids.hxx No info, but should be same as 
mysqlc_propertyids.cxx

mysqlc\source\mysqlc_resultset.cxx
mysqlc\source\mysqlc_resultset.hxx
mysqlc\source\mysqlc_resultsetmetadata.cxx
mysqlc\source\mysqlc_resultsetmetadata.hxx
mysqlc\source\mysqlc_services.cxx
mysqlc\source\mysqlc_statement.cxx
mysqlc\source\mysqlc_statement.hxx No info, but should be same as 
mysqlc_statement.cxx

mysqlc\source\mysqlc_subcomponent.hxx
mysqlc\source\mysqlc_types.cxx
mysqlc\source\mysqlc_types.hxx
mythes\mythes-1.2.0-makefile-mk.diff
ooo_custom_images\industrial\res\commandimagelist\frobnicate-icons.php
reportbuilder\java\com\sun\star\report\pentaho\layoutprocessor\OfficeGroupInstanceSectionLayoutController.java
reportbuilder\java\com\sun\star\report\pentaho\layoutprocessor\OfficePageSectionLayoutController.java
reportbuilder\java\com\sun\star\report\pentaho\model\OfficeGroupInstanceSection.java
reportbuilder\java\com\sun\star\report\pentaho\oasis-datastyle.css
reportbuilder\java\com\sun\star\report\pentaho\oasis-draw.css
reportbuilder\java\com\sun\star\report\pentaho\oasis-form.css
reportbuilder\java\com\sun\star\report\pentaho\oasis-style.css
reportbuilder\java\com\sun\star\report\pentaho\oasis-table.css
reportbuilder\java\com\sun\star\report\pentaho\oasis-text.css
reportbuilder\java\com\sun\star\report\pentaho\parser\style-mapping.txt
reportbuilder\java\com\sun\star\report\pentaho\smil.css
reportbuilder\java\com\sun\star\report\pentaho\star-office.css
reportbuilder\java\com\sun\star\report\pentaho\star-report.css
reportbuilder\java\com\sun\star\report\pentaho\star-rpt.css
reportbuilder\java\com\sun\star\report\pentaho\svg.css
reportbuilder\java\com\sun\star\report\pentaho\xsl-fo.css
reportbuilder\license\THIRDPARTYREADMELICENSE.html
reportbuilder\license\readme_en-US.html
reportbuilder\license\readme_en-US.txt
reportbuilder\prj\rpt.xml
reportbuilder\template\manifest.xml
reportbuilder\template\post.xml
reportbuilder\template\pre.xml
reportbuilder\util\component.txt
reportbuilder\util\description.xml
reportbuilder\util\manifest.xml
testautomation\framework\optional\input\filternames\Oracle_Open_Office_Filternames_add_en-US.txt
testautomation\framework\optional\input\filternames\Oracle_Open_Office_Filternames_en-US.txt
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_help_applications_en-US.txt
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_help_content_en-US.txt
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_help_topics_en-US.txt
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_headings_and_whole_words_en-US.txt
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_headings_only_en-US.txt
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_whole_words_only_en-US.txt
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_without_filter_en-US.txt
writerperfect\source\wpdimp\wpft_genericfilter.cxx


Sincerely,
Armin



Re: Rat scan vs SGA Files with BSD/MIT similar license

2012-03-22 Thread Armin Le Grand

Hi all,

these are the files (25) which are not covered by the RAT output but 
have a BSD or MIT equal or similar license included.




// GPL, but special entry there (see af's mail or in the files) :
//# As a special exception to the GNU General Public License, if you
//# distribute this file as part of a program that contains a
//# configuration script generated by Autoconf, you may include it under
//# the same distribution terms that you use for the rest of that program.
// thus can be kept and should be added to rat excludes
// A case for https://issues.apache.org/jira/browse/LEGAL-130
config.guess
config.sub

// Header contains license identical to BSD without advertising - 
should be added to rat excludes

// A case for https://issues.apache.org/jira/browse/LEGAL-130
connectivity\qa\complex\connectivity\hsqldb\TestCacheSize.java

// FSF, contains MIT equal license - should be added to rat excludes
// A case for https://issues.apache.org/jira/browse/LEGAL-130
hwpfilter\source\ksc5601.h

// findings from af: The libtextcat version 2.2 library is under BSD license
// It was released 2003 by WiseGuys Internet B.V. 
(http://software.wise-guys.nl:1080/libtextcat/index.html ).

// No problem there. It's BSD license (with advertising).
// Asking on the list what category this may be
// A case for https://issues.apache.org/jira/browse/LEGAL-130
libtextcat\data\new_fingerprints\fpdb.conf

// originally from XConsortium, mkdepend.man contains license info 
(permission)

// and looks like MIT1.1 - should be added to rat excludes
// A case for https://issues.apache.org/jira/browse/LEGAL-130
soltools\mkdepend\collectdircontent.cxx
soltools\mkdepend\collectdircontent.hxx
soltools\mkdepend\cppsetup.c
soltools\mkdepend\def.h
soltools\mkdepend\ifparser.c
soltools\mkdepend\ifparser.h
soltools\mkdepend\imakemdep.h
soltools\mkdepend\include.c
soltools\mkdepend\main.c
soltools\mkdepend\mkdepend.man
soltools\mkdepend\parse.c
soltools\mkdepend\pr.c

// Open Document Managment API, uses OPEN DOCUMENT MANAGEMENT API 
LICENSE 1.0
// defined in the file. Text is equal to BSD license without advertising 
- should be added to rat excludes

// A case for https://issues.apache.org/jira/browse/LEGAL-130
ucb\source\ucp\odma\odma.h

// (C) 1988, 1989, 1990 by Adobe Systems Incorporated
// permissive license, but not categorized by Apache (not A, B or X)
// A case for https://issues.apache.org/jira/browse/LEGAL-130
vcl\unx\generic\fontmanager\parseAFM.cxx
vcl\unx\generic\fontmanager\parseAFM.hxx

// Copyright © 2000 SuSE, Inc., license from text (see files)
// equal to MIT1.1 - should be added to rat excludes
// A case for https://issues.apache.org/jira/browse/LEGAL-130
x11_extensions\inc\Xrender.h
x11_extensions\inc\randr.h
x11_extensions\inc\randrproto.h
x11_extensions\inc\render.h
x11_extensions\inc\renderproto.h


Sincerely,
Armin
--
ALG



Re: Rat scan vs SGA

2012-03-21 Thread Armin Le Grand
\help_browser\Oracle_Open_Office_help_topics_en-US.txt
?? 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_headings_and_whole_words_en-US.txt
?? 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_headings_only_en-US.txt
?? 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_whole_words_only_en-US.txt
?? 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_without_filter_en-US.txt


// Copyright (C) 2007 TWAIN Working Group, e.g. available under 
www.twain.org/devfiles/twain.h

// uses The TWAIN License, see http://www.twain.org/license.shtm
?? twain\inc\twain.h

// Open Document Managment API, uses OPEN DOCUMENT MANAGEMENT API 
LICENSE 1.0
// defined in the file. Allows redistribution of source with conditions 
(see file)

?? ucb\source\ucp\odma\odma.h

// orw: dual license: GPL and BSD
?? unixODBC\inc\iodbcunix.h
?? unixODBC\inc\sql.h
?? unixODBC\inc\sqlext.h
?? unixODBC\inc\sqltypes.h
?? unixODBC\inc\sqlucode.h

// in progress, see #119007#
?? vcl\inc\os2\wingdi.h
?? vcl\inc\os2\xwphook.h

// (C) 1988, 1989, 1990 by Adobe Systems Incorporated, hdu is taking a look
?? vcl\unx\generic\fontmanager\parseAFM.cxx
?? vcl\unx\generic\fontmanager\parseAFM.hxx

// mixed file, (C) SUN/Oracle and Copyright (C) 2002 William Lachance
// May be GPL prtially
?? writerperfect\source\wpdimp\wpft_genericfilter.cxx

// Copyright © 2000 SuSE, Inc., license from text (see files)
// sounds like MIT1.1
?? x11_extensions\inc\Xrender.h
?? x11_extensions\inc\randr.h
?? x11_extensions\inc\randrproto.h
?? x11_extensions\inc\render.h
?? x11_extensions\inc\renderproto.h

Sincerely,
Armin
--
ALG



Re: Rat scan vs SGA

2012-03-21 Thread Armin Le Grand
 
(permission)

// and looks like MIT1.1 - should be added to rat excludes
OK soltools\mkdepend\collectdircontent.cxx
OK soltools\mkdepend\collectdircontent.hxx
OK soltools\mkdepend\cppsetup.c
OK soltools\mkdepend\def.h
OK soltools\mkdepend\ifparser.c
OK soltools\mkdepend\ifparser.h
OK soltools\mkdepend\imakemdep.h
OK soltools\mkdepend\include.c
OK soltools\mkdepend\main.c
OK soltools\mkdepend\mkdepend.man
OK soltools\mkdepend\parse.c
OK soltools\mkdepend\pr.c

// No license info, filtername lists probably written by testing, thus 
probably SUN/Oracle, should be added to grant
GR 
testautomation\framework\optional\input\filternames\Oracle_Open_Office_Filternames_add_en-US.txt
GR 
testautomation\framework\optional\input\filternames\Oracle_Open_Office_Filternames_en-US.txt


// No license info, test scripting lists probably written by testing, 
thus probably SUN/Oracle, should be added to grant
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_help_applications_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_help_content_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_help_topics_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_headings_and_whole_words_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_headings_only_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_whole_words_only_en-US.txt
GR 
testautomation\framework\optional\input\help_browser\Oracle_Open_Office_search_without_filter_en-US.txt


// Copyright (C) 2007 TWAIN Working Group, e.g. available under 
www.twain.org/devfiles/twain.h
// uses The TWAIN License, see http://www.twain.org/license.shtm, as 
required there it is mentioned

// already in our NOTICE file - should be added to rat excludes
OK twain\inc\twain.h

// Open Document Managment API, uses OPEN DOCUMENT MANAGEMENT API 
LICENSE 1.0
// defined in the file. Text is equal to BSD license without advertising 
- should be added to rat excludes

OK ucb\source\ucp\odma\odma.h

// orw: dual license: GPL and BSD
?? unixODBC\inc\iodbcunix.h
?? unixODBC\inc\sql.h
?? unixODBC\inc\sqlext.h
?? unixODBC\inc\sqltypes.h
?? unixODBC\inc\sqlucode.h

// in progress, see #119007#
?? vcl\inc\os2\wingdi.h
?? vcl\inc\os2\xwphook.h

// (C) 1988, 1989, 1990 by Adobe Systems Incorporated, hdu is taking a look
?? vcl\unx\generic\fontmanager\parseAFM.cxx
?? vcl\unx\generic\fontmanager\parseAFM.hxx

// mixed file, (C) SUN/Oracle and Copyright (C) 2002 William Lachance
// May be GPL prtially
?? writerperfect\source\wpdimp\wpft_genericfilter.cxx


// Copyright © 2000 SuSE, Inc., license from text (see files)
// sounds like MIT1.1
?? x11_extensions\inc\Xrender.h
?? x11_extensions\inc\randr.h
?? x11_extensions\inc\randrproto.h
?? x11_extensions\inc\render.h
?? x11_extensions\inc\renderproto.h

Sincerely,
Armin
--
ALG



  1   2   3   >