from:"Patricia Shanahan"

I have been working on a bug, and have reached the conclusion that a fix 
will require changes to the parsing of XML and recording of event 
actions. I am seriously handicapped in making progress on this because 
that happens in the depths of UNO, and I have zero UNO knowledge.


Can anyone help?

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: we are a ASF-project





On 9/12/2020 12:37 AM, Jörg Schmidt wrote:

Hello Patricia,


-Original Message-
From: Patricia Shanahan [mailto:p...@acm.org]
Sent: Saturday, September 12, 2020 9:20 AM
To: dev@openoffice.apache.org
Subject: Re: we are a ASF-project

This is about the subject line, not the content.


right, i have understood Marcus in the same way


It should be "we are an ASF-project".


Excuse me, is it about the difference between "a" and "an"?

If so, then I must say:
I don't think Marcus meant this spelling mistake, because he was talking about 
_changing_ subject.
If he did mean it, I wonder why, because my posts are certainly full of 
spelling mistakes all the time, so this single mistake can't have any special 
relevance.


As far as I can tell - I have not been following the thread - my 
objection to the substitution of "a" for "an" before a vowel sound has 
nothing to do with any content. It is just a frustration with seeing the 
same error over and over again.






Jörg



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: we are a ASF-project

On 9/12/2020 12:46 AM, Jörg Schmidt wrote:

-Original Message-
From: Patricia Shanahan [mailto:p...@acm.org]
Sent: Saturday, September 12, 2020 9:36 AM
To: dev@openoffice.apache.org
Subject: Re: we are a ASF-project

On 9/12/2020 12:20 AM, Patricia Shanahan wrote:

This is about the subject line, not the content. I don't usually do
spelling and grammar, but that seems to be the main

content. As a native

English speaker, that subject line makes me cringe every

time I see it.

It should be "we are an ASF-project".

Here's some documentation: Oxford English Dictionary entry
for "a, adj".
"Inflections:   Before a vowel sound an ..."

Thanks, but I'm afraid my Enlish is not getting any better. I am linguistically 
untalented, not only regarding English.

You are a lot more linguistically talented than I am.

I can struggle through reading French, know a little Latin, and have 
picked up some Spanish, especially words and phrases used on public 
signs and menus, just by living in a bilingual area. Otherwise, I am the 
classic monolingual English speaker.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: we are a ASF-project





On 9/12/2020 12:20 AM, Patricia Shanahan wrote:
This is about the subject line, not the content. I don't usually do 
spelling and grammar, but that seems to be the main content. As a native 
English speaker, that subject line makes me cringe every time I see it.


It should be "we are an ASF-project".


Here's some documentation: Oxford English Dictionary entry for "a, adj". 
"Inflections:   Before a vowel sound an ..."


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: we are a ASF-project

This is about the subject line, not the content. I don't usually do 
spelling and grammar, but that seems to be the main content. As a native 
English speaker, that subject line makes me cringe every time I see it.


It should be "we are an ASF-project".

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Website Migrations

2020-07-11 Thread Patricia Shanahan


On 7/11/2020 11:48 AM, Dave Fisher wrote:

Hi -

It’s time to start the process of migrating two of our websites from the 
deprecated Apache CMS to a new method of building. This will be a major 
undertaking and there are several goals.

The sites are:
https://openoffice.apache.org/
https://www.openoffice.org/

We have a CWiki page for planning at 
https://cwiki.apache.org/confluence/display/OOOUSERS/Website+Migrations 


We have empty Git repos:
https://github.com/apache/openoffice-project
https://github.com/apache/openoffice-org

The request is in to rename the “master” branch to “trunk”. These repositories 
are currently empty.

If someone has a “modern” design paradigm to suggest now is the time.

If someone has suggestions for content to eliminate or move now is the time.

I’d prefer to work out new site build mechanics on the project site first.


I don't have any specific recommendations, but I do suggest looking at 
what other projects have done. For example, see 
https://cwiki.apache.org/confluence/display/INFRA/How+Apache+Jena+migrated+from+the+CMS


--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Fwd: Re: should we conduct a 20 year anniversary online conference / meetup?

2020-07-07 Thread Patricia Shanahan





On 7/7/2020 8:18 AM, Peter wrote:

Dear Pedro,

Am 07.07.20 um 12:14 schrieb Pedro Lino:
As a member of this project I kindly request that people do not make 
presentations in German.


English is the lingua franca and everybody in this project regardless 
of nationality makes an effort to communicate in that language.
As an example Mechtilde's English is very good or at least good enough 
to communicate and pass instructions to someone else as myself who is 
not a native English speaker.


Thanks to services like https://www.deepl.com/translator there is a huge 
differense between writing and talking.


We mostly write and do not talk. This are two seperate skills. I am 
conviced as you are that english is piece of cake for Mechtilde and 
Michael. But if they say otherwise, I respect that.


We should expect little of everyone, but drive them to get the maximum 
out. So the lowest jump hight is german with subtitles. And that why I 
cannot reconsider.


Having presentations in a language other than English will only drive 
people away from this project.


I disagree. Only if we do not work to close the gap it will work 
disruptive. So I thopught of subtitles.


If we can make an english audio track we will do so. Whatever we will 
come up with we will try.


We should fetch people where they are not force them to a standard. We 
want to value competence, but having no competence should not be 
negative. Improve your own competence is a competent action. We can only 
value this if we lower barriers as much as possible and start there 
where people are. And open up ways to bring them to growth.




If the idea is to exchange ideas and attract people to this project 
I'm asking you please to reconsider.


Please help me to convince Mechtilde and Michael that they can do it. I 
am not the one who needs the reasurance. I hope you understand the 
difference. I believe in them as much as you do. But my job now is to 
enable the track and them with whatever they offer.


And this is not only true for this case. This is true for all cases. And 
if it is not clear it is for me no special offer, but the standard I 
follow.


Regardless of the English skills of the speakers, consider the audience. 
I can read French. I can write French with the help of a dictionary and 
spell checker, though it may not be much better than if I wrote in 
English and used Google Translate. I cannot follow spoken French.


Similarly, I hope the audience for these talks will include people who 
have the skills needed to participate in an e-mail discussion in 
English, but who cannot follow a talk in English. We should make those 
people feel welcome to the project.


The talks sound interesting, so I hope an English translation will 
become available.






--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Decisions and Behavior

2020-07-06 Thread Patricia Shanahan


On 7/6/2020 12:14 AM, Jörg Schmidt wrote:
...

My criticism concerned the PMC's approach in the present case. I would have 
simply wished for equal treatment of equal volunteer work, or some other 
justification (and I have explained what this justification could have been 
using the example of Günther).


I am strongly opposed to the PMC publicly justifying its committer and 
PMC decisions.


There are several special cases in which doing to would be very 
damaging. If we usually published the background to our decisions, and 
refused to do so only in a few cases, people would assume one of those 
special cases applies.


I believe we should announce when we have invited a committer or PMC 
member and they have accepted, and otherwise keep personnel discussions 
private.


--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: New Committer: Detlef Nannen

2020-07-05 Thread Patricia Shanahan

I got distracted, and forgot to post the only appropriate form of 
message for a "New Committer" thread:


Detlef, welcome to the AOO committer team.


--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Automated gbuild -> SCons convertibility now at 88.57%

2020-07-04 Thread Patricia Shanahan


On 7/4/2020 12:53 PM, Damjan Jovanovic wrote:

scripting is a dmake module with no symbols
package is a gbuild module with symbols

So yes, as we move off dmake, more and more modules should have working
debug symbols.


I have suddenly become a convert to moving off dmake.



This is the case on *nix too, where dmake doesn't provide full paths to
filenames, breaking debugging.

On Sat, Jul 4, 2020 at 9:35 PM Patricia Shanahan  wrote:


On 7/4/2020 12:24 PM, Damjan Jovanovic wrote:

Given how I've only developed on FreeBSD so far, anything Windows is
probably at negative infinity :) >
Do you have some example modules with that symbols problem, or at least
know whether they are gbuild or dmake modules?


c:\OpenOfficeDev\openoffice\main\scripting\source\protocolhandler\scripthandler.cxx

does not have symbols.

c:\OpenOfficeDev\openoffice\main\package\source\xstor\xstorage.cxx does
have symbols generated.



On Sat, Jul 4, 2020 at 9:13 PM Patricia Shanahan  wrote:


In the new build system, what is the status of automatic symbol
generation, needed for easy debug.

It is badly broken in 4.1.7, with most modules not getting symbols
generated despite --enable-symbols in the configure parameters. This has
cost me weeks of work on a debug project.

On 7/4/2020 11:44 AM, Damjan Jovanovic wrote:

Hi

In the scons-build branch, I've just pushed a set of 11 commits that
theoretically get 93 out of 105 gbuild modules (88.57%) automatically
converting to gbuild.

The "gotoSCons" converter and the SCons infrastructure in that branch

have

now been developed to such a level that a module can be automatically
converted from gbuild to SCons, from where it can use SCons for all of

the

following:
Building C/C++ objects
Linking shared libraries, static libraries, and executables
Building JUnit tests and running them
Building Google Tests and running them
Building .component files with XSLT
Running Ant sub-builds
Delivering "package" files such as headers
Even doing the impossibly difficult 5 step "AllLangResTarget" (.src ->
merged .src -> .srs -> .res for each language).

I still have to implement Jar, Zip, UnoApi, WinResTarget and SdiTarget,

but

I think only Jar and Zip are worth implementing automatic conversion

for,

as SdiTarget and UnoApi are only used in 5 places each, and

WinResTarget

in

only 2 places, which makes manual conversion for them easier. The

hardest

conversions are already done.

Where does this leave us?

The gotoSCons converter can't support a number of features, like
non-deterministic constructs (ifeq ($(GUI),UNX)), custom make rules,

etc. A

module can only be automatically converted if it doesn't use the
unsupported features. Currently, 35 modules use only supported

features,

and can be converted automatically (this should increase to 39 modules

when

I add Jar and Zip conversion).

Another 58 modules use non-deterministic constructs or custom make

rules.

Converting those 58 could be done through a semi-automated process,

which

involves editing the gbuild files to remove the unsupported features,
running the automated conversion on what is left, then manually

patching

what was removed into the conversion results. Sometimes this is quick

and

easy, at other times probably not.

The final 12 modules use unsupported targets requiring a longer and

mostly

manual conversion to SCons, though even there the supported targets

could

be converted automatically.

The SCons infrastructure does require some cleanup, as I was learning

while

developing, and we still need library naming conversions, tests on
Linux/WIndows/Mac, etc.

The more I've used SCons, the more I've liked it. I've even started

using

it in my own projects at work now. I've found a way to solve every

problem

I've encountered, and the SCons developers have been helpful when I

asked

them questions. Complex functionality like header dependency scanning,
automatic directory creation for output files, using @responsefile for

long

command lines when necessary, and other features gbuild implements
manually, all work in SCons automatically. In 1816 lines of code, our

SCons

infrastructure implements what took gbuild 9418 lines, and SCons is far
more readable and maintainable (even in its current messy state).

The plan isn't to merge this to trunk any time soon. Rather the idea is

to

develop the converter even further, then when it's complete enough,

convert

as many gbuild modules to SCons. Then measure performance of building

those

modules en-masse with SCons alone - if there are performance problems

at

that stage, they are only going to get worse with more modules.

The real test however is converting the other 78 dmake modules to

SCons.

37

of them are 3rd party "externals" like jpeg and zlib, which have their

own

build systems that we just call, so conversion is relatively easy. The
other 41 modules are hard to convert, but gbuild is one of the reason

Re: Automated gbuild -> SCons convertibility now at 88.57%

2020-07-04 Thread Patricia Shanahan


On 7/4/2020 12:24 PM, Damjan Jovanovic wrote:

Given how I've only developed on FreeBSD so far, anything Windows is
probably at negative infinity :) >
Do you have some example modules with that symbols problem, or at least
know whether they are gbuild or dmake modules?


c:\OpenOfficeDev\openoffice\main\scripting\source\protocolhandler\scripthandler.cxx 
does not have symbols.


c:\OpenOfficeDev\openoffice\main\package\source\xstor\xstorage.cxx does 
have symbols generated.




On Sat, Jul 4, 2020 at 9:13 PM Patricia Shanahan  wrote:


In the new build system, what is the status of automatic symbol
generation, needed for easy debug.

It is badly broken in 4.1.7, with most modules not getting symbols
generated despite --enable-symbols in the configure parameters. This has
cost me weeks of work on a debug project.

On 7/4/2020 11:44 AM, Damjan Jovanovic wrote:

Hi

In the scons-build branch, I've just pushed a set of 11 commits that
theoretically get 93 out of 105 gbuild modules (88.57%) automatically
converting to gbuild.

The "gotoSCons" converter and the SCons infrastructure in that branch

have

now been developed to such a level that a module can be automatically
converted from gbuild to SCons, from where it can use SCons for all of

the

following:
Building C/C++ objects
Linking shared libraries, static libraries, and executables
Building JUnit tests and running them
Building Google Tests and running them
Building .component files with XSLT
Running Ant sub-builds
Delivering "package" files such as headers
Even doing the impossibly difficult 5 step "AllLangResTarget" (.src ->
merged .src -> .srs -> .res for each language).

I still have to implement Jar, Zip, UnoApi, WinResTarget and SdiTarget,

but

I think only Jar and Zip are worth implementing automatic conversion for,
as SdiTarget and UnoApi are only used in 5 places each, and WinResTarget

in

only 2 places, which makes manual conversion for them easier. The hardest
conversions are already done.

Where does this leave us?

The gotoSCons converter can't support a number of features, like
non-deterministic constructs (ifeq ($(GUI),UNX)), custom make rules,

etc. A

module can only be automatically converted if it doesn't use the
unsupported features. Currently, 35 modules use only supported features,
and can be converted automatically (this should increase to 39 modules

when

I add Jar and Zip conversion).

Another 58 modules use non-deterministic constructs or custom make rules.
Converting those 58 could be done through a semi-automated process, which
involves editing the gbuild files to remove the unsupported features,
running the automated conversion on what is left, then manually patching
what was removed into the conversion results. Sometimes this is quick and
easy, at other times probably not.

The final 12 modules use unsupported targets requiring a longer and

mostly

manual conversion to SCons, though even there the supported targets could
be converted automatically.

The SCons infrastructure does require some cleanup, as I was learning

while

developing, and we still need library naming conversions, tests on
Linux/WIndows/Mac, etc.

The more I've used SCons, the more I've liked it. I've even started using
it in my own projects at work now. I've found a way to solve every

problem

I've encountered, and the SCons developers have been helpful when I asked
them questions. Complex functionality like header dependency scanning,
automatic directory creation for output files, using @responsefile for

long

command lines when necessary, and other features gbuild implements
manually, all work in SCons automatically. In 1816 lines of code, our

SCons

infrastructure implements what took gbuild 9418 lines, and SCons is far
more readable and maintainable (even in its current messy state).

The plan isn't to merge this to trunk any time soon. Rather the idea is

to

develop the converter even further, then when it's complete enough,

convert

as many gbuild modules to SCons. Then measure performance of building

those

modules en-masse with SCons alone - if there are performance problems at
that stage, they are only going to get worse with more modules.

The real test however is converting the other 78 dmake modules to SCons.

37

of them are 3rd party "externals" like jpeg and zlib, which have their

own

build systems that we just call, so conversion is relatively easy. The
other 41 modules are hard to convert, but gbuild is one of the reasons

that

they were hard, and where SCons is expected to make the greatest
difference. Only once we are building without dmake, without gbuild,
without build.pl, without Cygwin, on all platforms, then it would be the
right time to merge to trunk.

If at some stage in this process we are unhappy with SCons, and some

better

build system can be found, it shouldn't be difficult to change to it. The
converter could output files for that other build system inste

Re: Automated gbuild -> SCons convertibility now at 88.57%

2020-07-04 Thread Patricia Shanahan

In the new build system, what is the status of automatic symbol 
generation, needed for easy debug.


It is badly broken in 4.1.7, with most modules not getting symbols 
generated despite --enable-symbols in the configure parameters. This has 
cost me weeks of work on a debug project.


On 7/4/2020 11:44 AM, Damjan Jovanovic wrote:

Hi

In the scons-build branch, I've just pushed a set of 11 commits that
theoretically get 93 out of 105 gbuild modules (88.57%) automatically
converting to gbuild.

The "gotoSCons" converter and the SCons infrastructure in that branch have
now been developed to such a level that a module can be automatically
converted from gbuild to SCons, from where it can use SCons for all of the
following:
Building C/C++ objects
Linking shared libraries, static libraries, and executables
Building JUnit tests and running them
Building Google Tests and running them
Building .component files with XSLT
Running Ant sub-builds
Delivering "package" files such as headers
Even doing the impossibly difficult 5 step "AllLangResTarget" (.src ->
merged .src -> .srs -> .res for each language).

I still have to implement Jar, Zip, UnoApi, WinResTarget and SdiTarget, but
I think only Jar and Zip are worth implementing automatic conversion for,
as SdiTarget and UnoApi are only used in 5 places each, and WinResTarget in
only 2 places, which makes manual conversion for them easier. The hardest
conversions are already done.

Where does this leave us?

The gotoSCons converter can't support a number of features, like
non-deterministic constructs (ifeq ($(GUI),UNX)), custom make rules, etc. A
module can only be automatically converted if it doesn't use the
unsupported features. Currently, 35 modules use only supported features,
and can be converted automatically (this should increase to 39 modules when
I add Jar and Zip conversion).

Another 58 modules use non-deterministic constructs or custom make rules.
Converting those 58 could be done through a semi-automated process, which
involves editing the gbuild files to remove the unsupported features,
running the automated conversion on what is left, then manually patching
what was removed into the conversion results. Sometimes this is quick and
easy, at other times probably not.

The final 12 modules use unsupported targets requiring a longer and mostly
manual conversion to SCons, though even there the supported targets could
be converted automatically.

The SCons infrastructure does require some cleanup, as I was learning while
developing, and we still need library naming conversions, tests on
Linux/WIndows/Mac, etc.

The more I've used SCons, the more I've liked it. I've even started using
it in my own projects at work now. I've found a way to solve every problem
I've encountered, and the SCons developers have been helpful when I asked
them questions. Complex functionality like header dependency scanning,
automatic directory creation for output files, using @responsefile for long
command lines when necessary, and other features gbuild implements
manually, all work in SCons automatically. In 1816 lines of code, our SCons
infrastructure implements what took gbuild 9418 lines, and SCons is far
more readable and maintainable (even in its current messy state).

The plan isn't to merge this to trunk any time soon. Rather the idea is to
develop the converter even further, then when it's complete enough, convert
as many gbuild modules to SCons. Then measure performance of building those
modules en-masse with SCons alone - if there are performance problems at
that stage, they are only going to get worse with more modules.

The real test however is converting the other 78 dmake modules to SCons. 37
of them are 3rd party "externals" like jpeg and zlib, which have their own
build systems that we just call, so conversion is relatively easy. The
other 41 modules are hard to convert, but gbuild is one of the reasons that
they were hard, and where SCons is expected to make the greatest
difference. Only once we are building without dmake, without gbuild,
without build.pl, without Cygwin, on all platforms, then it would be the
right time to merge to trunk.

If at some stage in this process we are unhappy with SCons, and some better
build system can be found, it shouldn't be difficult to change to it. The
converter could output files for that other build system instead; at
present it's only 498 lines of code in 1 file, that are involved in writing
SCons build files, all we would need is a similar file for that other build
system.

Build systems are not the most exciting part of development, but bad build
systems make development painful, and as a large multi-platform project, we
build a lot. We answer build-related questions on the mailing lists too
often, and new contributors are put off by the current build system. A lot
of what we want to do with AOO, such as ports to Win64, AArch64, newer MSVC
versions, and so on, also involve build-related changes.

Damjan



--
This email has

Re: New Committer: Detlef Nannen

2020-07-01 Thread Patricia Shanahan


On 7/1/2020 6:06 AM, Jörg Schmidt wrote:
...

And there should be no doubt:
Detlef undoubtedly deserves to be a committer, only others have that to the 
same degree. And whoever apparently excludes these others from it(*), makes his 
opinion clear.


This is intended for all AOO participants, not just Jörg. If you know of 
anyone you think should be a committer and is not please send an e-mail 
to priv...@openoffice.apache.org giving their name and the reasons why 
they should be a committer.


--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Compile in a Visual Studio break

2020-06-15 Thread Patricia Shanahan

I have given up on getting symbols throughout AOO. The build system 
unfortunately ignores --enable-symbols for many, if not most, modules 
and partial building and rebuilding are not working for me.


As a workaround, I have a hack for compiling in a break. Visual Studio 
has options to take breaks on exceptions being thrown. It works even in 
code that does not have symbols generated. This e-mail is to make it 
available to anyone in the future having the same problem, including my 
own future self.


Put these lines at the start of the module, near other includes:

#include 
#define ps_report(e) {class e : std::exception{}; try{ throw 
e();}catch(e){}}


At any point where you need a break, put

ps_report(arbitrary_identifier)

The arbitrary_identifier can be any string that meets the syntax 
requirements for an identifier. Build AOO.


Before reaching the intended break, enable break on C++ exception in 
Visual Studio. If the ps_report use is reached, Visual Studio will treat 
it as a breakpoint. The arbitrary_identifier will be displayed as part 
of the exception class name. The call stack is available. You can 
continue from the breakpoint, and the program flow will be unchanged 
because the catch cancels out the exception.


--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Request for build help

2020-06-08 Thread Patricia Shanahan


I am having persistent problems building 4.1.7. The problems also apply
to 4.1.3.

A complete build from clean works, but takes many hours. A build without
cleaning always fails in comphelper.

I have uploaded a typical log file to 
http://www.patriciashanahan.com/apache/log3.txt. My configure parameters 
are attached.


Any suggestions?


--
This email has been checked for viruses by AVG.
https://www.avg.com
SDK_PATH="C:/PROGRA~1/MICROS~1/Windows/v7.0"
WDK_HOME="/cygdrive/c/WinDDK/7600.16385.1"
./configure \
--with-build-version="$(date +"%Y-%m-%d %H:%M")" \
--with-frame-home="$SDK_PATH" \
--with-psdk-home="$SDK_PATH" \
--with-midl-path="$SDK_PATH/bin" \
--with-ant-home="/cygdrive/c/ant/apache-ant-1.9.14" \
--with-jdk-home="C:/PROGRA~2/Java/JDK17~1.0_8" \
--with-csc-path="C:/Windows/Microsoft.NET/Framework/v3.5" \
--with-cl-home="C:/PROGRA~2/MICROS~1.0/VC" \
--with-asm-home="C:/PROGRA~2/MICROS~1.0/VC/bin" \
--with-atl-include-dir="$WDK_HOME/inc/atl71" \
--with-atl-lib-dir="$WDK_HOME/lib/atl/i386" \
--with-mfc-include-dir="$WDK_HOME/inc/mfc42" \
--with-mfc-lib-dir="$WDK_HOME/lib/mfc/i386" \

--with-dmake-url="https://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2;
 \
--with-directx-home="C:\Microsoft_DirectX_SDK_June_2010" \
--enable-win-x64-shellext \
--enable-wiki-publisher \
--without-junit \
--without-stlport \
--with-mozilla-build="/cygdrive/c/mozilla-build" \
--enable-category-b \
--with-lang="en-US" \
--enable-bundled-dictionaries \
--with-packager-list=/cygdrive/c/Source/Pack.lst \
--with-nsis-path="C:/NSIS" \
--with-package-format="installed"


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: macOS and AOO42X

2020-05-17 Thread Patricia Shanahan





On 5/17/2020 3:29 PM, Marcus wrote:

Am 17.05.20 um 23:13 schrieb Brian Barker:

At 16:55 17/05/2020 -0400, Keith N. McKenna wrote:
The Apache® OpenOffice® Projekt is on the road to a bigger update 
for its leading open source office suite.


The changes look good except that its should be either it is or it's 
it would probably be better to use it is rather than the contraction 
it's.


*No!* Once again, in "for its leading open source office suite" the 
"its" is a possessive pronoun, spelled without an apostrophe (cf. his, 
not *hi's!), and does not stand for "it is".


I've replaced the problematic word with "the". If this st also not 
correct, then the blog post could be edited after it was published.


I am putting on my native English speaker hat, to make up for my 
regrettable lack of any skill in German.


"Its" is the possessive form of "It". "It's" is the contraction for "It is".

--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Karma management (Was Re: Wiki Account)

2020-05-16 Thread Patricia Shanahan

I would like the following as a general system, with exceptions for 
particular resources if there is a good reason:


The PMC chair is always an admin. Making the PMC chair an admin should 
be part of the hand over process when we change chairs.


There should be at least one other admin, preferably someone who is 
active on the resource.


Other people get whatever permissions make sense for what they are 
doing, but it should be easy to change, given at least two active admins.


On 5/16/2020 6:56 AM, Carl Marcum wrote:

Hi Matthias,

That's perfect :)

Best regards,
Carl

On 5/16/20 9:40 AM, Matthias Seidel wrote:

Hi Carl,

Am 16.05.20 um 15:31 schrieb Carl Marcum:

That's a good idea.

Also a list of who currently has what karma would be helpful if it
doesn't exist already or another means to find it.

Something like this (needs some more update)?

https://openoffice.apache.org/pmc-faqs.html

Regards,

    Matthias


I think Keith mentioned in another thread that he was an admin in the
mwiki.

Thanks,
Carl

On 5/16/20 7:59 AM, Patricia Shanahan wrote:

I think we need to make a list of powers the PMC chair should have.
That should include adding administrators etc. for all the OpenOffice
resources. Part of handing over the chair should be making the new
chair administrator for each resource.

On 5/16/2020 3:29 AM, Matthias Seidel wrote:

Someone must have the rights...
Otherwise this is just another unpleasant situation.

Anyone?

Am 16.05.20 um 12:27 schrieb Peter Kovacs:

I am not able to process an account opening.

Am 16.05.20 um 11:23 schrieb Matthias Seidel:

Has anyone answered to Jungi?!

Regards,

  Matthias

Am 30.04.20 um 19:48 schrieb Jungi Hong:

Hello,

I am interested in opening a wiki account. I propose the username:
darthdj31

The email would be jhong101...@gmail.com.

Best regards,

Jungi


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Wiki Account

2020-05-16 Thread Patricia Shanahan

I think we need to make a list of powers the PMC chair should have. That 
should include adding administrators etc. for all the OpenOffice 
resources. Part of handing over the chair should be making the new chair 
administrator for each resource.


On 5/16/2020 3:29 AM, Matthias Seidel wrote:

Someone must have the rights...
Otherwise this is just another unpleasant situation.

Anyone?

Am 16.05.20 um 12:27 schrieb Peter Kovacs:

I am not able to process an account opening.

Am 16.05.20 um 11:23 schrieb Matthias Seidel:

Has anyone answered to Jungi?!

Regards,

     Matthias

Am 30.04.20 um 19:48 schrieb Jungi Hong:

Hello,

I am interested in opening a wiki account. I propose the username:
darthdj31

The email would be jhong101...@gmail.com.

Best regards,

Jungi



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org





--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: testers and reviewers for Github

2020-04-26 Thread Patricia Shanahan





On 4/26/2020 4:05 AM, Peter Kovacs wrote:

Hallo all,


We have some pull request (patches) signed in on Github.

We need people to test them and sign them off.

Matthias should not sign everything on his own. I am volunteering here, 
but the question is:


Who else can I count into?


Do you need me to be able to build?

I have started using Ubuntu on VirtualBox, so I can dodge the 
difficulties of building on Windows.





All the Best

Peter



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: about build environment development

2020-04-16 Thread Patricia Shanahan





On 4/15/2020 10:08 AM, Damjan Jovanovic wrote:

On Wed, Apr 15, 2020 at 3:15 PM Jim Jagielski  wrote:





On Apr 15, 2020, at 3:01 AM, Damjan Jovanovic  wrote:


We are also thin on new contributors, and I recall you saying they're
largely scared off by the current build system.



Two points:

   1. I doubt that by the time we finish porting to a whole new build
system, we will even have anyone *wanting* to contribute. With each delay
and push-out on releases, and more time spent working on the build system
instead of AOO itself, we become less and less relevant. Is that really a
priority we should be focusing on? Are the number of people knowledgeable
around scons really greater than what we have now? But I could be wrong,
which leads me to #2...



What would you recommend we focus on instead then?


I would recommend going for robustness, rather than new features. I know 
of some areas for potential improvement:


Array bounds checking, especially during input processing.

Memory allocation checking.

Debug profile corruption.



Ideally, new contributors wouldn't need to be knowledgeable about scons.
The build should be easier to perform, hopefully just "./configure"
followed by "scons" (and scons even implements features that can subsume
./configure too). Already, scons doesn't need the "source winenv.set.sh"
and "cd instsetoo_native" steps to build its modules.



   2. "The conversion from gbuild to scons would largely be automated, fast
and correct." If that is the case, let's test that theory right now.



This has been possible for some time. In the scons-build branch, you can do
the following:

$ cd gotoSCons
$ mvn package
$ java -cp target/gotoSCons-0.1-SNAPSHOT.jar
org.apache.openoffice.gotoSCons.GBuildConverter parsingAnalysis ../main
(per-module output)
Could parse: [MathMLDTD, UnoControls, animations, cosv, cppcanvas,
drawinglayer, eventattacher, fileaccess, i18nutil, idl, io, rdbmaker,
registry, remotebridges, sane, store, svgio, twain, ucbhelper, unixODBC,
xmlreader, xmlscript]
22 out of 105 gbuild modules are parseable

That means 22 modules can already be converted, completely and correctly.
As we add more features to the converter (AllLangResTarget, UnoApi, Junit,
GoogleTest, etc.), that 22 will increase.

The per-module gbuild files are easy to parse. Parsing the syntax takes
only 3 methods and < 100 lines of Java. The non-deterministic ones with
"ifeq ($(GUIBASE),aqua)" require some manual work, but even there, a lot
can be automated. There is some more work involved in semantic conversion:
understanding and converting specific gbuild commands, converting paths to
scons format, etc. but even so, we're on just 1913 lines of code in total
for the converter.

The hard part is to convert gbuild functions in main/solenv/gbuild into
scons, for example, the worst case scenario is AllLangResTarget, for which
this monstrous dependency tree needs to be implemented, with 4 layers of
intermediate targets and complex actions with side effects and header
dependencies (not shown):

#  AllLangResTarget(name)
#  (meta-target; delivers an empty timestamp file)
#^ ^
#   /   \
#  / \
# /   \
#  ResTarget(nameen-US,name,en-US)
ResTarget(nameen-GB,name,en-GB)
#  $(WORKDIR)/ResTarget/$(resName).res
$(WORKDIR)/ResTarget/$(resName).res
#  $(WORKDIR)/ResTarget/nameen-US.res
  $(WORKDIR)/ResTarget/nameen-GB.res
#^   ^^
#| rsc   ||
#|   ||
#  SrsTarget   SrsTarget
SrsTarget
#  $(WORKDIR)/SrsTarget/$(srsName).srs
#  $(WORKDIR)/SrsTarget/uui/res.srs
#^
#| concatenate
#+--+
#|   \
#|\
#  SrcPartTarget   SrcPartTarget
#  $(WORKDIR)/SrsPartTarget/$(srsPartName)
#  $(WORKDIR)/SrsPartTarget/uui/source/ids.src
#^   ^
#| rsc   | rsc
#|   |
# (when not translating) |   | (when translating)
#|   |
#|SrcPartMergeTarget
#|$(WORKDIR)/SrsPartMergeTarget/$(1)
#|
  $(WORKDIR)/SrsPartMergeTarget/uui/source/ids.src
#| ^
#|/
#|   / transex3
#|  / (when translating)
#  $(srsPartName)  /
#  uuid/source/ids.src
#

Re: about build environment development

2020-04-14 Thread Patricia Shanahan

Without knowing enough about the merits of the different build systems 
we got where we are through a history in which a new build system is 
selected every N years, but it takes more than N years to fully switch.


My recommendation is to pick one of the existing build systems, and get 
everything on to it.


On 4/14/2020 9:46 PM, Peter Kovacs wrote:
If one wants to tap in our build system he needs to understand Perl, 
shell, make, ant, XML, configure, ...


This is just way to complicated, especially if you want to bring in an 
IDE to ease code development.



Damjan is not very happy with the features gmake offers. I am not sure 
where exactly the Issue is.


He is opting for SCONs, with the option to extend the build system with 
python. And IMHO on Damjan


Side he is quite serious about it.


Everyone else has not expressed any opinion on this development, so I am 
not sure everyone is aware. The last discussion on this topic,


consent has been strongly to make gmake work.

Another objection is that we got some heavy negative experience report 
from the serf community about SCONS.


Which are switching from, SCONS to cmake.


So in the end we do not have Consent where we want to go. And currently 
it is heavily influenced by Damjan. And this is imho very thin.


I am still like the Idea most to go in the direction of ant / maven, 
despite its flaws. But I am not negative on SCONS either. My main point 
is we need something that


offers a better architecture and is easier to handled and maintained.


Also what we could try is making use of something like portage. Portage 
is pretty easy to use repostory manager used by gentoo, whioch also had 
a community prior to homebrew on mac. It is not very difficult to 
setup.  But it is build to make different build system work together. So 
we could have a build repository, that builds our dependencies. We 
reconstruct our monolith in smaller build libraries, like UNOcore, 
OOFrame, UNOGUI, OOapp, OOpython, StarBasic, OOwizards, extentionXYZ 
(Just saying something), and pick the best build system (cmake, gmake, 
ant, maven, SCONS) for each library. Also we could think on incubating 
Starbasic or UNO, as own Project if they become more interesting. Since 
Portage is made for source build, but can also handle binaries, maybe we 
could add some features that will make it easy to export towards 
specific distributions, making it easy for distributors to export to 
their system. BTW, portage is build on python, so it should work on all 
systems we target. Sorry if this Idea is to crazy for you. It is only an 
idea.



Maybe it is a good time now to bring this topic up in everyones mind.


All the Best

Peter


Am 15.04.20 um 01:14 schrieb Carl Marcum:



On 4/14/20 5:53 PM, Kay Schenk wrote:


On 4/14/20 1:46 PM, Carl Marcum wrote:



On 4/14/20 3:57 PM, Peter Kovacs wrote:
You could try to build only the module, by going into the folder 
and execute make directly.


Hi Peter,

Yes but that doesn't solve my problem with targets not running in 
order or how I can enforce it if possible.

I don't want to break the build if my change ever makes it to trunk.

Eventually if I can get Ant to build the Jar exactly as gbuild does 
I can use that one and my problem goes away.

But until then I was wanting to use the current one that gbuild builds.

Thanks,
Carl


Hi Carl --

From your first post in this thread...

When I build with "build --all" everything works as expected.
When I build with "build --all -P2 -- -P2" the file copy fails 
because the juh.jar file isn't completed.


I recall having issues with the second part -- -P2.

You might try omitting that, and just use "build --all -P2" or maybe 
"build --all -P4"


ref...

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#Building_2 



The build will take a longer but you shouldn't run into the 
"non-completion" issue you're having.


Hope this helps,

Kay


Hi Kay,

Thanks for pointing out what the second parameter meant :)

It would still be good to know if it's possible to declare 
dependencies between targets in gbuild somehow like you can with Ant 
builds.


I'm guessing any final solution that gets into trunk has to build with 
multiple threads per module.


My best option is probably to do the jar build along with the other 
tasks in Ant so I can control when it happens.


Were already using Ant to build java jars in ridljar, jurt, 
officebean, and probably other modules.


I didn't mention it but I'm working on creating the necessary javadoc, 
source, and library jars for distribution through Apache Nexus [1].
But during the build process to avoid the need for a separate Vote 
next time around.


[1] https://wiki.openoffice.org/wiki/Uno/Java/MavenBundles

Thanks again,
Carl



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Nameing in Calc

2020-04-10 Thread Patricia Shanahan


Thanks.

On 4/10/2020 6:52 AM, BMCS wrote:

NO. I am not proposing or considering anything of the kind. I was simply
replying to a question that was raised.
My post said *_IF_* we were looking for an alternative name, NOT that we
should be changing anything.

BTW. Congratulations on your election.

Regards
Dave

On 10/04/2020 14:35, Patricia Shanahan wrote:

I hope you are not seriously considering changing names that have been
the same as long as I can remember (well, maybe not quite back to
Visicalc, the first spread sheet I used).


On 4/10/2020 6:03 AM, BMCS wrote:

On 10/04/2020 13:03, Peter Kovacs wrote:


Am 10.04.20 um 13:02 schrieb Dave:

My response is in-line with your original post.

On 10/04/2020 10:02, Peter Kovacs wrote:

Does anyone remeber the thinking behind this or has it been always
like
this and I just never knew.

To the best of my recollection it has been this way since Sun open
sourced OOo in 2001.

I suspected as much from Pedro's explanation.



I mean I would not notice it if I had not to describe it to someone
else.

Just out of curiosity, what would you consider to be a better
terminology to use for that tab. Obviously the word "Text" would be a
misnomer, since spreadsheet calculations cannot be performed on plain
text, without some form of prior conversion into a numeric format.


an interesting question. Hard to answer.

My choice would be cell characteristics.


If we were looking for an alternative name for the "Format Cells" dialog
that might be a suitable candidate, but the tabs (Font, Font Effects,
Alignment, Borders, Background) are all "Cell Characteristics". We could
then start debating whether or not "Cell Protection" is a characteristic
of a cell :)

I am perfectly comfortable with "Number", but if a change of that tab
name was deemed necessary my vote would go to something like "Type" or
"Class".

Just my 2c worth.

Regards
Dave


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Nameing in Calc

2020-04-10 Thread Patricia Shanahan

I hope you are not seriously considering changing names that have been 
the same as long as I can remember (well, maybe not quite back to 
Visicalc, the first spread sheet I used).



On 4/10/2020 6:03 AM, BMCS wrote:

On 10/04/2020 13:03, Peter Kovacs wrote:


Am 10.04.20 um 13:02 schrieb Dave:

My response is in-line with your original post.

On 10/04/2020 10:02, Peter Kovacs wrote:

Does anyone remeber the thinking behind this or has it been always like
this and I just never knew.

To the best of my recollection it has been this way since Sun open
sourced OOo in 2001.

I suspected as much from Pedro's explanation.



I mean I would not notice it if I had not to describe it to someone
else.

Just out of curiosity, what would you consider to be a better
terminology to use for that tab. Obviously the word "Text" would be a
misnomer, since spreadsheet calculations cannot be performed on plain
text, without some form of prior conversion into a numeric format.


an interesting question. Hard to answer.

My choice would be cell characteristics.


If we were looking for an alternative name for the "Format Cells" dialog
that might be a suitable candidate, but the tabs (Font, Font Effects,
Alignment, Borders, Background) are all "Cell Characteristics". We could
then start debating whether or not "Cell Protection" is a characteristic
of a cell :)

I am perfectly comfortable with "Number", but if a change of that tab
name was deemed necessary my vote would go to something like "Type" or
"Class".

Just my 2c worth.

Regards
Dave

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Patricia elected for ASF Board

2020-04-05 Thread Patricia Shanahan

Thanks. I had hoped to get more active in AOO, but will be giving 
priority to board activities for my Apache time.


On 4/5/2020 8:27 AM, Marcus wrote:

I want to take the chance to congratulate Patricia for electing.

Great to see that one of our circle is engaged in the ASF Board of 
directors.


I wish you all the best and much success. :-)

Marcus

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: dev email not appearing in archives

2020-02-22 Thread Patricia Shanahan


On 2/22/2020 9:10 AM, Carl Marcum wrote:



On 2/22/20 12:05 PM, Matthias Seidel wrote:

Am 22.02.20 um 18:00 schrieb Pedro Lino:

Seems to be a bug in the web page (when sorted by thread).

There is no way to scroll further down (only tested Firefox but maybe 
it works on Chrome/Chromium based browsers)


Workaround: Click on Date (top right) and then in the middle of the 
table header you will see 1.2.Next

But even in Date mode the last message is from Feb. 15th.

Is this hosted by Apache? Then it would be something for Infra...

Regards,

    Matthias


Thanks for confirming.

I'll let them know.


I use lists.apache.org, and it seems to be fine.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Restructuring AOO Build Guide

2020-02-17 Thread Patricia Shanahan





On 2/17/2020 3:45 PM, Carl Marcum wrote:
...

I have  a few thoughts on the step-by-step pages.
1. Break it by AOO version and then OS.  I think there are many sections 
that are probably obsolete now and it's hard to tell, especially for 
someone new.


I think the Step-by-Step guide should be split by OS, and be the main 
guide. Whether it should also be split by AOO version depends on how 
much is different between versions.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Build instructions

2020-02-16 Thread Patricia Shanahan


On 2/16/2020 4:31 PM, Keith N. McKenna wrote:

On 2/15/2020 4:06 PM, Matthias Seidel wrote:


(As you may remember, we wrote about that and I sent you a Dropbox
link where you can download it from)

Regards,

    Matthias


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org


Matthias;
  If you still have that link i can put it into the wiki. I am also more
than willing to help to restructure the Build Guide. It may be best to
start a new thread devoted to just that where all can share ideas on
how to do that.


Are there any legal/copyright issues with supplying Microsoft software 
that way?


What would it take to get to use current software, removing the issue?

I agree about a thread for discussing the structure of the Build Guide.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Build instructions

2020-02-16 Thread Patricia Shanahan

On 2/16/2020 3:02 AM, Peter Kovacs wrote:

Hi,

Maybe it would be more helpful to simplify create setup by profiling a dev
environment setup script for the distributions?

That might be a good long term objective. The step-by-step instructions,
if they worked, could serve as the specification for the script.

We would still need the instructions for people who are not using a VM,
and have some software already installed. For example, even on a machine
I had never used to build AOO, I had Cygwin with Perl.

The immediate survival issue is that we need a set of instructions that
can be carried out. Without that, we cannot recruit programmers. I am
currently at a place in the instructions that tells me to install a
piece of software from a URL that tells me it is not available. A script
would be just as stuck at exactly the same place.

(Note: I am stubbornly pretending to be a new volunteer, or a script,
trying to apply the instructions in order to do my first AOO build.)

With the help of chocolatey we could install cygwin per script. And then add
the other Programms as needed.
Just a crazy idea.

All the best
Peter

Am 15. Februar 2020 23:29:51 MEZ schrieb Patricia Shanahan :

Hi Matthias,

We consistently lose programming volunteers when we ask them to attempt

a build. That makes getting instructions that work, especially for
Windows, the commonest platform, absolutely essential.

On 2/15/2020 1:06 PM, Matthias Seidel wrote:

Hi Patricia,

Am 15.02.20 um 20:36 schrieb Patricia Shanahan:

I have learned enough about Git to attempt a new Windows build. I am

building on a Windows 10 system, using the 64-bit Cygwin, and

keeping

detailed notes of any problems with the instructions.

1. I got very confused between what I should be getting from

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#General_Build_Requirements

and what from

https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Build_with_Cygwin_64-bit

The "general" had a lot of conditionals.

I think it could be made easier to use if one could just start from
the step-by-step and have it link to common web pages for anything
that really is common.

This one I am not going to attempt myself because changes could affect
other platforms that I am not using.

2. There is no /cygdrive/c/temp. /usr/tmp is a temporary directory.

/"(or any other temporary directory of your choice)"/

The fix is to change it to "/usr/tmp (or other temporary directory of
your choice)", though I am not sure why one would need an alternative
to
/usr/tmp.

3. Command "lynx -source
rawgit.com/transcode-open/apt-cyg/master/apt-cyg > apt-cyg" failed
because I had not been told to install lynx.

I have never understood or used these instructions regarding lynx.

Let's get rid of them. The closer we can get to one set of instructions

that work the better. Cygwin's setup automatically installs
dependencies, and is the normal way of installing Cygwin packages. One
would need to use it to get lynx anyway.

Unclear how much can be omitted in this area if the required

packages,

and their dependencies, have already been installed through the

Cygwin

setup program, as will be the case if following the instructions. It

is really necessary to provide an alternative?

4. http://www.microsoft.com/en-us/download/details.aspx?id=3138 gets

an error page "We're sorry, this download is no longer available."

At this point, I am officially stuck.

As anyone else is, Microsoft has pulled that download long ago.

(As you may remember, we wrote about that and I sent you a Dropbox

link

where you can download it from)

Yes, but I am modeling a new recruit trying to build AOO for the first
time, using the latest instructions, on a machine that has not
previously been used to build it. I really am using a computer I got
after the last time I built AOO, and I am being very careful to follow
the instructions as written, ignoring prior experience. My objective is

as much to test the build instructions and get them fixed as to do the
build.

Do we understand why AOO building still requires an obsolete MSVC? Any
way to fix it? This seems to me to be a particularly urgent build
problem.

Perhaps the best we can do here for now is to say "If you get to this
point and do not already have Microsoft Windows SDK for Windows 7 and
.NET Framework 3.5. SP1, send mail to dev@openoffice.apache.org to get
your secret decoder ring."

Thanks,

Patricia

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Build instructions

2020-02-15 Thread Patricia Shanahan

Hi Matthias,

We consistently lose programming volunteers when we ask them to attempt
a build. That makes getting instructions that work, especially for
Windows, the commonest platform, absolutely essential.

On 2/15/2020 1:06 PM, Matthias Seidel wrote:

Hi Patricia,

Am 15.02.20 um 20:36 schrieb Patricia Shanahan:
I have learned enough about Git to attempt a new Windows build. I am
building on a Windows 10 system, using the 64-bit Cygwin, and keeping
detailed notes of any problems with the instructions.

1. I got very confused between what I should be getting from
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#General_Build_Requirements
and what from
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Build_with_Cygwin_64-bit

The "general" had a lot of conditionals.

I think it could be made easier to use if one could just start from
the step-by-step and have it link to common web pages for anything
that really is common.

This one I am not going to attempt myself because changes could affect
other platforms that I am not using.

2. There is no /cygdrive/c/temp. /usr/tmp is a temporary directory.

/"(or any other temporary directory of your choice)"/

The fix is to change it to "/usr/tmp (or other temporary directory of
your choice)", though I am not sure why one would need an alternative to
/usr/tmp.

3. Command "lynx -source
rawgit.com/transcode-open/apt-cyg/master/apt-cyg > apt-cyg" failed
because I had not been told to install lynx.

I have never understood or used these instructions regarding lynx.

Let's get rid of them. The closer we can get to one set of instructions
that work the better. Cygwin's setup automatically installs
dependencies, and is the normal way of installing Cygwin packages. One
would need to use it to get lynx anyway.

Unclear how much can be omitted in this area if the required packages,
and their dependencies, have already been installed through the Cygwin
setup program, as will be the case if following the instructions. It
is really necessary to provide an alternative?

4. http://www.microsoft.com/en-us/download/details.aspx?id=3138 gets
an error page "We're sorry, this download is no longer available."

At this point, I am officially stuck.

As anyone else is, Microsoft has pulled that download long ago.

(As you may remember, we wrote about that and I sent you a Dropbox link
where you can download it from)

Do we understand why AOO building still requires an obsolete MSVC? Any
way to fix it? This seems to me to be a particularly urgent build problem.

Thanks,

Patricia

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Build instructions

2020-02-15 Thread Patricia Shanahan

I have learned enough about Git to attempt a new Windows build. I am 
building on a Windows 10 system, using the 64-bit Cygwin, and keeping 
detailed notes of any problems with the instructions.


1. I got very confused between what I should be getting from 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#General_Build_Requirements 
and what from 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Build_with_Cygwin_64-bit


The "general" had a lot of conditionals.

I think it could be made easier to use if one could just start from the 
step-by-step and have it link to common web pages for anything that 
really is common.


2. There is no /cygdrive/c/temp. /usr/tmp is a temporary directory.

3. Command "lynx -source 
rawgit.com/transcode-open/apt-cyg/master/apt-cyg > apt-cyg" failed 
because I had not been told to install lynx.


Unclear how much can be omitted in this area if the required packages, 
and their dependencies, have already been installed through the Cygwin 
setup program, as will be the case if following the instructions. It is 
really necessary to provide an alternative?


4. http://www.microsoft.com/en-us/download/details.aspx?id=3138 gets an 
error page "We're sorry, this download is no longer available."


At this point, I am officially stuck.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Facebook comment: It is time for an advanced product. please meet with me.


+1

I had assumed that if I read the Facebook post I would get some 
background on what it is about that might justify something other than 
"please post on dev@"


On 2/7/2020 2:17 PM, Andrea Pescetti wrote:

On 07/02/2020 Peter Kovacs wrote:

I have no clue how I should react on this proposal. For me Facebook is
not a business channel.


No way this is worth so many messages to the dev list and a collective 
waste of time on interpreting incomplete information.


The standard way to contact the project is this public dev list. He is 
welcome to do so. He won't get serious consideration if all he can write 
is "please meet with me", of course.


If it is something that for some reason needs to be kept confidential, 
there is a private list.


End of story. This is all we need to answer.

Regards,
   Andrea.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Facebook comment: It is time for an advanced product. please meet with me.

Not much information there. I would ask for some idea what it is about 
before meeting.


On 2/7/2020 9:59 AM, Peter Kovacs wrote:

https://m.facebook.com/story.php?story_fbid=2835088696549989=185963401462545

Strange through my phone I can link. Facebook is a really strange application.
Please have a go.

All the best
Peter

Am 7. Februar 2020 18:50:08 MEZ schrieb Patricia Shanahan :

How about a link to the group or page?

Any idea whereabouts in California? I live in San Diego county, at the
south end, and there are places in California that are hundreds of
miles
from my home.

On 2/7/2020 9:00 AM, Peter Kovacs wrote:

I am sorry. Facebook does not allow external links. If you have a
Facebook acount you can see it in the vistor section

I think it is public. Or I invite you to the facebook site. He posted

a

message on our Apache OpenOffice board. People

usually write how much they love / hate our Software or ask for help.

The message he has placed is in the subject. I have asked him where

he

lives, and he answered CA, but he is flexible. That is all

communication

right now.

Since I answer as AOO, I did not further Chitchat.

He seems to be a older respectable US Citizen. A patriot to his

country.

He seem not to use Facebook a lot. So I would not say he writes

random

comments.

I am curious what his Idea is. But in our definition of serious I

would

not expect this will be something major. But you never know. People

are

awesome and full of surprises. ;)


My Ideas are:

1) Dave could arrange for the meeting. Is this interesting enough for

you?


2) I can chitchat try to get more information, what he wants.

3) I could guide him to private or dev for introduction. And then we
take next steps.

all the best

Peter


On 07.02.20 17:32, Patricia Shanahan wrote:

Can you post a link or something? I have no context.

On 2/7/2020 7:03 AM, Peter Kovacs wrote:

Hello all,

what should I give for an answer?

The person lives in california, in case somebody wants to talk.


All the Best

Peter




-

To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org





-

To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Facebook comment: It is time for an advanced product. please meet with me.


How about a link to the group or page?

Any idea whereabouts in California? I live in San Diego county, at the 
south end, and there are places in California that are hundreds of miles 
from my home.


On 2/7/2020 9:00 AM, Peter Kovacs wrote:

I am sorry. Facebook does not allow external links. If you have a
Facebook acount you can see it in the vistor section

I think it is public. Or I invite you to the facebook site. He posted a
message on our Apache OpenOffice board. People

usually write how much they love / hate our Software or ask for help.

The message he has placed is in the subject. I have asked him where he
lives, and he answered CA, but he is flexible. That is all communication
right now.

Since I answer as AOO, I did not further Chitchat.

He seems to be a older respectable US Citizen. A patriot to his country.
He seem not to use Facebook a lot. So I would not say he writes random
comments.

I am curious what his Idea is. But in our definition of serious I would
not expect this will be something major. But you never know. People are
awesome and full of surprises. ;)


My Ideas are:

1) Dave could arrange for the meeting. Is this interesting enough for you?

2) I can chitchat try to get more information, what he wants.

3) I could guide him to private or dev for introduction. And then we
take next steps.

all the best

Peter


On 07.02.20 17:32, Patricia Shanahan wrote:

Can you post a link or something? I have no context.

On 2/7/2020 7:03 AM, Peter Kovacs wrote:

Hello all,

what should I give for an answer?

The person lives in california, in case somebody wants to talk.


All the Best

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Facebook comment: It is time for an advanced product. please meet with me.


Can you post a link or something? I have no context.

On 2/7/2020 7:03 AM, Peter Kovacs wrote:

Hello all,

what should I give for an answer?

The person lives in california, in case somebody wants to talk.


All the Best

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: need some feedback on source code page changes on project site...

2020-02-06 Thread Patricia Shanahan

I am planning to attempt a check out and build using the instructions. 
I'll wait until the changes are committed, so my build serves as a test 
case.


On 2/6/2020 12:12 PM, Kay Schenk wrote:

Hello all--

The information on obtaining and using source code is outdated on the 
project site --


https://openoffice.apache.org/source.html

I've made changes and attached the .html conversion of my changed 
.mdtext file here. This is not committed yet.


I would appreciate some feedback before I commit this. Thanks.

--
Regards,
Kay



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Audience for AOO (Was: Re: Apache OpenOffice 4.1.7 for OS/2 (and OS/2 based systems like ArcaOS))

2020-01-31 Thread Patricia Shanahan


On 1/31/2020 8:35 AM, Damjan Jovanovic wrote:

On Fri, Jan 31, 2020 at 6:00 PM Pedro Lino  wrote:


Hi Jim


Now sure, if you are running the latest version of Linux, on a high-end

machine, and needs lots of bells and

whistles, then other Office suites are likely more tailored for your

setup.

Actually I'm running a high-end machine with Ubuntu 18.04 LTS (soon to be
updated to 20.04 LTS) and I prefer OpenOffice because of the stability.



The stability cannot be overstated. I have to use a related office suite as
well, but despite some improvements, it has endless, ongoing regressions.
Every release manages to break something new.


My brother is not a programmer, but has been using computers since the 
1960's and is technically competent (retired UK chartered engineer). 
When I mentioned that I had joined the AOO project, he thanked me 
because he uses it. It has all the features he needs, and he does not 
want regressions or having to learn new interfaces every year.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: OpenOffice trunc Assertion Error

2020-01-09 Thread Patricia Shanahan


What happens if you ignore the assertion and carry on?

I had to do that for several assertions when debugging some security 
problems - the problems I was working were higher priority.


On 1/9/2020 1:35 AM, Peter Kovacs wrote:

Hi,

To be clear the Assert is a different issue and needs more research.
The Assert claims a different object is to be used for top level objects. Since 
the issue pops up on top-level object, right at start, I assume something is 
not as it should be designed. The answers on the list suggest that the 
knowledge is not present. So I need to do digging first before I can say what 
to do. I think it may be worth open an issue and collect all informations there.

Thanks pat for the review support I appreciate it.


All the best
Peter

Am 9. Januar 2020 02:55:04 MEZ schrieb Dave Fisher :

Hi -

See inline

Sent from my iPhone


On Jan 8, 2020, at 3:44 PM, Peter Kovacs  wrote:

Hello again,

hope I do not annoy anyone, with my questions.
I have looked deeper in the issue using OpenGrok.

Now the Issue seems pretty clear.
We have only the function signatures:

file: atkwrapper.hxx
85  AtkObject *atk_object_wrapper_new(
86  const ::com::sun::star::uno::Reference<

::com::sun::star::accessibility::XAccessible >& rxAccessible,

87  AtkObject* parent = NULL );

And we have the call for the Function just above this one

(file:atkwrapper.cxx):

AtkObject *
atk_object_wrapper_ref( const uno::Reference<

accessibility::XAccessible > , bool create )

{
g_return_val_if_fail( rxAccessible.get() != NULL, NULL );

AtkObject *obj = ooo_wrapper_registry_get(rxAccessible);
if( obj )
{
g_object_ref( obj );
return obj;
}

if( create )
return atk_object_wrapper_new( rxAccessible );

return NULL;
}

So this is a bit confusing.

Anyone objects if I refactor the above code so we have only one

return statement at the end of the function? I think it is annoying and
you quickly miss the exitpoints of the function.

You are doing this to make a code quality tool quiet?

You will need to carefully understand how to add else clauses to the
code. If the functions is long it will be tedious. Bad clauses will
create very subtle bugs. I would want to build often 

Such changes may also make these functions slightly slower.

If you do this then I think you’ll want someone to review the diff.

Apologies if I’m being negative or discouraging.

Best Regards,
Dave



All the Best
Peter


On 2020/01/07 21:27:44, Peter Kovacs  wrote:



Hello all,

I have build OpenOffice from trunc with debug options. When started

I

get an Assertion Error.
Error: assertion failed!
 From File /home/legine/AOO/main/vcl/unx/gtk/a11y/atkwrapper.cxx at

Line

874
Abort ? (Yes=abort / No=ignore / Cancel=core dump)

Code in Question is:
/* gail_focus_tracker remembers the focused object at the first
  * parent in the hierarchy that is a Gtk+ widget, but at

the

time the
  * event gets processed (at idle), it may be too late to



create the
  * hierarchy, so doing it now ..
  */
 uno::Reference< accessibility::XAccessible > xParent(
xContext->getAccessibleParent() );

 /* The top-level objects should never be of this class

*/

 OSL_ASSERT( xParent.is() );


The Wrapper is not an object right? Only a collection of functions

or do

I read this wrong?

Thx for some help.

All the Best
Peter



-

To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: OpenOffice trunc Assertion Error

2020-01-08 Thread Patricia Shanahan


On 1/8/2020 5:55 PM, Dave Fisher wrote:

Hi -

See inline

Sent from my iPhone


On Jan 8, 2020, at 3:44 PM, Peter Kovacs  wrote:

Hello again,

hope I do not annoy anyone, with my questions.
I have looked deeper in the issue using OpenGrok.

Now the Issue seems pretty clear.
We have only the function signatures:

file: atkwrapper.hxx
85  AtkObject *atk_object_wrapper_new(
86  const ::com::sun::star::uno::Reference< 
::com::sun::star::accessibility::XAccessible >& rxAccessible,
87  AtkObject* parent = NULL );

And we have the call for the Function just above this one (file:atkwrapper.cxx):
AtkObject *
atk_object_wrapper_ref( const uno::Reference< accessibility::XAccessible > 
, bool create )
{
g_return_val_if_fail( rxAccessible.get() != NULL, NULL );

AtkObject *obj = ooo_wrapper_registry_get(rxAccessible);
if( obj )
{
g_object_ref( obj );
return obj;
}

if( create )
return atk_object_wrapper_new( rxAccessible );

return NULL;
}

So this is a bit confusing.

Anyone objects if I refactor the above code so we have only one return 
statement at the end of the function? I think it is annoying and you quickly 
miss the exitpoints of the function.


You are doing this to make a code quality tool quiet?

You will need to carefully understand how to add else clauses to the code. If 
the functions is long it will be tedious. Bad clauses will create very subtle 
bugs. I would want to build often 

Such changes may also make these functions slightly slower.

If you do this then I think you’ll want someone to review the diff.


For some functions, single return is natural and clear. For others, the 
code is simpler, more readable, and clearer with multiple returns. I 
think this may be a case where I would prefer multiple returns, but I 
would be interested in seeing what it looks like if refactored, and open 
to the possibility that it might be clearer.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

PMC Chair

2019-11-21 Thread Patricia Shanahan


One of the resolutions passed at the last board meeting was:

"Change the Apache OpenOffice Project Chair (Jim Jagielski, VP)"

Jim,

I don't know whether congratulation or commiseration is more 
appropriate, so you get whichever you prefer from me.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: C++ standard when building OpenOffice

2019-11-04 Thread Patricia Shanahan





On 11/3/2019 8:15 PM, Damjan Jovanovic wrote:

On Mon, Nov 4, 2019 at 3:49 AM Branko Čibej  wrote:


On 04.11.2019 02:14, Damjan Jovanovic wrote:

Thank you for the info. I haven't had good experiences with Boost in my
Win64 attempts either...

Don, how feasible do you think Go or Rust are, to start using in place of
C++?


Really? You'd rewrite code in a completely different language because
you can't figure out a way to select std::auto_ptr or std::unique_ptr
depending on your build environment?



I said "start using" (for new development), not "rewrite". The Mozilla
project did something similar, they used Rust to develop their new Servo
layout engine, not rewrite the whole of Firefox in it.


That can be considered on its own merits for any new feature. It is not 
a solution to the build problem, because we will still have millions of 
lines of C++ that has to be built for each target. If anything, it will 
make the build problem worse, by adding another language to the mix.


--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: C++ standard when building OpenOffice

2019-11-03 Thread Patricia Shanahan





On 11/3/2019 5:49 PM, Branko Čibej wrote:

On 04.11.2019 02:14, Damjan Jovanovic wrote:

Thank you for the info. I haven't had good experiences with Boost in my
Win64 attempts either...

Don, how feasible do you think Go or Rust are, to start using in place of
C++?


Really? You'd rewrite code in a completely different language because
you can't figure out a way to select std::auto_ptr or std::unique_ptr
depending on your build environment?


I think there are more reasons than that for wanting to move away from 
C++, but I do not think it is feasible. The total size of files whose 
names end in ".cxx" is 5,410,709 lines. Under any reasonable 
productivity assumptions, that would take person-decades to convert.


Maybe a less ambitious project would be feasible. Pick a fairly recent 
version of the C++ standard and STL that is popular - lots of existing 
code written to that version of the standard so compilers and libraries 
are likely to support it for some time into the future. Aim to convert 
to that, so we can use system supplied headers etc.




FWIW, both Go and Rust are far more moving targets than C++, but sure,
that's not going to be a problem, eh.

-- Brane



On Mon, Nov 4, 2019 at 1:08 AM Don Lewis  wrote:


On  3 Nov, Don Lewis wrote:

For much of our history, until fairly recently, the versions of gcc that
we used defaulted to -std=gnu++98 when compiiling C++ code.

When FreeBSD on i386 and amd64 switched from gcc to clang, it also
defaulted to -std=gnu++98.  Clang has been C++11 compliant from version
3.3 onwards.  Around the time of the switch, I added the
-DHAVE_STL_INCLUDE_PATH compiler flag so that clang would use it's own
STL include files instead of the boost TR1 includes.  Clang was
perfectly happy using its own STL include files even though they were
not part of C++98, only C++11.

Later on, when clang 6 changed the default to gnu++14, the build
generated tons warning and some number of errors.  To work around this,
I added the -std=gnu++98 compiler flag to force the old mode.

FreeBSD on powerpc still uses gcc and it recently came to my attention
that the build was broken there.  The FreeBSD port of AOO to powerpc
does not use -DHAVE_STL_INCLUDE_PATH, so it was falling back to the
boost TR1 headers.  The FreeBSD port uses the system boost, and recent
versions of boost have dropped TR1 support.  To work around that, I
tried enabling -DHAVE_STL_INCLUDE_PATH to use the gcc C++ headers.  This
failed badly because the gcc STL headers check to see if the compilation
mode is C++11 or better and immediately error out of this is not the
case.  Switching the compilation mode to c++11 results in the warning
and error spew mentioned above.  I tried modifying the stlport headers
to include the gcc TR1 headers in gnu++98 mode.  That worked better, but
I still got some mysterious C++ errors that I was not able to figure
out.  My next attempt will be to try the boost non-TR1 headers.

That was a dead end. Recent boost appears to assume that the STL headers
are provided by the system.  I'll probably have to switch back to
bundled boost and use its TR1 headers.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Git on Windows

2019-10-31 Thread Patricia Shanahan

I am using Windows 10 Pro, 64 bit. I have cygwin 64 bit installed, and 
would prefer to stick to 64 bit software - it is many years since I've 
had a 32 bit desktop or laptop.


What Git software is recommended and what should I clone for working 
with AOO 4.2 branch?


--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: New computer


Thanks for the write up and links.

On 10/30/2019 11:01 AM, Damjan Jovanovic wrote:

On Wed, Oct 30, 2019 at 6:16 PM Patricia Shanahan  wrote:


On 10/30/2019 8:13 AM, Damjan Jovanovic wrote:

What do you already know? SVN?


RCS, SCCS, and SVN.



I personally did:
git clone https://gitbox.apache.org/repos/asf/openoffice.git
(ie. not GitHub)
which I think used my Apache credentials. If you prefer to clone from
GitHub, and want to link your Apache and GitHub credentials, you can
apparently do it on:
https://gitbox.apache.org/


Any guidance on how to decide which I am likely to prefer?



It doesn't really matter which you start with, because they're each other's
mirrors, and in Git you can always change your local repository's "remote".
For example if you cloned GitHub, and want to switch to GitBox, you don't
need to clone the GitBox link, you can simply do:
git remote set-url origin https://gitbox.apache.org/repos/asf/openoffice.git

With GitHub, you can accept GitHub pull requests from other contributors,
even in your web browser, so it might be a better choice in that regard. I
can't say I personally approve of the GitHub lock-in for that feature
though.


I definitely want to avoid GitHub lock-in. I've seen too many services 
change their terms to be comfortable depending too much on one.







As for how you use Git, if you are interested, I can give you some links,
and my own "Git for SVN users" crash course.


Links would be useful. For me when learning programming languages, "for
dummies" courses work better than conversion courses. The "for dummies"
type of course helps me get into the right mindset for the language. I
don't know whether SVN to Git will be different.



Ok sure:

Graph theory explanations of how branches and Git operations work:
https://eagain.net/articles/git-for-computer-scientists/


This looks like the best starting point for me. I am very comfortable 
with basic graph theory, including DAGs.




The free online book, "Pro Git":
https://git-scm.com/book/en/v2

A detailed guide to various Git options, written for the Wine project but
generally useful:
https://wiki.winehq.org/Git_Wine_Tutorial



I'll try sum it up for you. For SVN users, Git's terminology is straight
from hell. "svn checkout X" checks out a working copy from repository X,
but "git checkout X" switches the current branch to X (among other things).
Git's equivalent is "git clone" (except that the entire repository with
full history and all branches is cloned, not just a working copy.) An SVN
revision is a commit in Git.


So I should really forget SVN, go back to basics, and learn Git on its 
own terms from scratch.


I'll read the rest of this after the graph theory web site.



Everything you commit is only committed locally, and can be undone. You
have to "git push" to send your commits upstream.

The main branch of a project is usually called "master", but in AOO ours is
called "trunk" since we imported from SVN. The branch you are on at the
moment is given by "git branch", which lists all the local branches and
stars the current one. "git status" also shows your current branch and
files changed.

Remote branches can be shown with "git remote show origin". If you "git
checkout" with their name, eg. "git checkout AOO418", it will make a local
branch by that name and switch to it. You can also make a local branch
remote (somehow).

You make new local branches with "git branch ", eg. "git branch
temp". (It's instantaneous: it doesn't have to copy history or anything
like that). You can "git checkout temp" to switch to it, "git branch -D
temp" to delete it. A "detached head" is when you "git checkout" something
that's not a branch (as you can "git checkout" any commit or tag, not just
a branch). If you are just looking around, that's not a problem, but if you
"git commit" on a detached head, that commit isn't referenced from
anywhere, and if you checkout anything else, you will lose that work. If
you don't want to lose it, you can "git branch myWork" to attach a branch
to that new commit, so you can get back to it later (with "git checkout
myWork").

There are 2 important ways of working with branches, merging and rebasing.
Both are only local, until you "git push". Merging in Git is similar to
merging in SVN, changes in one branch get merged into another, but rebasing
is amazing. With rebasing you can rearrange commits and branches to your
liking, split commits, merge commits, reorder commits, delete commits,
change commit messages, reposition an old branch so it starts at a newer
commit (and deal with outdated code locally in that branch before merging
or pushing it), etc. "git rebase -i HEAD~3" opens a text editor with the
la

Re: New computer


On 10/30/2019 8:13 AM, Damjan Jovanovic wrote:

What do you already know? SVN?


RCS, SCCS, and SVN.



I personally did:
git clone https://gitbox.apache.org/repos/asf/openoffice.git
(ie. not GitHub)
which I think used my Apache credentials. If you prefer to clone from
GitHub, and want to link your Apache and GitHub credentials, you can
apparently do it on:
https://gitbox.apache.org/


Any guidance on how to decide which I am likely to prefer?



As for how you use Git, if you are interested, I can give you some links,
and my own "Git for SVN users" crash course.


Links would be useful. For me when learning programming languages, "for 
dummies" courses work better than conversion courses. The "for dummies" 
type of course helps me get into the right mindset for the language. I 
don't know whether SVN to Git will be different.





On Wed, Oct 30, 2019 at 2:00 PM Patricia Shanahan  wrote:


I detangled the cables the hard way - shut everything down, unplugged,
detangled, and put it back together with only the cables that are
currently being used.

Now I do need some advice. What is the best starting point for learning
Git-for-AOO? I do have a GitHub account, with my personal e-mail address
not my apache.org address.

On 10/28/2019 11:33 AM, Patricia Shanahan wrote:

Thanks, but what I need is a magic wand of cable untangling I don't
suppose you have one handy.

In installing my new computer I found that the cables connecting various
computers, displays, router, and printer are a mess.

On 10/28/2019 9:51 AM, Matthias Seidel wrote:

Hi Patricia,

How are things going?
If you are in need of something just let me know...

Regards,

 Matthias

Am 26.10.19 um 06:24 schrieb Patricia Shanahan:

Any opinions on which I should do?


On 10/25/2019 1:27 PM, Matthias Seidel wrote:

Hi Patricia,

If you want to build 4.1.x have a look at:
https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ReadMe.txt

For 4.2.x (and trunk) see:
https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/ReadMe.txt

This is how I do my test builds.

Regards,

  Matthias

Am 24.10.19 um 22:09 schrieb Patricia Shanahan:

Are the Windows 10 instructions up-to-date?

I have just got a shiny new Windows 10 Pro computer, and am planning

a

clean start on AOO building. It will take a day or so for me to
install and set up basic stuff, and then I'll need to install

whatever

I need for AOO building.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org








--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org






--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: New computer

I detangled the cables the hard way - shut everything down, unplugged, 
detangled, and put it back together with only the cables that are 
currently being used.


Now I do need some advice. What is the best starting point for learning 
Git-for-AOO? I do have a GitHub account, with my personal e-mail address 
not my apache.org address.


On 10/28/2019 11:33 AM, Patricia Shanahan wrote:
Thanks, but what I need is a magic wand of cable untangling I don't 
suppose you have one handy.


In installing my new computer I found that the cables connecting various 
computers, displays, router, and printer are a mess.


On 10/28/2019 9:51 AM, Matthias Seidel wrote:

Hi Patricia,

How are things going?
If you are in need of something just let me know...

Regards,

    Matthias

Am 26.10.19 um 06:24 schrieb Patricia Shanahan:

Any opinions on which I should do?


On 10/25/2019 1:27 PM, Matthias Seidel wrote:

Hi Patricia,

If you want to build 4.1.x have a look at:
https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ReadMe.txt

For 4.2.x (and trunk) see:
https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/ReadMe.txt

This is how I do my test builds.

Regards,

 Matthias

Am 24.10.19 um 22:09 schrieb Patricia Shanahan:

Are the Windows 10 instructions up-to-date?

I have just got a shiny new Windows 10 Pro computer, and am planning a
clean start on AOO building. It will take a day or so for me to
install and set up basic stuff, and then I'll need to install whatever
I need for AOO building.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org








--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [DISCUSSION] Build environment future

As a user of the build system, I think we have too many build 
strategies, and should not add another one unless it is absolutely 
essential to do so. Of course I would prefer an IDE, but another round 
of build system changes is far too high a price to pay.


Given that most is on gmake, I would much prefer to stick with gmake.

If we keep changing our collective mind about the build system we will 
never have a consistent system, but will always have some modules on 
each of several systems.


On 10/29/2019 10:25 PM, Peter Kovacs wrote:

Hello Damjan and all


I would like to re-discuss our current plan. Hoping to gain a common view.

Current state is mostly we use gmake, there are still some difficult to
migrate dmake projects. And we use Ant for java.

The plan is not to stop at the dmake -> gmake conversion but to move on
to scons, removing as much dependencies as we can. Right?

I would like to set the target to build everything to Ant, removing as
much dependencies we can.


My arguments are mostly that Ant is supported by most when not all IDEs
and I would really like to have an IDE as working environment, and my
hope is that it is easier maybe to integrate an Ant build environment
then a scons or gmake environment.

  I think this would give us a better base then the plan above. So what
was the arguments against Ant again?


All the Best

Peter


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: New computer

2019-10-28 Thread Patricia Shanahan

Thanks, but what I need is a magic wand of cable untangling I don't 
suppose you have one handy.


In installing my new computer I found that the cables connecting various 
computers, displays, router, and printer are a mess.


On 10/28/2019 9:51 AM, Matthias Seidel wrote:

Hi Patricia,

How are things going?
If you are in need of something just let me know...

Regards,

    Matthias

Am 26.10.19 um 06:24 schrieb Patricia Shanahan:

Any opinions on which I should do?


On 10/25/2019 1:27 PM, Matthias Seidel wrote:

Hi Patricia,

If you want to build 4.1.x have a look at:
https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ReadMe.txt

For 4.2.x (and trunk) see:
https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/ReadMe.txt

This is how I do my test builds.

Regards,

     Matthias

Am 24.10.19 um 22:09 schrieb Patricia Shanahan:

Are the Windows 10 instructions up-to-date?

I have just got a shiny new Windows 10 Pro computer, and am planning a
clean start on AOO building. It will take a day or so for me to
install and set up basic stuff, and then I'll need to install whatever
I need for AOO building.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org






--
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: New computer

2019-10-25 Thread Patricia Shanahan


Any opinions on which I should do?


On 10/25/2019 1:27 PM, Matthias Seidel wrote:

Hi Patricia,

If you want to build 4.1.x have a look at:
https://home.apache.org/~mseidel/AOO-builds/AOO-418-Test/ReadMe.txt

For 4.2.x (and trunk) see:
https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/ReadMe.txt

This is how I do my test builds.

Regards,

    Matthias

Am 24.10.19 um 22:09 schrieb Patricia Shanahan:

Are the Windows 10 instructions up-to-date?

I have just got a shiny new Windows 10 Pro computer, and am planning a
clean start on AOO building. It will take a day or so for me to
install and set up basic stuff, and then I'll need to install whatever
I need for AOO building.

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

New computer

2019-10-24 Thread Patricia Shanahan


Are the Windows 10 instructions up-to-date?

I have just got a shiny new Windows 10 Pro computer, and am planning a 
clean start on AOO building. It will take a day or so for me to install 
and set up basic stuff, and then I'll need to install whatever I need 
for AOO building.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: OpenGrok

2019-10-19 Thread Patricia Shanahan


+1

On 10/18/2019 6:04 PM, Damjan Jovanovic wrote:

Thank you so much!

It works well.


On Sat, Oct 19, 2019 at 1:26 AM Ariel Constenla-Haile <
ariel.constenla.ha...@gmail.com> wrote:


Hi *,

On Thu, Oct 17, 2019 at 3:15 AM Peter Kovacs  wrote:

Server is openoffice-vm1-he-de.Apache. Org


A first attempt is now live at http://openoffice-vm1-he-de.apache.org

It has trunk/master and AOO42X and AOO418 branches indexed.
Tomcat is behind mod_proxy_ajp, I've seen that http://androidxref.com/
uses Apache Coyote, which is said to be a better configuration, but
I've no idea how to use it, if someone is in the know, just comment.

Try it and comment if you find errors, and think of a subdomain name,
for example source.openoffice.org, opengrok.openoffice.org,
xref.openoffice.org, etc.
I'll try to puppetize as much as I can, but opengrok needs manual
intervention.

Regards
--
Ariel Constenla-Haile
La Plata, Buenos Aires
Argentina

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org






-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [vote] AOO417-RC1

2019-09-12 Thread Patricia Shanahan

How long will you allow for testing of the Linux builds between the rebuild and 
releasing them?

Patricia

> On Sep 11, 2019, at 18:30, Jim Jagielski  wrote:
> 
> If RC1 passes, and I do think it is a Good Idea to have a longer-than-normal 
> vote, then the macOS and Windows builds will move, as-is, to the release 
> state; The Linux binaries will be rebuilt, but with no code changes at all, 
> to fix the git short-hash inconsistency between macOS/Win and the Linux 
> builds (the Linux builds use a 7digit hash but the macOS and Windows use a 
> 10digit one, so the About splash pages will show slightly different 
> "versions" (although source code-wise, they are bit-bit exact)
> 
>> On Sep 11, 2019, at 5:48 PM, Peter Kovacs  wrote:
>> 
>> Hi Matthias,
>> 
>> I m sorry I am super nervous about the 12th and I feared with all the 
>> discussion that we will not vote at all or to late.
>> So I just started it.
>> The rc was announced by Jim on the 6th Sept. with the intend to start a vote 
>> on Monday.
>> There was this discussion but it ended with the agreement that we can move 
>> on as is. The views did not differ so much. 
>> 
>> How about the vote proceeds until Jim catches up and then Jim can set the 
>> end date. We have the vote going and people can come and test. I am happy if 
>> we have more testers then the last time.
>> 
>> All the best
>> Peter
>> 
>> Am 11. September 2019 20:38:14 MESZ schrieb Matthias Seidel 
>> :
>>> Hi Peter,
>>> 
>>> before we start a vote people should have the opportunity to download
>>> RC1 and test it:
>>> 
>>> https://dist.apache.org/repos/dist/dev/openoffice/4.1.7-RC1/
>>> 
>>> Regards,
>>> 
>>>   Matthias
>>> 
>>> 
 Am 11.09.19 um 07:31 schrieb Peter Kovacs:
 Hi all,
 
 
 In order to finalize the release, I jump in for Jim, who is
>>> traveling. :-)
 
 Please take your vote.
 
 The Release Candidate is good for production:
 
 [ ] yes / +1
 
 [ ] no / -1
 
 My vote is based on
 
 [ ] binding (member of PMC)
 
 [ ] I have build and tested the RC from source
 
 [ ] I have tested the binary RC
 
 
 All the Best
 Petko
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
 For additional commands, e-mail: dev-h...@openoffice.apache.org
 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
> 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

ApacheConNA

2019-08-25 Thread Patricia Shanahan

I seem to have a good gap in my medical treatments covering early 
September, so I am planning to attend the ApacheCon in Las Vegas. I 
would like to meet any other OpenOffice interested people who will be there.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Build on Windows

2019-05-16 Thread Patricia Shanahan





On 5/16/2019 3:23 PM, Matthias Seidel wrote:

Hi Patricia,

Am 17.05.19 um 00:17 schrieb Patricia Shanahan:



On 5/15/2019 8:06 PM, Damjan Jovanovic wrote:

On Thu, May 16, 2019 at 4:45 AM Patricia Shanahan  wrote:


"Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5.
SP1
(recommended by Microsoft. Note: later versions of the Windows SDK will
not work. AOO can not be built with MSVC 2010 or 2012 - MSVC 2008 is
needed and is found in the Windows 7 SDK)"

Both the links given for installing the software get "download no
longer
available".

Since I have built many times on the machine in question that download
cannot be necessary. Since the instructions do not specify the
files, it
is difficult to search for them.



That isn't good at all.

My 13 March 2018 email entitled "First steps in building with MSVC 14 /
Visual Studio 2015" described some of the work involved in using
newer MSVC
versions to build AOO. That "Windows Kit" needs better integration
into the
build and packaging, but I think it will limit us to Windows 7 and later
(the irony being that the open-source mingw[-w64] toolchain, which only
links to the primordial MSVCRT.DLL, could let us support even Windows
9x).

Hopefully we can also simplify the current situation with the many
MSVCR*
versions we use in the process.

Get started and I'll catch up in a few weeks when I am more free?


I did find old SDK files I already had, probably what I was using
before. Unfortunately, I am now getting


As I already wrote on another list, the SDK is still available via MSDN
(at least it was the last time I looked for it).

But I can also give you access to the installation file, if you like?


Could you check whether your MSDN location still works, and if so update 
the step-by-step to point there? If it does not work then, yes, please 
send me the files.




Regards,

    Matthias



"error: .NET exception occured: System.BadImageFormatException: Could
not load file or assembly 'cli_basetypes' or one of its dependencies.
This assembly is built by a runtime newer than the currently loaded
runtime and cannot be loaded.
File name: 'cli_basetypes'"

Since the build system is not my thing, I think I will wait until you
have time to look at it. If my health then permits, I'll resume AOO
activity.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org





-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Build on Windows

2019-05-16 Thread Patricia Shanahan





On 5/15/2019 8:06 PM, Damjan Jovanovic wrote:

On Thu, May 16, 2019 at 4:45 AM Patricia Shanahan  wrote:


"Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5. SP1
(recommended by Microsoft. Note: later versions of the Windows SDK will
not work. AOO can not be built with MSVC 2010 or 2012 - MSVC 2008 is
needed and is found in the Windows 7 SDK)"

Both the links given for installing the software get "download no longer
available".

Since I have built many times on the machine in question that download
cannot be necessary. Since the instructions do not specify the files, it
is difficult to search for them.



That isn't good at all.

My 13 March 2018 email entitled "First steps in building with MSVC 14 /
Visual Studio 2015" described some of the work involved in using newer MSVC
versions to build AOO. That "Windows Kit" needs better integration into the
build and packaging, but I think it will limit us to Windows 7 and later
(the irony being that the open-source mingw[-w64] toolchain, which only
links to the primordial MSVCRT.DLL, could let us support even Windows 9x).

Hopefully we can also simplify the current situation with the many MSVCR*
versions we use in the process.

Get started and I'll catch up in a few weeks when I am more free?


I did find old SDK files I already had, probably what I was using 
before. Unfortunately, I am now getting


"error: .NET exception occured: System.BadImageFormatException: Could 
not load file or assembly 'cli_basetypes' or one of its dependencies. 
This assembly is built by a runtime newer than the currently loaded 
runtime and cannot be loaded.

File name: 'cli_basetypes'"

Since the build system is not my thing, I think I will wait until you 
have time to look at it. If my health then permits, I'll resume AOO 
activity.



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Build on Windows

2019-05-15 Thread Patricia Shanahan





On 5/15/2019 8:06 PM, Damjan Jovanovic wrote:

On Thu, May 16, 2019 at 4:45 AM Patricia Shanahan  wrote:


"Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5. SP1
(recommended by Microsoft. Note: later versions of the Windows SDK will
not work. AOO can not be built with MSVC 2010 or 2012 - MSVC 2008 is
needed and is found in the Windows 7 SDK)"

Both the links given for installing the software get "download no longer
available".

Since I have built many times on the machine in question that download
cannot be necessary. Since the instructions do not specify the files, it
is difficult to search for them.



That isn't good at all.

My 13 March 2018 email entitled "First steps in building with MSVC 14 /
Visual Studio 2015" described some of the work involved in using newer MSVC
versions to build AOO. That "Windows Kit" needs better integration into the
build and packaging, but I think it will limit us to Windows 7 and later
(the irony being that the open-source mingw[-w64] toolchain, which only
links to the primordial MSVCRT.DLL, could let us support even Windows 9x).

Hopefully we can also simplify the current situation with the many MSVCR*
versions we use in the process.

Get started and I'll catch up in a few weeks when I am more free?

Damjan



Do you have any idea what changed? I have built many, many times on that 
computer, but it looks as though I need to specify more paths to keep 
configure happy. I have old versions of Visual Studio.


---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Build on Windows

2019-05-15 Thread Patricia Shanahan

"Install Microsoft Windows SDK for Windows 7 and .NET Framework 3.5. SP1 
(recommended by Microsoft. Note: later versions of the Windows SDK will 
not work. AOO can not be built with MSVC 2010 or 2012 - MSVC 2008 is 
needed and is found in the Windows 7 SDK)"


Both the links given for installing the software get "download no longer 
available".


Since I have built many times on the machine in question that download 
cannot be necessary. Since the instructions do not specify the files, it 
is difficult to search for them.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [discussion] refactoring OpenOffice

2019-03-02 Thread Patricia Shanahan

My motivation for wanting to update data structures is bug fixing. I've
already had to track down and fix buffer overflows. A general move to
self-expanding buffers and bounds checking would fix bugs we do not yet
know about.

On 3/2/2019 7:16 AM, Jim Jagielski wrote:

FWIW, I agree. We've already seen how simple, obvious changes have a nasty ripple effect. Having a
major restructure "now" would, from what I can see, have a major impact on us being able
to release 4.2.0 in anything close to "soon"...

I also have issues w/ fixing/restructuring things that work... dmake is weird,
but it does seem to work, and unless we can completely rework the entire build
system, I'd prefer to see us work on closing bugs and making releases and port
to gbuild those parts that must be updated.

Of course, this is a volunteer project and no one can, or should, force someone
to work on stuff they don't want to or prevent someone from scratching an itch.
I'd just like the project to be working together with a more unified vision...

On Mar 1, 2019, at 10:31 PM, Patricia Shanahan wrote:

The OpenOffice build system is both complicated and fragile. If you do move
things around, you MUST test the ability to build and install for each
supported OS.

To me, this change seems high risk for low benefit. I would far rather see any
available cycles put into replacing ad-hoc data structures with STL structures.

On 3/1/2019 11:05 AM, Peter Kovacs wrote:

Hello all,
I am really annoyed by the Code. I see repentance and to me a code
concept is totally lacking.
What I would like to do is a general cleanup / refactoring pass.
I would like to start with similar features and move them together in
the same module, maybe even merge them.
As a process I suggest I post a mail with [refactor] in the subject. The
Mail will contain what will be moved merged, I collect all references in
the mail.
If there is no objection within 3+ days I conduct the move. (+ because I
need to find time to move and test the change.)
Is this a process feasible?
All the Best
Peter
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [discussion] refactoring OpenOffice

2019-03-02 Thread Patricia Shanahan

One starting point is my last few patches, which involved a bug in one 
of the string implementations, and buffer overflows.


On 3/1/2019 11:58 PM, Peter Kovacs wrote:

Do you have an example or can you explain how to find these. I'll have a
look.

On 02.03.19 04:31, Patricia Shanahan wrote:

The OpenOffice build system is both complicated and fragile. If you do
move things around, you MUST test the ability to build and install for
each supported OS.

To me, this change seems high risk for low benefit. I would far rather
see any available cycles put into replacing ad-hoc data structures
with STL structures.

On 3/1/2019 11:05 AM, Peter Kovacs wrote:

Hello all,


I am really annoyed by the Code. I see repentance and to me a code
concept is totally lacking.

What I would like to do is a general cleanup / refactoring pass.

I would like to start with similar features and move them together in
the same module, maybe even merge them.

As a process I suggest I post a mail with [refactor] in the subject. The
Mail will contain what will be moved merged, I collect all references in
the mail.

If there is no objection within 3+ days I conduct the move. (+ because I
need to find time to move and test the change.)


Is this a process feasible?


All the Best

Peter




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: [discussion] refactoring OpenOffice

2019-03-01 Thread Patricia Shanahan

The OpenOffice build system is both complicated and fragile. If you do 
move things around, you MUST test the ability to build and install for 
each supported OS.


To me, this change seems high risk for low benefit. I would far rather 
see any available cycles put into replacing ad-hoc data structures with 
STL structures.


On 3/1/2019 11:05 AM, Peter Kovacs wrote:

Hello all,


I am really annoyed by the Code. I see repentance and to me a code
concept is totally lacking.

What I would like to do is a general cleanup / refactoring pass.

I would like to start with similar features and move them together in
the same module, maybe even merge them.

As a process I suggest I post a mail with [refactor] in the subject. The
Mail will contain what will be moved merged, I collect all references in
the mail.

If there is no objection within 3+ days I conduct the move. (+ because I
need to find time to move and test the change.)


Is this a process feasible?


All the Best

Peter




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Bootstrap?

2019-02-03 Thread Patricia Shanahan

I suggest rerunning the configure script. If it is successful, a 
bootstrap should appear. If not, you need to investigate what went wrong 
with configure.


On 2/3/2019 7:45 AM, Pedro Lino wrote:

Hi Nikhil, all

I forgot to mention that I'm building now (as I did before) under Ubuntu 16.04 
x64 so I don't need any dll
Any ideas what happened to bootstrap? Should I simply chmod and execute 
bootstrap.1?
Should I modify the step-by-step guide?

Regards,
Pedro


 On February 3, 2019 at 2:32 PM Nikhil Gupta < nikhilgupta360...@gmail.com 
mailto:nikhilgupta360...@gmail.com > wrote:


 Hi,
 This is the same problem which occurred when I first install AOO,
 For bootstraping the project,
 First you have to completely satisfy all the General requirements which is
 described in this thread-
 https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO

 especially unowinreg.dll which you have to save main/external/unowinreg

 then follow this mail which i followed for configuration
 Peter Kovacs < pe...@apache.org mailto:pe...@apache.org >

 to dev
 You need to do something like:

 autoconf

 ./configure
 --with-epm-url=
 https://sourceforge.net/projects/oooextras.mirror/files/epm-3.7.tar.gz
 --with-dmake-url= 
https://sourceforge.net/projects/oooextras.mirror/files/dmake-4.12.tar.bz2
 --with-lang="en-US de fr it pt ja"
 --enable-wiki-publisher
 --enable-verbose
 --without-stlport
 --enable-category-b
 --enable-opengl
 --enable-dbus
 --without-junit
 --with-package-format="installed archive deb"
 --enable-bundled-dictionaries
 --with-vendor=ASF buildbot - NOT FOR RELEASE
 --with-build-version=%(today)s-Rev.%(got_revision)s

 After that has been finished successfull you can bootstrap



 On Sun, Feb 3, 2019 at 7:08 PM Pedro Lino < pedro.l...@mailbox.org 
mailto:pedro.l...@mailbox.org > wrote:


 > > Hi all


 >

 > > I have built AOO from source in previous versions using 
the step-by-step

 guide

 > >


 > > 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step


 >

 > > Currently (in trunk and all branches from

 https://svn.apache.org/repos/asf/openoffice/) there is no bootstrap 
file
 (only bootstrap.1 which is not set to execute) so

 >

 > > ./bootstrap


 >

 > > doesn't work. Oddly enough I downloaded build 4.1.5 which 
I build

 successfully in the past but it only contains bootstrap.1

 >

 > > Am I missing something?


 >

 > > Regards,

 Pedro

 >




---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Suggestion

2019-01-27 Thread Patricia Shanahan


On 1/27/2019 3:25 PM, Andrea Pescetti wrote:
...
In short, I think adding an e-mail client never made sense, and that 
this was irrelevant even when it was actually in the suite (not named 
OpenOffice yet), but it is even more irrelevant now.


I used StarOffice when it had a mail client, never used its mail, and 
did not see any of my colleagues using it.


There may be a case for an Outlook-replacement mail and scheduling 
client. If so, I think it would be better as an independent project, 
free to pick its programming language, libraries etc.


---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Successful 1st Build!

2019-01-27 Thread Patricia Shanahan

Yes, the first step on this is definitely a feasibility and performance 
study. I would start by making the existing AOO string class a wrapper 
around an STL string. That way, we could experiment with only local 
changes, not finding and changing every place that does string manipulation.


On 1/27/2019 6:51 AM, Peter Kovacs wrote:

I could not find a Issue for that. So I opened a bug[1].

But honestly I think this is might be quite a challenge. I am not sure
if the UTF-implementation is affected by this task.

According to FOSDEM talk from the last years it has some very suboptimal
coding decisions. If that is affected, it might have some affect on our API.

We should investigate this first and make a plan.


all the best

Peter

[1] https://bz.apache.org/ooo/show_bug.cgi?id=128019


On 27.01.19 15:27, Patricia Shanahan wrote:

Another project to consider after this is replacing AOO's own string
implementation with the standard template library string.

On 1/27/2019 4:32 AM, Peter Kovacs wrote:

Awesome!

Okay, next Step. Let me see if I have some Ideas.

How about this one here:

https://bz.apache.org/ooo/show_bug.cgi?id=118788

It is about tweaking a LibreOffice patch to our code. The patch is dual
licensed so we can use this. Which is awesome.

It may be a good low hanging fruit to grapple for you. Or a bad one, but
then we know it hangs higher. :P


All the best

Peter


On 26.01.19 23:28, Nikhil Gupta wrote:

Hi everyone,
I successfully build the open-office on my system.Now I am looking
forward
to where I can start contributing to the project. I have 2 year
programming
experience in c++ mainly functional programming.
So if there any guide available there it would be appreciated.

Thanks.
Nikhil




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Successful 1st Build!

2019-01-27 Thread Patricia Shanahan

Another project to consider after this is replacing AOO's own string 
implementation with the standard template library string.


On 1/27/2019 4:32 AM, Peter Kovacs wrote:

Awesome!

Okay, next Step. Let me see if I have some Ideas.

How about this one here:

https://bz.apache.org/ooo/show_bug.cgi?id=118788

It is about tweaking a LibreOffice patch to our code. The patch is dual
licensed so we can use this. Which is awesome.

It may be a good low hanging fruit to grapple for you. Or a bad one, but
then we know it hangs higher. :P


All the best

Peter


On 26.01.19 23:28, Nikhil Gupta wrote:

Hi everyone,
I successfully build the open-office on my system.Now I am looking forward
to where I can start contributing to the project. I have 2 year programming
experience in c++ mainly functional programming.
So if there any guide available there it would be appreciated.

Thanks.
Nikhil




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Successful 1st Build!

2019-01-26 Thread Patricia Shanahan


CONGRATULATIONS!


On 1/26/2019 2:28 PM, Nikhil Gupta wrote:

Hi everyone,
I successfully build the open-office on my system.Now I am looking forward
to where I can start contributing to the project. I have 2 year programming
experience in c++ mainly functional programming.
So if there any guide available there it would be appreciated.

Thanks.
Nikhil



---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: branch 4.1.7?

2019-01-21 Thread Patricia Shanahan

I agree that the focus should be on 4.2.0. However, I strongly favor 
having a ready-to-go 4.1.7. Any day, we could encounter a really 
serious, must-fix-immediately, security bug. Having as much as possible 
done ahead of time will reduce the delay from knowing the fix to end 
users having the fix.


On 1/21/2019 8:36 AM, Jim Jagielski wrote:

Gotcha. I was just thinking that if we had a 4.1.7 branch in a ready-to-go 
stage, if we needed to do another 4.1.x release it would be already there.

But agree that the focus should be on 4.2.0


On Jan 21, 2019, at 11:25 AM, Rory O'Farrell  wrote:

On Mon, 21 Jan 2019 11:12:12 -0500
Jim Jagielski  wrote:


Does it make sense to create a branch of 4.1.7 from 4.1.6...?


No, unless for some urgent fix.  I think better to continue with 4.2.0, then on 
to 5.0

4.2.0 editing OK in Writer (60k word file, book format, no 
illustrations/tables).  A simple spreadsheet working OK; existing Impress 
presentations displaying, apart from two where slide backgrounds cause crash. 
Multimedia in new presentations not yet checked.

--
Rory O'Farrell 

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org




-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Latest test builds

2019-01-21 Thread Patricia Shanahan





On 1/21/2019 7:37 AM, Matthias Seidel wrote:

Am 21.01.19 um 16:18 schrieb Rory O'Farrell:

On Mon, 21 Jan 2019 16:09:33 +0100
Matthias Seidel  wrote:


Hi Rory,

Am 21.01.19 um 15:29 schrieb Rory O'Farrell:

On Mon, 21 Jan 2019 08:39:23 +0100
Peter Kovacs  wrote:


Hi Rory,

do we have a Bug for this?


All the Best

Peter

Seems to be bug 115156
I have added my earlier information to that bug.

Can you please attach a file that crashes?

I can not reproduce this behavior with any docx I have available.

Regards,

    Matthias

Sample file attached to bug report 115156


Opened fine with AOO420m1(Build:9800)  -  Rev. 1851640 (Jim's build) on
Xubuntu 18.04.1 (64-bit)

When exactly should the crash occur?

Matthias


I opened it on MS Windows 10, using the 4.1.6 download from Sourceforge. 
No problems. This is significant because one of the changes in 4.1.6 
involves expanding line separators from one character to two, which only 
happens when opening a file on an MS Windows system.


I think we need more information on where this is happening. Also, I 
wonder whether profile deletion affects it.






Rory


Rory

On 20.01.19 17:45, Rory O'Farrell wrote:

On Sun, 20 Jan 2019 10:28:53 -0500
Jim Jagielski  wrote:


I've uploaded the latest test builds for macOS and Linux 64.
These are based on ~r1851640 and include 2 main updates from
the earlier one:

  o beanshell now included
  o macOS path bug should now be squashed 
(https://bz.apache.org/ooo/show_bug.cgi?id=127965)

Let me know if anyone wants me to kick off a Linux 32bit
build.

Find them here:

  http://home.apache.org/~jim/AOO-builds/4.2.0-dev-r1851640/

Cheers!


I have seen a report that 4.1.6 is failing to open .docx files.  4.2.0 
(r1851640) and Jim's earlier version are also failing with .docx files.  The 
latest 4.2.0 will crash with a small .docx (~20KB) and offer to recover it; it 
will then display it.  With a larger .docx (365 KB) it will crash, and be 
unable to recover or display that file. It also does not identify the file with 
which it has crashed or is trying to recover. I have not checked these 
behaviours against 4.1.6

This does not present any immediate problem for me, as I work only in .odt format, but 
after repairing a corrupt .docx file on forum for a user, I was unable to open it for 
testing, although the repaired document.xml passed a "Well-formed XML" check.



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org








---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Win64 progress at almost 50%; the challenging Win64<->UNO bridge looms

2018-12-02 Thread Patricia Shanahan

I have many years of professional assembly language programming 
experience. I have learned several assembly languages, but not one for 
Win64. I also have a good general understanding of stack management and 
call/return from compiler and operating system work.


Would it be useful for me to start learning the appropriate assembly 
language and stack management? If so, I would like pointers to the 
assembler and ABI etc. conventions.


On 12/1/2018 12:22 AM, Damjan Jovanovic wrote:

Hi

At least 81 modules (44.26%) successfully build on Win64 now, up from 67
(36.61%) before.

At present the build breaks in main/bridges, which I can hack past, but
then modules like cli_ure and i18npool break, probably because they need
the missing Win64 UNO bridge.

This Win64 <-> UNO bridge has to call arbitrary methods, translate
arbitrary exceptions, etc. between UNO and C++. It has to be written
predominantly in assembly language, and needs to implement the platform's
calling convention, deal with its ABI, RTTI, etc. - quite a challenge.

Wish me luck, or join and help?

Damjan



---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: starting 4.1.7 and 4.2.0 Releases

2018-11-12 Thread Patricia Shanahan





On 11/12/2018 2:49 PM, Andrea Pescetti wrote:

On 11/11/2018 Peter Kovacs wrote:

I suggest that we start right away with an Parallel development of 4.1.7
Release branch.


First, we'll have to officially release and announce 4.1.6.

Then energy should really go to 4.2.0. Only if there are any outstanding 
bugs or regressions we should release a 4.1.7.


I think that, unlike 4.2.0 that still requires lots of efforts, 4.1.x is 
so predictable that we could even have a defined process for it, like:
- Early January 2019 (not earlier) we discuss whether it is desirable to 
have a 4.1.7

- Late January 2019 we release 4.1.7 in case
- Then everybody goes back to working on 4.2.0 for some time
- Then we repeat in, say, April or even later.

Otherwise we'll always risk to fit "yet another small fix" into 4.1.x 
instead of making progress on 4.2.0. The 4.1.x releases had the merit to 
expand the basis of potential Release Managers (a lot of people 
alternated in the Release Manager role and turn-over is a good thing), 
but we can't go on wasting energy on 4.1.x.


But again: first, we'll have to officially release and announce 4.1.6.


The way I see it, we should be keeping 4.1.x for security fixes that 
cannot wait until 4.2.0. As such, we may need to decide to release 4.1.7 
at any time. It needs to be ready to go ASAP if a really serious 
security bug shows up.


---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: moving to git !?

2018-11-05 Thread Patricia Shanahan

I am going to have to learn git. No big deal - revision control systems 
go out of fashion every few years and it becomes time to learn a 
currently fashionable one.


Can you recommend a book or tutorial? I've used RCS and SCCS as well as, 
obviously, Subversion.


On 11/5/2018 2:37 PM, Peter Kovacs wrote:

Hello all,

We had the discussion 1 year ago to move to git. For me it was a clear
vote for this move. However nothing happened when we released 4.1.4.

https://lists.apache.org/thread.html/4db20d193cc30850e63dc03378a20462d1e5c113e566fffd6c776d1c@%3Cdev.openoffice.apache.org%3E


It was somewhat unlucky. We should start to prepare the move. I think it
is okay to do this now. After that we should start with 4.1.7 release
and 4.2.0 release preparations.

We can also start the uno split if Damjan is still in this idea.


Also we need to check on the pull workflow with infra. Any volunteers to
do this?

Any Concerns with this initiative?



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Linux building problem (Was Re: [vote] OpenOffice Release Candidate 4.1.6 RC1)

2018-11-01 Thread Patricia Shanahan

Your mail actually went to dev@, which is fine because I have no 
experience building AOO on Linux, and dev@ is the right place to ask for 
help. You should use a more appropriate subject.


On 11/1/2018 4:49 AM, Pedro Lino wrote:

Hi Patricia

I'm taking this opportunity to write to you directly (I hope this is not a 
problem)

Do you have experience building in Linux?

I have found this obstacle but no one on the dev mailing list answered (which 
worries me since I have been trying to contribute to this project...)

Any idea how to solve these dependencies problem?

Thank you in advance!

Best,
Pedro

plino@Latitude-E6520:/$ sudo apt-get install bison flex libarchive-zip-perl 
libcups2-devlibpam0g-dev gperf libfreetype6-dev libxaw7-dev 
libfontconfig1-devlibxrandr-dev patch libgconf2-dev libgnomevfs2-dev 
ant libgtk2.0-devjunit junit4 libidl-dev liborbit2-dev libwww-perl  
  libxml-parser-perl autoconf libssl-dev libpam-dev libgstreamer\*
Reading package lists... Done
Building dependency tree
Reading state information... Done
Note, selecting 'libpam0g-dev' instead of 'libpam-dev'
Note, selecting 'libgstreamer-plugins-base1.0-dev' for glob 'libgstreamer*'
Note, selecting 'libgstreamer0.10-0' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-vaapi1.0-dev' for glob 'libgstreamer*'
Note, selecting 'libgstreamer1.0-dev' for glob 'libgstreamer*'
Note, selecting 'libgstreamermm-1.0-0v5' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-plugins-base0.10-0' for glob 'libgstreamer*'
Note, selecting 'libgstreamer1.0-0-dbg' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-plugins-base0.10-dev' for glob 'libgstreamer*'
Note, selecting 'libgstreamermm-1.0-0' for glob 'libgstreamer*'
Note, selecting 'libgstreamermm-1.0-dev' for glob 'libgstreamer*'
Note, selecting 'libgstreamermm-1.0-doc' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-ocaml' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-ocaml-dev-5f1y4:i386' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-plugins-good1.0-dev' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-plugins-good1.0-0' for glob 'libgstreamer*'
Note, selecting 'libgstreamer0.10-dev' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-plugins-bad0.10-0' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-ocaml-dev-dh5s9' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-plugins-base1.0-0' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-ocaml-5f1y4:i386' for glob 'libgstreamer*'
Note, selecting 'libgstreamer0.10-0-dbg' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-java' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-plugins-bad1.0-dev' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-ocaml-dev' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-plugins-bad1.0-0' for glob 'libgstreamer*'
Note, selecting 'libgstreamer1.0-0' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-ocaml-dh5s9' for glob 'libgstreamer*'
Note, selecting 'libgstreamer-ocaml' instead of 'libgstreamer-ocaml-dh5s9'
Note, selecting 'libgstreamer-ocaml-dev' instead of 
'libgstreamer-ocaml-dev-dh5s9'
Note, selecting 'libgstreamer-ocaml:i386' instead of 
'libgstreamer-ocaml-5f1y4:i386'
Note, selecting 'libgstreamer-ocaml-dev:i386' instead of 
'libgstreamer-ocaml-dev-5f1y4:i386'
autoconf is already the newest version (2.69-9).
autoconf set to manually installed.
libwww-perl is already the newest version (6.15-1).
libwww-perl set to manually installed.
libxml-parser-perl is already the newest version (2.44-1build1).
libxml-parser-perl set to manually installed.
libgstreamer-ocaml is already the newest version (0.2.0-2build2).
libgstreamer0.10-0 is already the newest version (0.10.36-1.5ubuntu1).
libgstreamer0.10-0 set to manually installed.
libarchive-zip-perl is already the newest version (1.56-2ubuntu0.1).
libarchive-zip-perl set to manually installed.
libfontconfig1-dev is already the newest version (2.11.94-0ubuntu1.1).
libfontconfig1-dev set to manually installed.
libfreetype6-dev is already the newest version (2.6.1-0.1ubuntu2.3).
libfreetype6-dev set to manually installed.
libgstreamer-plugins-base1.0-0 is already the newest version (1.8.3-1ubuntu0.2).
libgstreamer-plugins-base1.0-0 set to manually installed.
libgstreamer-plugins-base1.0-dev is already the newest version 
(1.8.3-1ubuntu0.2).
libgstreamer-plugins-good1.0-0 is already the newest version (1.8.3-1ubuntu0.4).
libgstreamer-plugins-good1.0-0 set to manually installed.
libgstreamer1.0-0 is already the newest version (1.8.3-1~ubuntu0.1).
libgstreamer1.0-0 set to manually installed.
libgstreamer1.0-dev is already the newest version (1.8.3-1~ubuntu0.1).
libssl-dev is already the newest version (1.0.2g-1ubuntu4.13).
libssl-dev set to manually installed.
patch is already the newest version (2.7.5-1ubuntu0.16.04.1).
patch set to manually installed.
libgstreamer-plugins-bad1.0-0 is already the newest version (1.8.3-1ubuntu0.2).

Re: [vote] OpenOffice Release Candidate 4.1.6 RC1

2018-10-31 Thread Patricia Shanahan

Since this is a release vote, it is governed by the Apache policy on 
Release Approval at 
http://www.apache.org/legal/release-policy.html#release-approval


"Before casting +1 binding votes, individuals are REQUIRED to download 
all signed source code packages onto their own hardware, verify that 
they meet all requirements of ASF policy on releases as described below, 
validate all cryptographic signatures, compile as provided, and test the 
result on their own platform."


Because of the extent to which our users depend on the compiled 
packages, if I were participating in the vote I would also download and 
test some of them, but building from signed source is required for a 
binding +1.


On 10/31/2018 3:30 PM, Marcus wrote:

Thanks for the vote.

To make it an official vote I miss the following information:

- What exactly do we vote for (link to the source and binaries)?
- What is the time for the vote? Please more than just the normal 72 
hours so that we all can use a weekend for more testing.


Thanks

Marcus



Am 31.10.2018 um 22:20 schrieb Peter Kovacs:

This is about a small maintenance Release. We fix various Issues.

Please take your vote.



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Windows builds

2018-10-28 Thread Patricia Shanahan

I should be able to give some time and attention to AOO during the next 
few weeks.


Is the step-by-step building guide up to date for Windows?

Does it now work for Windows 10?

Any gotchas I need to watch out for?

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Correct sentence about OpenOffice

2018-08-09 Thread Patricia Shanahan

As a matter of curiosity, why does the first change affect any language 
other than English?


I do agree with the change. (I am a native speaker of English English, 
and fluent in written US English).


On 8/9/2018 9:19 AM, Matthias Seidel wrote:

Hi Pedro,

Remember, the change would have to be localized for all available
languages... ;-)

And we have (at least) two different locations for such a string.
Whatever we choose, it should be identical.

Regards,

    Matthias

P.S.: Please allow at least 72 hours time for others to give their feedback.


Am 09.08.2018 um 13:44 schrieb Pedro Lino:

Hi Matthias



Yes, that wording always irritated me...

 On Windows the tooltips says:
 The office productivity suite compatible to the open and standardized
 ODF document format. Supported by The Apache Software Foundation.


I will then switch "compatible to" to "compatible with"

and "Supported by the Apache OpenOffice" to "Supported by the Apache Software 
Foundation."

(with a lowercase "the" since it is the ASF, not the TASF :) )

if there is no opposing feedback


Regards,

Pedro






---
This email has been checked for viruses by AVG.
https://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: A 4.1.6 Release

2018-07-21 Thread Patricia Shanahan

I don't think the decision of whether to do a 4.1.7 is something the PMC 
can decide, and it won't be until 4.2 is the established field release. 
If you get hit with security bugs, you have to fix the field release, 
whether you like it or not. When 4.2 is established in the field, you 
will have a choice between fixing 4.1.x or withdrawing support for 4.1.x.


On 7/20/2018 11:28 PM, Peter Kovacs wrote:

I hope i have time on Sunday. I wanted to proceed last Sunday but failed on 
this.
Currently my calendar is kind of full. Next possible opportunity is conning 
Wednesday.

I am undecided if the 4.1.6 will be the last release. But after 4.1.6 I agree 
4.2.0 beta should get priority. I can imagine that at least one maintenance 
release could be possible while we stabilize 4.2.0. In the beta phase.


Am 19. Juli 2018 19:49:46 MESZ schrieb Matthias Seidel 
:

Back to the topic:

If we want to release 4.1.6, we should start the process described
here:
https://cwiki.apache.org/confluence/display/OOOUSERS/How+to+Cook+a+Release

That said, 4.1.6 should really be the last 4.1.x. (my opinion). We have
to get 4.2.0 releasable!

Regards,

    Matthias


Am 04.07.2018 um 23:45 schrieb Marcus:

Am 04.07.2018 um 22:46 schrieb Kay Schenk:

On Wed, Jul 4, 2018 at 1:00 PM, Marcus  wrote:


Am 04.07.2018 um 08:23 schrieb Peter Kovacs:


I think Jim is referring to the gstreamer situation, where we

decided

that we skip CentOS6 more or less for 4.2.0.And one argument was,
if they
want something they should support us. This is not showing

sympathy

for a
small user group that uses very old software for 2 more years

until

they
have to move to CentOS 7. I personally think that the gstreamer
Topic can
be solved after we have released a beta version. Damjan and I have
pointed
out a lot of possible ways to deal with the issue. Just for now I
think we
have other problems then gstreamer in 4.2.0. I think it is my

fault

that I
put that argument so much in the front line, but that stuck for

me.


In the last months we had a drop in activity. And more then one

topic

received not the attention it deserved. I would not conclude that
anyone
has stopped caring at this point in time.


Let us conclude for now:
4.1.x is still in maintenance. And in my opinion we could think of
maintaining it until 2020 when CentOS6 drops out of maintenance.

Some

support from CentOS6 side would be nice. But we need to search
someone for
this.
I have that on my todo list, but did not manage to follow it up.



incl. gstreamer 0.1.0 that is now within the 4.1.x code.

PS:
CentOS 6 will be supported until Nov 2020; which means another ~2.5
years.

4.2.0 has I think 3 bugs we know about and that blocks a beta

release.

Current target for building with gstreamer is CentOS7. Building
without
gstreamer could be done on CentOS6. We should keep the code in
trunc CentOS
6 compatible where ever we can for now. That will make it easy to
back port
patches to 4.1.x if we decide to maintain 4.1.x until EOL of

CentOS6.




In 4.2.0 we can still keep gstreamer 0.1.0 or update to something
newer.
To be honest, I don't care *about this special topic*.

And it is only relevant on Linux, right?

IMHO more relevant is the baseline: When we increase the CentOS
version we
also raise the sysreq for Linux kernel, glibc, etc. This has a much
bigger
impact for our users.


You are absolutely correct about this, Marcus. Monitoring the

32-bit

Linux
downloads might help here. It does seem like AOO could be moving

away

from
32-bit for Linux and other operating systems. I don't know what
impact this
will have overall though.


I don't remember exactly, does the gstreamer 0.1.0 vs. 1.0.0
discussion is also connected to the Linux 32-bit builds? If so, a
solution could be indeed to drop the 32-bit builds. From SF.net stats
I get the following (2018-01-01 until today).

BTW:
Very likely it's the used OS the download is started from. And not

the

OS where OpenOffice should be installed on.

OS    %
---
Windows    86,1165
Macintosh 7,8424
Unknown 4,9012
Linux 1,0621
Android 0,0762
BSD 0,0011
Solaris 0,0006

But even then, I'm sure the most downloads from resp. for Linux will
be for 64-bit.

Has anybody more exact numbers - or an idea how to get them?

Marcus




On 03.07.2018 23:50, Matthias Seidel wrote:



What impact has Ant 1.10.x exactly on older machines?
It is no problem for me to build the Windows version with Ant
1.9.12. As
long as we use Java 8.

But again, I just did a personal build to test AOO 4.1.x with

Java 8.

Nothing else.
To be more precise: I was the only one who cared. No response

from

other
members!


Am 03.07.2018 um 23:19 schrieb Jim Jagielski:


The above made it appear that Ant 1.9.x was no longer supported

plus

had some sort of security related issue making it unsuited for
AOO... ie,
we *needed* to use Ant 1.10 not just that we now *can* use it.

How about showing some

Re: SVN trunk: Windows build crashes on startup

2018-04-11 Thread Patricia Shanahan


Copied the wrong revision number. It should be 1814901.

On 4/11/2018 6:46 AM, Patricia Shanahan wrote:
My Windows debug builds are based on revision 1828829. (I have avoided 
updating because recent changes are not relevant to the problems I'm 
debugging, and the Windows builds do not seem to be very stable right now.)


On 4/11/2018 4:29 AM, Damjan Jovanovic wrote:

Hi

First I thought it was a patch I was developing, but even with a clean
rebuild, the Windows binaries reproducibly crash during startup.

It's not a debug build so I can't debug further.

Can anyone provide the SVN revision of a Windows build that works for 
them,

so I have a starting point for a regression test?

Damjan



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: SVN trunk: Windows build crashes on startup

2018-04-11 Thread Patricia Shanahan

My Windows debug builds are based on revision 1828829. (I have avoided 
updating because recent changes are not relevant to the problems I'm 
debugging, and the Windows builds do not seem to be very stable right now.)


On 4/11/2018 4:29 AM, Damjan Jovanovic wrote:

Hi

First I thought it was a patch I was developing, but even with a clean
rebuild, the Windows binaries reproducibly crash during startup.

It's not a debug build so I can't debug further.

Can anyone provide the SVN revision of a Windows build that works for them,
so I have a starting point for a regression test?

Damjan



-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Back to OpenOffice




On 3/24/2018 6:10 AM, Matthias Seidel wrote:

You can try revision 1827295, I could build it successfully with this
configuration:
https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/ReadMe.txt

Later revisions seem to be broken (on Windows) for the moment.


The step-by-step lists the Windows Driver Kit installation as 
"Optional". If I don't install it, what should I use for WDK_HOME?


---
This email has been checked for viruses by AVG.
http://www.avg.com


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Which C++ language version?


What version of the C++ standard should we code to?

For example, can the move to STL use features that were added in C++ 11?

-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Memory management strategy


On 3/25/2018 10:44 AM, Pedro Giffuni wrote:

Somewhat related ...

I have been considering the use of APR pools:

http://www.apachetutor.org/dev/pools

It would be great to have the memory managed by the same technology used 
in Apache httpd.


I need to think about this. It seems very appropriate for transaction 
processing. I am not so sure it is a good fit for AOO.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Memory management strategy

Currently, AOO uses a lot of finite size arrays. Ideally, overflows will 
be detected and lead to an error message, but that still prevents 
processing of the user's documents.


Computer memories and swap spaces are still increasing in size, so the 
array size limits are more likely to be the limiting factor on document 
sizes.


I can see two main strategies, but I'm open to additional suggestions.

1) Keep the finite size arrays, but periodically review them to see if 
the sizes should be increased.


2) Use automatically extending STL structures. If a document is too big 
or uses too many instances of some array element, the symptom will be 
the process as a whole running out of memory. We would have to make sure 
all memory allocation failures are handled smoothly.


This somewhat ties in with exception handling strategy. As we turn what 
used to be silent out-of-bounds conditions into exceptions, it is 
important to avoid arbitrary catching and hiding of all exceptions.


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Back to OpenOffice