Re: docx2odt converters

2021-09-16 Thread Carl Marcum

Hello Guy,

I can't tell from this what the issue is.  Is it docx format and what 
happens when opened in AOO?


Best regards,
Carl

On 9/15/21 4:58 AM, Guy Waterval wrote:

Hello all,

I received a mail from a user having difficulties importing MS Word
documents to AOO.  Here is the text of the message :
"I am having a problem displaying a C/D (that is formatted in Word) , but I
have Apache Open Office installed on my Win.10 system. I would like to
avoid  having to go through Google & I would like a free program".
As I never import MS documents in AOO, I have no experience with such a
problem. I'd like to know if somebody has an experience with the docx2odt
converters available on the web.

Many thanks for your help.



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



Re: the "Extensions and Templates" webpage - minor enhancements

2021-08-29 Thread Carl Marcum

Hi Czesław,

On 8/27/21 5:14 AM, Czesław Wolański wrote:

Hi all,

the "Extensions and Templates" webpage:

https://www.openoffice.org/extensions/index.html

The image "EXTENSIONS" somewhat overwhelms and there is no adequate image
for "TEMPLATES".
Font size for the link "Find out much more on the Extensions Area Wiki"
could be a little smaller.

My draft proposal can be viewed / downloaded at the following link:

https://drive.google.com/file/d/1gqmzuv-nlz8ItylBFsuYveItfhc3boUV/view?usp=sharing


Best regards,
Czesław




+1
That looks good.

Best regards,
Carl

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



Re: devtools

2021-08-12 Thread Carl Marcum

Hi Jim,


For the directories:
bootstrap-connector
guno-extension
lazybones-templates

I have copied to my  github account projects and have been working on 
them there.


I haven't done anything with netbeansintegration yet but I could.

These all work best as standalone projects in Git due to the way they 
each build an artifact

and it helped with issue tracking and releasing (personal releases that is).

I'm okay if you want to copy the whole tree over so they have a home in git.

I can go back and get them updated either way.

Best regards,
Carl


On 8/12/21 12:00 PM, Jim Jagielski wrote:

Any other opinions or comments?


On Aug 6, 2021, at 12:52 PM, Jim Jagielski  wrote:

To me, it being within OpenOffice.git makes the most sense... but I'm fine 
either way ;)


On Aug 6, 2021, at 12:49 PM, Dave Fisher  wrote:

Within /Apache/OpenOffice.git repository? Or a new 
/Apache/OpenOffice-devtools.git?

+1, especially if history is preserved.

Of course there would be wiki and webpages to update.

Sent from my iPhone


On Aug 6, 2021, at 9:31 AM, Jim Jagielski  wrote:

Our devtools repo is till under svn; should we switch it to git. It would be 
nice, I think, to use on version control implementation for all our code 
related repos.
-
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: LAZY CONSENSUS: change IRC links from Freenode to Libera.Chat

2021-08-05 Thread Carl Marcum

Hi Arrigo,

On 8/5/21 4:44 PM, Dave Fisher wrote:



On Aug 5, 2021, at 1:11 PM, Arrigo Marchiori  wrote:

Hello All,

following Carl's very good advice, here is my proposal:

  I will merge https://github.com/apache/openoffice-org/pull/57
  consisting of changing IRC links from Freenode into Libera Chat, if
  no one objects within August 10th.

Nicely done!


I don’t see any reason to wait. We aren’t going back to Freenode …

Make it so!


I also agree.

Best regards,
Carl


Regards,
Dave


Thank you and best regards,
--
Arrigo

-
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: IRC links on our web site

2021-08-04 Thread Carl Marcum

Hi Arrigo,

On 8/3/21 3:51 PM, Arrigo Marchiori wrote:

Dear All,

tonight I tried to login on the Freenode network and I was rejected.
I was told I must (re)register or else I could not connect.

In my very humble opinion, the time has come to get rid of any links
to the Freenode network, and rather invite visitors to our channel on
Libera.Chat. Keeping links to Freenode at this point may (still IMHO)
just backfire, as casual users may encounter problems just to connect
to the server, as it happened to me today.

I just pushed a new branch of our "openoffice-org" repository and
issued a pull request on GitHub [1]. Comments and reviews are welcome as
usual.

I will also work on the wiki, in my free time.

If anyone would like discuss the topic of leaving Freenode, please let
us talk about it. I saw some people on our Freenode channel, last time
I was allowed, who do not seem to appear on Libera.Chat. I must
confess this makes me a bit puzzled :-)

Best regards.

References:
  1: https://github.com/apache/openoffice-org/pull/57


Although I never used freenode and have only logged into Libera a couple 
time after all the news about freenode began.
I'll let those who participate in that method speak but I think most 
have moved.
This may be a good topic for a lazy consensus and if nobody objects just 
do it.


But in my opinion it's okay to change the links.

Best regards,
Carl


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



Re: [OS/2 and macOS] saving ODS with chart

2021-07-27 Thread Carl Marcum

Hi Arrigo,

On 7/27/21 4:21 PM, Arrigo Marchiori wrote:

Hello All,

resurrecting an old thread.

On Thu, May 27, 2021 at 02:19:44PM -, Yuri Dario wrote:


Hi,


i can build AOO 4.2.x without problems with gcc 6.3 which is in Debian 9
I had problems to build it at Debian 10 with gcc 8.3.

here I have a 4.2 build done under Manjaro with gcc 9.2: saving a diagram
in ods format works fine, so it doesn't seems to be a compiler issue;

How is XML writing done with ODS files?

It's... complicated ;-)

I tried to dig deeper into this problem, as I could reproduce it with
the "catalina" branch on our Mac Mini.


Executive Summary (TL;DR ;-)

A boolean setting is not recognized as a boolean. An exception is
thrown when accessing it. The exception is swallowed and the XML
files' contents are not written.


Details
===
Method XMLFilter::impl_Export() in file
main/chart2/source/model/filter/XMLFilter.cxx:599 [1] has the
responsibility to output the XML files that describe the chart. It
sets some common options (beans::XPropertySet xInfoSet), and appends
them to uno::Sequence aFilterProperties. This sequence, together with
other pieces of information, is passed to the three invocations of
method XMLFilter::impl_ExportStream(), that starts at line 754.
Each invocation should give the contents of one XML file.
But in fact they do nothing.

Each invocation of method XMLFilter::impl_ExportStream() gets up to
line:

810:  xExporter->setSourceDocument( m_xSourceDoc );

This method raises an exception, that is caught below at line 820. The
return code "nWarning" is never set to anything but zero, therefore
the method returns (line 824) having failed its task, but reporting
success.

The question is: why does the above method setSourceDocument() throw
an exception? Let's look into it. I am not sure it is called directly
due to inheritance and virtual methods, but in the end it is [2]
SvXMLExport::setSourceDocument() in file
xmloff/source/core/xmlexp.cxx:676

The exception is thrown at a seemingly harmless line:

703:  if (::cppu::any2bool(aAny))

because for some reason, that "aAny" value, returned by method
beans::XPropertySetInfo::getPropertyValue(), is not a bool, and
function any2bool() throws because it cannot decode it.

But that property _was_ set as a bool by method
XMLFilter::impl_Export(), in file
main/chart2/source/model/filter/XMLFilter.cxx, at the beginning of
this explanation:

691:  xInfoSet->setPropertyValue( sUsePrettyPrinting, uno::makeAny( 
bUsePrettyPrinting ) );

References:

  1: 
https://github.com/apache/openoffice/blob/f1593045b154fade3a67d5f1771054eccc807e3f/main/chart2/source/model/filter/XMLFilter.cxx#L599

  2: 
https://github.com/apache/openoffice/blob/f1593045b154fade3a67d5f1771054eccc807e3f/main/xmloff/source/core/xmlexp.cxx#L676


Questions and comments
==
Why does ::cppu::any2bool(aAny) not recognize a value constructed as
uno::makeAny( bUsePrettyPrinting ) ?

Or is the beans::XPropertySet the culprit?

Both CXX files pointed above have not been touched for at least 8
years. Why are they failing now? And why are they failing on a
seemingly trivial issue like a boolean property?

Maybe AOO42X introduced some changes in the overall management of
properties, "Any" objects and the like, that could have more or less
inadvertently solved this issue? Has anyone reproduced the problem
with AOO42X or trunk?

I would tend to blame the overall system because of the loads of
warnings that are emitted by clang 12 when it compiles AOO41X.

I don't know if it's worth the effort to further look into this, or
instead, just leave AOO41X working with older compilers and move
forward with AOO42X.

Comments, questions, criticism are welcome!

Best regards,


Would it be worth a try to check that the value type of the Any is a 
bool before accessing it like code further down at line 2114:


if (xPropertySetInfo->hasPropertyByName(sRepeat))
{
    uno::Any aAny = mxExportInfo->getPropertyValue(sRepeat);
    if (aAny.getValueType() == getBooleanCppuType())
    mpProgressBarHelper->SetRepeat(::cppu::any2bool(aAny));
    else {
    DBG_ERRORFILE("why is it no boolean?");
    }
}

Best regards,
Carl



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



Re: Working on Refresh of openoffice.apache.org

2021-06-30 Thread Carl Marcum

Hi Dave,

I think it looks great!

I've tested mobile with Firefox's developer tools and my iPhone 11 with 
Firefox and that looks great too.


Thanks for your work on this!

Best regards,
Carl

On 6/30/21 5:13 PM, Dave Fisher wrote:

Hi -

I like where everything is now. When I run google’s Lightroom tool in a Chrome 
Incognito window I get scores of 94, 97, 100, and 100.


On Jun 30, 2021, at 1:40 PM, Peter Kovacs  wrote:


On 30.06.21 20:17, Dave Fisher wrote:

On Jun 30, 2021, at 11:12 AM, Peter Kovacs  wrote:


On 30.06.21 19:25, Dave Fisher wrote:

I like the look at https://openoffice-refresh.staged.apache.org/. Please review.

+1, maybe can we have some icons in front of a menu point? like the ASF feather 
in front of the ASF?

The feather in front of “The ASF” is possible.


And maybe an indication which menu point we currently see. Maybe an arrow? (if you visit the 
link and you click on General you would see a -> in front of the menu point 
"About".)

I’m counting on bootstrap for the nav menus and I don’t think that is at all 
easy. It would likely require keeping information about what menu a page is 
part of in the page along with making sure that the page is on the menu.

I thought of something like this pseudocode:

if (window.location.href = this.dropdown-item.href) then this.css = "selected" else 
this.css = "unselected"?

I get your idea and it could be a way to do it and there is a way to make 
bootstrap menu items inactive.

There may be some issues with the comparison as the window.location.href is 
fully qualified while we do not want to use fully qualified urls for the 
dropdown-item hrefs (makes testing the site painful.)


Hmm, bummer seems not that easy.

So maybe something like:

const boxes = 
documentui.dropdown-menu.show.querySelectorAll('#dropdown-item');

boxes.forEach(box => {
if (window.location.href = box.dropdown-item.href) then box.css = "selected" else box.css 
= "unselected"?

}

Well something along those lines. I really suck at JS, i just try to write 
something so you have a better Idea what I thought of. Could well (likely) be 
this is rubbish.

So for the pages I tried this approach seem to be pretty neat. Pages that are 
not listed on the menue, maybe it is the qwuestion where they belong, anyhow.

Actually, I would want to learn how to customize Bootstrap 5 first, but I’m not 
going to do that right now.


There were numerous tweaks needed. The current site did not catch the rename of 
volunteer@ to recruitment@.

Unless there are objections I plan to squash & merge after I get the mobile 
view better.

I tried earlier today on my phone and it did look promising already. The 
Desktop does also look great.

Do you have an android phone, or iPhone?

I tried from an Android phone. Sony Xperia XA2 and now Samsung S8 to be exact. 
I use a Firefox browser.

Now I see a hamburger menu, nice. However the feather makes the menu look 
unaligned. it is great on the desktop.

I am not a gui developer so I am not sure what is state of the art on hamburger 
menus is, but i would intend the other menus, with the goal that the text 
starts always at same point.

IMO the feather is good in the hamburger menu. All of the ASF menu items leave 
the site.

I’m done with UI work for now. It is time to update content. See 
https://github.com/apache/openoffice-project/blob/preview/refresh/PAGES.md

All The Best,
Dave


I really like the fact that it incorporates the UI approach we are using.

Thanks!
Dave


--
This is the Way! http://www.apache.org/theapacheway/index.html

-
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 is the Way! http://www.apache.org/theapacheway/index.html


-
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: Time for a 4.2.0-dev3?

2021-06-27 Thread Carl Marcum

Hi Matthias,

On 6/27/21 12:17 PM, Matthias Seidel wrote:

Hi Carl,

Am 27.06.21 um 13:16 schrieb Carl Marcum:

Hi Matthias,

On 6/26/21 10:55 AM, Matthias Seidel wrote:

3 month later, I assume there is no interest in releasing a Dev3?

That's okay with me.

I hope you are OK with doing a dev3? ;-)


Sorry, yes I'm okay with a dev3 :)

Best regards,
Carl



Regards,

    Matthias


Best regards,
Carl


Regards,

     Matthias

Am 23.03.21 um 16:54 schrieb Matthias Seidel:

Hi Jim,

I would suggest we build the same language set as in Dev 2.

That means 41+5 languages:

http://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.2.0-Dev2/wntmsci/Pack-dev.lst


@Mechtilde: What about new Pootle templates? We had a lot of string
changes...

Regards,

     Matthias

Am 23.03.21 um 16:03 schrieb Jim Jagielski:

In an effort to save some time and resources, can we confirm on
whether or not we are building the full language set?


On Mar 20, 2021, at 2:04 PM, Matthias Seidel
 wrote:

Hi all,

I have created the directory structure for Dev3:

https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev3/

Regards,

     Matthias

Am 17.03.21 um 18:00 schrieb Matthias Seidel:

Hi Arrigo,

Am 16.03.21 um 21:53 schrieb Arrigo Marchiori:

Hello,

On Tue, Mar 16, 2021 at 04:26:53PM +0100, Matthias Seidel wrote:


Hi all,

The subject says it all... ;-)

No exact time frame, but we could include a full set of updated
translations from Pootle here.

I would also like to have some pull requests merged, if possible!

Definitely!

The next step would be to solve the Release Blocker for 4.2.0 and
release it! ;-)

Regards,

     Matthias


And I am still tackling bug #126869. Man, UNO is... big!

Regards,

-
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: Time for a 4.2.0-dev3?

2021-06-27 Thread Carl Marcum

Hi Matthias,

On 6/26/21 10:55 AM, Matthias Seidel wrote:

3 month later, I assume there is no interest in releasing a Dev3?


That's okay with me.

Best regards,
Carl



Regards,

    Matthias

Am 23.03.21 um 16:54 schrieb Matthias Seidel:

Hi Jim,

I would suggest we build the same language set as in Dev 2.

That means 41+5 languages:

http://svn.apache.org/repos/asf/openoffice/devtools/build-scripts/4.2.0-Dev2/wntmsci/Pack-dev.lst

@Mechtilde: What about new Pootle templates? We had a lot of string
changes...

Regards,

    Matthias

Am 23.03.21 um 16:03 schrieb Jim Jagielski:

In an effort to save some time and resources, can we confirm on whether or not 
we are building the full language set?


On Mar 20, 2021, at 2:04 PM, Matthias Seidel  wrote:

Hi all,

I have created the directory structure for Dev3:

https://dist.apache.org/repos/dist/dev/openoffice/4.2.0-Dev3/

Regards,

Matthias

Am 17.03.21 um 18:00 schrieb Matthias Seidel:

Hi Arrigo,

Am 16.03.21 um 21:53 schrieb Arrigo Marchiori:

Hello,

On Tue, Mar 16, 2021 at 04:26:53PM +0100, Matthias Seidel wrote:


Hi all,

The subject says it all... ;-)

No exact time frame, but we could include a full set of updated
translations from Pootle here.

I would also like to have some pull requests merged, if possible!

Definitely!

The next step would be to solve the Release Blocker for 4.2.0 and
release it! ;-)

Regards,

Matthias


And I am still tackling bug #126869. Man, UNO is... big!

Regards,

-
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: minor patch enabling the piecewise inclusion of category-b components

2021-06-25 Thread Carl Marcum

Hi Yury,


On 6/25/21 3:00 PM, Matthias Seidel wrote:

Hi Yury,

Am 25.06.21 um 08:18 schrieb Yury Tarasievich:

Could you guys put these changes in, please, instead of me messing
with git?
I'm quite incompetent in git process,
and the patch content is straightforward. Anybody could produce it.

If anybody could produce it, why can't you? ;-)

If you don't want to use Git, can you provide a diff file?

Matthias




I've applied patch from your Gist link.

Can you provide some examples of your usage to the PR-134 [1] and I'll 
test it with a build.


[1] https://github.com/apache/openoffice/pull/134

Thanks,
Carl

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



Re: Hyperlink Warning Message

2021-06-23 Thread Carl Marcum

Hi Arrigo,

On 6/23/21 1:19 PM, Arrigo Marchiori wrote:

Dear All,

On Tue, Jun 22, 2021 at 07:41:23PM +0200, Marcus wrote:


Am 22.06.21 um 19:26 schrieb Matthias Seidel:

What about adding .wpl .m3u etc. to the list of secure file extensions?

I would like to build a new version soon to let our users test...

+1

Marcus

I just uploaded a Linux build:
https://home.apache.org/~ardovm/openoffice/bug128453/2021-06-23/
It is in the "installed" format, i.e. it _should_ be executable right
after decompression.

Sources are in the bug128453 branch (again):
https://github.com/apache/openoffice/tree/bug128453

I also added the "ogg", "flac" and "m3u" extensions.

For your kind testing.

Best regards,



Thanks for providing the "installed" type build.
That makes it very easy to test.

I tested the 3 new extensions you added with file:/// type links and all 
3 were passed on to the OS.
I think this now covers all the requests collected in bz from what I can 
tell.


Thanks again for your work on this.

Best regards,
Carl

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



Re: rework the automated tests to not require an office build first

2021-06-12 Thread Carl Marcum

Hi Keith,

On 6/12/21 4:28 PM, Keith N. McKenna wrote:

On 2021-06-12 09:13, Carl Marcum wrote:

Hi All,

cc'd qa@

I think it would be good to rework the test framework to not require
having just built the office.

Currently, to compile and run the tests, there are dependencies on
environment settings created and files built into main/solver/.
Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar
files.
All these file dependencies are also available in either the office that
would be under test or the SDK.

I think it would be a benefit for QA and open the use and development of
automated tests to testers and developers that don't also have a AOO
build environment.
For instance I can run the test suite against Linux where I have a build
env but not on Windows where I don't.

The one big thing about this would be it would require a tester to have
the SDK installed in the office under test.
I think this is a much lower bar than building the office to get them.

Does anyone have an opinion one way or the other?

Thanks,
Carl

Carl;

I believe that would be a wonderful addition to our QA tools. Currently
I am using windows 10, but do not have the disk capacity for a build
environment. If you can get this working it would enable me to
contribute much more to  our QA efforts.

I am more than willing to run any tests needed for Windows 10 Professional.


Thanks, I'll let you know when I have something.

Best regards,
Carl


Regards,
Keith





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



Re: rework the automated tests to not require an office build first

2021-06-12 Thread Carl Marcum

Hi Pedro,

On 6/12/21 11:41 AM, Pedro Lino wrote:

Hi Carl, all


On 06/12/2021 2:13 PM Carl Marcum  wrote:
The one big thing about this would be it would require a tester to have
the SDK installed in the office under test.
I think this is a much lower bar than building the office to get them.

Does anyone have an opinion one way or the other?

This sounds excellent. It would probably allow more Windows users (the most 
used PC OS and accordingly where there are more AOO users) to test it.

I volunteer to run any needed tests on Windows 7 x64.


If I'm able to follow through with it I'll let you know.

Thanks,
Carl



Thanks!

Cheers,
Pedro

-
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: Hyperlink Warning Message

2021-06-12 Thread Carl Marcum

Hi Pedro,

On 6/12/21 12:22 PM, Pedro Lino wrote:

Hi Carl, all


On 06/12/2021 2:47 AM Carl Marcum  wrote:
Can anyone on windows confirm with the file [1]?
[1] http://home.apache.org/~cmarcum/hyperlink-tests/hyperlink-test-doc.odt

I confirm Francis' findings on AOO 4.1.11 running on Windows 7 x64.
There is no problem reopening the document.


Thanks for testing!


I can also confirm that all links in the document behave as expected under AOO 
4.1.11, with warnings only on untrusted links.


Yes very good news.

There is now a PR #132 if you're able to test it.

Best regards,
Carl


All good news ;)

Cheers,
Pedro

-
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: rework the automated tests to not require an office build first

2021-06-12 Thread Carl Marcum

Hi Arrigo,

On 6/12/21 9:25 AM, Arrigo Marchiori wrote:

Hello Carl, All,

On Sat, Jun 12, 2021 at 09:13:13AM -0400, Carl Marcum wrote:


Hi All,

cc'd qa@

I think it would be good to rework the test framework to not require having
just built the office.

It sounds like a very good idea to me.


Currently, to compile and run the tests, there are dependencies on
environment settings created and files built into main/solver/.
Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar files.
All these file dependencies are also available in either the office that
would be under test or the SDK.

I think it would be a benefit for QA and open the use and development of
automated tests to testers and developers that don't also have a AOO build
environment.
For instance I can run the test suite against Linux where I have a build env
but not on Windows where I don't.

The one big thing about this would be it would require a tester to have the
SDK installed in the office under test.
I think this is a much lower bar than building the office to get them.

Does anyone have an opinion one way or the other?

IMHO I am totally for it.

Unfortunately I do not have resources (and knowledge) to help you at
the moment, but if this is not an urgent matter, we can plan it.


Thanks, I was planning on doing the heavy lifting :)

I've already got a lot of it working on a CentOS 8 machine that I can't 
build office on and the tests build and run.


There are more use-cases like running them against the "installed" build 
for those that want to build office and test it in place that I still 
need to work out.


Best regards,
Carl


I am looking forward to hear other peoples' opinions.

Best regards,



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



rework the automated tests to not require an office build first

2021-06-12 Thread Carl Marcum

Hi All,

cc'd qa@

I think it would be good to rework the test framework to not require 
having just built the office.


Currently, to compile and run the tests, there are dependencies on 
environment settings created and files built into main/solver/.

Mostly things like idlc, regmerge, and javamaker etc. and the UNO jar files.
All these file dependencies are also available in either the office that 
would be under test or the SDK.


I think it would be a benefit for QA and open the use and development of 
automated tests to testers and developers that don't also have a AOO 
build environment.
For instance I can run the test suite against Linux where I have a build 
env but not on Windows where I don't.


The one big thing about this would be it would require a tester to have 
the SDK installed in the office under test.

I think this is a much lower bar than building the office to get them.

Does anyone have an opinion one way or the other?

Thanks,
Carl


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



Re: Hyperlink Warning Message

2021-06-12 Thread Carl Marcum

Hi Matthias,

On 6/12/21 5:10 AM, Matthias Seidel wrote:

Hi Carl, all,

Tests look great and we should think about merging the fix into the
official AOO4111 branch.

Yes merge it in AOO41X and branch from it.

Yes I think it's ready for trunk and AOO42X also.
Maybe we wait for the other two until we have more widespread testing 
but this seems like the right fix to me.


Best regards,
Carl



Additionally we could need test builds for mac and Linux.

Regards,

    Matthias

Am 12.06.21 um 03:47 schrieb Carl Marcum:

Hi Matthias,

On 6/11/21 6:19 PM, Matthias Seidel wrote:

Hi Keith, all,

Am 10.06.21 um 15:53 schrieb Matthias Seidel:

Hi Keith,

Could you provide a test document?

Or (if you use Windows) make a test with this build:

https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/Full%20Installation/Apache_OpenOffice_4.2.0_Win_x86_install_en-US_56e2535bb8.exe


I posted the wrong link for the build, please try this one:

https://home.apache.org/~mseidel/AOO-builds/AOO-4111-Test/Full%20Installation/Apache_OpenOffice_4.1.11_Win_x86_install_en-US_6652b2eb2e.exe


Regards,

     Matthias

This one works great on my test document!
No warning on the .uno:Reload button or the odf file or inter-document
links.

I did discover a bug unrelated to this.

When I open the document I created on Linux with the hyperlinks and
uno button using the file open dialog it opens correctly using Windows
10.
When I open it again using dropdown beside the Open button in the
Start Center or File > Recent Documents I get an ASCII Filter Options
dialog and then a General Error. General input/output error and the
file doesn't open.

Also happens with a production 4.1.9 that was on this system I'm
testing on.

Can anyone on windows confirm with the file [1]?
[1]
http://home.apache.org/~cmarcum/hyperlink-tests/hyperlink-test-doc.odt


Thanks,
Carl

Regards,

     Matthias

Am 04.05.21 um 16:05 schrieb k...@kshelton.plus.com:

For some years I've had a Reload button in my Calc document to
avoid having to use the File menu. Just updated to 4.1.10 and now I
get a message when pressing Reload button:

This hyperlink is going to open “.uno:Reload”. Do you want to proceed?

Is there a way of switching off this message please?

Thanks.

Regards
Keith Shelton




-
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: Hyperlink Warning Message

2021-06-12 Thread Carl Marcum

Hi Francis,

On 6/11/21 11:31 PM, F Campos Costero wrote:

I downloaded the test document and tried the links using 4.1.10. I saw the
expected warnings. Closing the file and reopening via the drop down list on
the Open button worked with no problem. I then installed the 4.1.11 linked
above (Apache_OpenOffice_4.1.11_Win_x86_install_en-US_6652b2eb2e.exe
<https://home.apache.org/~mseidel/AOO-builds/AOO-4111-Test/Full%20Installation/Apache_OpenOffice_4.1.11_Win_x86_install_en-US_6652b2eb2e.exe>)
and repeated the test, again with no problems when I reopened the
document.  I did not try all of the links in the document but I did try at
least one of each kind.
Is that the kind of test you needed?


Yes that's just what I needed.
That tells me it may just be machine specific and not easy to reproduce.

Thanks for your test!

Best regards,
Carl


I am on Windows 10 and ran the
2021-06 update yesterday.

Francis

On Fri, Jun 11, 2021 at 7:47 PM Carl Marcum  wrote:


Hi Matthias,

On 6/11/21 6:19 PM, Matthias Seidel wrote:

Hi Keith, all,

Am 10.06.21 um 15:53 schrieb Matthias Seidel:

Hi Keith,

Could you provide a test document?

Or (if you use Windows) make a test with this build:



https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/Full%20Installation/Apache_OpenOffice_4.2.0_Win_x86_install_en-US_56e2535bb8.exe

I posted the wrong link for the build, please try this one:



https://home.apache.org/~mseidel/AOO-builds/AOO-4111-Test/Full%20Installation/Apache_OpenOffice_4.1.11_Win_x86_install_en-US_6652b2eb2e.exe

Regards,

 Matthias

This one works great on my test document!
No warning on the .uno:Reload button or the odf file or inter-document
links.

I did discover a bug unrelated to this.

When I open the document I created on Linux with the hyperlinks and uno
button using the file open dialog it opens correctly using Windows 10.
When I open it again using dropdown beside the Open button in the Start
Center or File > Recent Documents I get an ASCII Filter Options dialog
and then a General Error. General input/output error and the file
doesn't open.

Also happens with a production 4.1.9 that was on this system I'm testing
on.

Can anyone on windows confirm with the file [1]?
[1] http://home.apache.org/~cmarcum/hyperlink-tests/hyperlink-test-doc.odt


Thanks,
Carl

Regards,

 Matthias

Am 04.05.21 um 16:05 schrieb k...@kshelton.plus.com:

For some years I've had a Reload button in my Calc document to avoid

having to use the File menu. Just updated to 4.1.10 and now I get a message
when pressing Reload button:

This hyperlink is going to open “.uno:Reload”. Do you want to proceed?

Is there a way of switching off this message please?

Thanks.

Regards
Keith Shelton




-
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: Hyperlink Warning Message

2021-06-11 Thread Carl Marcum

Hi Matthias,

On 6/11/21 6:19 PM, Matthias Seidel wrote:

Hi Keith, all,

Am 10.06.21 um 15:53 schrieb Matthias Seidel:

Hi Keith,

Could you provide a test document?

Or (if you use Windows) make a test with this build:

https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/Full%20Installation/Apache_OpenOffice_4.2.0_Win_x86_install_en-US_56e2535bb8.exe

I posted the wrong link for the build, please try this one:

https://home.apache.org/~mseidel/AOO-builds/AOO-4111-Test/Full%20Installation/Apache_OpenOffice_4.1.11_Win_x86_install_en-US_6652b2eb2e.exe

Regards,

    Matthias


This one works great on my test document!
No warning on the .uno:Reload button or the odf file or inter-document 
links.


I did discover a bug unrelated to this.

When I open the document I created on Linux with the hyperlinks and uno 
button using the file open dialog it opens correctly using Windows 10.
When I open it again using dropdown beside the Open button in the Start 
Center or File > Recent Documents I get an ASCII Filter Options dialog 
and then a General Error. General input/output error and the file 
doesn't open.


Also happens with a production 4.1.9 that was on this system I'm testing on.

Can anyone on windows confirm with the file [1]?
[1] http://home.apache.org/~cmarcum/hyperlink-tests/hyperlink-test-doc.odt


Thanks,
Carl



Regards,

    Matthias

Am 04.05.21 um 16:05 schrieb k...@kshelton.plus.com:

For some years I've had a Reload button in my Calc document to avoid having to 
use the File menu. Just updated to 4.1.10 and now I get a message when pressing 
Reload button:

This hyperlink is going to open “.uno:Reload”. Do you want to proceed?

Is there a way of switching off this message please?

Thanks.

Regards
Keith Shelton





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



Re: Hyperlink Warning Message

2021-06-11 Thread Carl Marcum

Hi Matthias,

On 6/11/21 5:05 PM, Matthias Seidel wrote:

Hi Carl,

Am 11.06.21 um 23:01 schrieb Carl Marcum:

Hi Matthias,

On 6/10/21 9:53 AM, Matthias Seidel wrote:

Hi Keith,

Could you provide a test document?

Or (if you use Windows) make a test with this build:

https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/Full%20Installation/Apache_OpenOffice_4.2.0_Win_x86_install_en-US_56e2535bb8.exe


Was this 4.2 build supposed to have the .uno: hyperlink fixed so the
warning doesn't display?

No, this one is based on Arrigo's branch:

https://home.apache.org/~mseidel/AOO-builds/AOO-4111-Test/Full%20Installation/Apache_OpenOffice_4.1.11_Win_x86_install_en-US_6652b2eb2e.exe

Regards,

    Matthias
Sorry, since you asked Keith Shelton to test it and that was his problem 
I thought you may have patched it.


So I tried it :)

Thanks for building!
Carl

My test still has the warning.

Thanks,
Carl


Regards,

     Matthias

Am 04.05.21 um 16:05 schrieb k...@kshelton.plus.com:

For some years I've had a Reload button in my Calc document to avoid
having to use the File menu. Just updated to 4.1.10 and now I get a
message when pressing Reload button:

This hyperlink is going to open “.uno:Reload”. Do you want to proceed?

Is there a way of switching off this message please?

Thanks.

Regards
Keith Shelton




-
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: Hyperlink Warning Message

2021-06-11 Thread Carl Marcum

Hi Matthias,

On 6/10/21 9:53 AM, Matthias Seidel wrote:

Hi Keith,

Could you provide a test document?

Or (if you use Windows) make a test with this build:

https://home.apache.org/~mseidel/AOO-builds/AOO-420-Test/Full%20Installation/Apache_OpenOffice_4.2.0_Win_x86_install_en-US_56e2535bb8.exe


Was this 4.2 build supposed to have the .uno: hyperlink fixed so the 
warning doesn't display?


My test still has the warning.

Thanks,
Carl



Regards,

    Matthias

Am 04.05.21 um 16:05 schrieb k...@kshelton.plus.com:

For some years I've had a Reload button in my Calc document to avoid having to 
use the File menu. Just updated to 4.1.10 and now I get a message when pressing 
Reload button:

This hyperlink is going to open “.uno:Reload”. Do you want to proceed?

Is there a way of switching off this message please?

Thanks.

Regards
Keith Shelton





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



Re: sharing "installed" builds for Linux testing

2021-06-11 Thread Carl Marcum

Hi Yury!

On 6/9/21 12:29 AM, Yury Tarasievich wrote:


On 2021/06/08 15:50:56, Marcus  wrote: > Am 08.06.21 um 
16:08 schrieb Carl Marcum:> > > Would sharing the "installed" type 
builds work for Linux testing of > > > small changes as long as the 
architecture was the same?


I'm using OpenOffice and/or LibreOffice in this manner for years. This 
works.


If need be I create shell script with alternate config directory 
specification:


-env:UserInstallation=file:///home/you/.openoffice/4

Is this for an alternate user profile?

Is this passed at startup?

Thanks,
Carl


-Yury

-
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: sharing "installed" builds for Linux testing

2021-06-11 Thread Carl Marcum

Hi Keith,

On 6/11/21 11:09 AM, Keith N. McKenna wrote:

On 2021-06-08 10:08, Carl Marcum wrote:

Hi All,

Would sharing the "installed" type builds work for Linux testing of
small changes as long as the architecture was the same?
That way Linux testers wouldn't need to integrate with the system
similar to Windows users having the option of an administrative install.

I've tested sharing a build from CentOS 7  to Ubuntu 18 and CentOS 8
without any noticeable issues.
It seems the user profile is kept in a sub-directory so I like that also.

I didn't know if this had been tried before or if there is a downside.

After a build I copy the office out to a new directory and then copy the
SDK into it.

$ mkdir /AOO450
$ cp -r
/openoffice/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice/installed/install/en-US/openoffice4
/AOO450/
$ cp -r
/openoffice/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice_SDK/installed/install/en-US/openoffice4/sdk
/AOO450/openoffice4/

Then the openoffice4 dir gets archived from there.
Users could unpack and test then delete.

Thanks,
Carl

Carl, ET AL;

There is this mwiki page for doing just what you are asking:
https://wiki.openoffice.org/wiki/Run_OOo_versions_parallel#Installing_3..2A_versions_.28three_layer_OpenOffice.org.29.
It is marked as outdated and may need some updating. As I do not use
Linux I have never tried it myself.

Regards
Keith


Thanks for the link. I haven't ran across this before.

Actually when you build with config option --with-package-format 
"installed" instead of "rpm deb" you get the directory layout and 
embedded user profile without all that work.

That's what I suggest building and sharing for quick testing.

Thanks again.
Carl

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



Re: Hyperlink Warning Message

2021-06-10 Thread Carl Marcum

Hi Marcus,

On 6/10/21 9:29 AM, Marcus wrote:

Am 08.06.21 um 11:16 schrieb Matthias Seidel:

Find the Windows build here:

https://home.apache.org/~mseidel/AOO-builds/AOO-4111-Test/Full%20Installation/Apache_OpenOffice_4.1.11_Win_x86_install_en-US_6652b2eb2e.exe 



here my results:

http://www.openoffice.org/
http://www.openoffice.org/test.exe
http://www.openoffice.org/test.ods
https://www.openoffice.org/
https://www.openoffice.org/test.exe
https://www.openoffice.org/test.ods

--> Any HTTP or HTTPS links are opened without warning.

smb://www.openoffice.org/
smb://www.openoffice.org/test.exe
smb://www.openoffice.org/test.ods
file://www.openoffice.org/
file://www.openoffice.org/test.exe
file://www.openoffice.org/test.ods

--> Any SMB or FILE links get the warning dialog before opening.

How can I test with UNO links like ".uno:reload"?


The test document I created has a button with a .uno:Reload action.

http://home.apache.org/~cmarcum/hyperlink-tests/

Or make a push button using form controls.
Set Action to Open document/web page
Set URL to .uno:Reload

Best regards,
Carl



Thanks

Marcus




Am 07.06.21 um 18:09 schrieb Marcus:

Am 07.06.21 um 02:12 schrieb Carl Marcum:

Hi Arrigo,

On 6/6/21 3:56 PM, Arrigo Marchiori wrote:

Hello Carl, All,

On Sun, Jun 06, 2021 at 11:50:12AM -0400, Carl Marcum wrote:


Hi Arrigo and All,

On 6/5/21 5:53 PM, Arrigo Marchiori wrote:

Hello Carl, All,

On Sat, Jun 05, 2021 at 03:47:12PM -0400, Carl Marcum wrote:


Hi Arrigo,

On 6/5/21 9:50 AM, Arrigo Marchiori wrote:

Dear Matthias, Czesław, All,

On Sat, Jun 05, 2021 at 12:39:16PM +0200, Matthias Seidel wrote:


Hi Czesław,

Am 05.06.21 um 12:35 schrieb Czesław Wolański:

Hi Matthias, all

A preliminary check in Calc (Windows 7, 64-bit)

(1) in-document links beginning with #
test: button with link to other sheet
result: OK (no security warning)

(2) .uno:XXX links
result: security warning

(3) Links to local files
test: the "Hyperlink" dialog, button "WWW Browser"
result: OK (no security warning)

That's what I expected, since the patches are for file://

.uno: hasn't been addressed yet

@Arrigo: correct me if I am wrong ;-)

You should have just become wrong ;-)

I found out that there are many checks on the URL protocol. I
suggest
that the warning was not checked at the right moment, but too 
soon.


Because we had a report of unexpected _execution_ of malicious
links,
I suggest we leave the safety check on hyperlinks _just before
calling
the OS to execute them_.

The result is that HTTP, HTTPS, but also "uno:" and all other
protocols already understood by AOO are not checked, and no
warnings
will appear. We could argue that their safety must be assured by
the
code handling them, as we accepted to delegate the browser for
Internet links.

The latest commit, just pushed to branch bug128453, moves the 
check

for "safe extensions" (or directory) from the beginning of
hyperlinks'
processing, to just before the execution of the link target by
the OS.
The protocol is not checked any more, because supported protocols
are already filtered out and processed at that point.

This should make all links to non-files work again, and still 
warn

users when they are going to open JAR's, EXE's and other unknown
types.

What do you think about this?

I like your thinking on this.
I'll build this branch on Linux and test using some of the test
documents
and ones I've made to make sure I understand the different cases.
Then I'll report back.

You can find my 64 bit Linux builds here:
https://home.apache.org/~ardovm/openoffice/bug128453/

I tried the "beta" option of the build script... I hope it works.

Thank you for your cooperation!

Best regards,

I've built the bug128453 branch [1] on Linux CentOS 7 and ran the
test suite
that included the hyperlink tests for the dialogs [2].

I put together some test documents here [3].

Very nice, thank you!

[...]

So far everything looks good and I get the warning everywhere I
expect to
with one exception.
The smb://nonexistant.url.com link does not display the warning and
I get
this output:
---
This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.

gio: smb://nonexistant.url.com/: The specified location is not 
mounted

---
Note that I build on CentOS 7 and use --enable-gio and
--disable-gnome-vfs
in configure.

Maybe there is a reason the SMB protocol is treated differently
than the
others when there is only the host section of the url?

I'm not saying this is bad but just different. We can discuss...

Sure.

The smb:// protocol is treated like file://. A proof of this is that
the link to "smb://nonexistant.url.com/evil.jar" shows a warning 
dialog

because the ".jar" extension is not considered safe.

For the same reason, f you create a link to
"smb://nonexistant.url.com/whatever.ods" it will be opened without
warnings.

The link you are discussing poin

sharing "installed" builds for Linux testing

2021-06-08 Thread Carl Marcum

Hi All,

Would sharing the "installed" type builds work for Linux testing of 
small changes as long as the architecture was the same?
That way Linux testers wouldn't need to integrate with the system 
similar to Windows users having the option of an administrative install.


I've tested sharing a build from CentOS 7  to Ubuntu 18 and CentOS 8 
without any noticeable issues.

It seems the user profile is kept in a sub-directory so I like that also.

I didn't know if this had been tried before or if there is a downside.

After a build I copy the office out to a new directory and then copy the 
SDK into it.


$ mkdir /AOO450
$ cp -r 
/openoffice/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice/installed/install/en-US/openoffice4
 /AOO450/
$ cp -r 
/openoffice/main/instsetoo_native/unxlngx6.pro/Apache_OpenOffice_SDK/installed/install/en-US/openoffice4/sdk
 /AOO450/openoffice4/

Then the openoffice4 dir gets archived from there.
Users could unpack and test then delete.

Thanks,
Carl


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



Re: Hyperlink Warning Message

2021-06-06 Thread Carl Marcum

Hi Arrigo,

On 6/6/21 3:56 PM, Arrigo Marchiori wrote:

Hello Carl, All,

On Sun, Jun 06, 2021 at 11:50:12AM -0400, Carl Marcum wrote:


Hi Arrigo and All,

On 6/5/21 5:53 PM, Arrigo Marchiori wrote:

Hello Carl, All,

On Sat, Jun 05, 2021 at 03:47:12PM -0400, Carl Marcum wrote:


Hi Arrigo,

On 6/5/21 9:50 AM, Arrigo Marchiori wrote:

Dear Matthias, Czesław, All,

On Sat, Jun 05, 2021 at 12:39:16PM +0200, Matthias Seidel wrote:


Hi Czesław,

Am 05.06.21 um 12:35 schrieb Czesław Wolański:

Hi Matthias, all

A preliminary check in Calc (Windows 7, 64-bit)

(1) in-document links beginning with #
test: button with link to other sheet
result: OK (no security warning)

(2) .uno:XXX links
result: security warning

(3) Links to local files
test: the "Hyperlink" dialog, button "WWW Browser"
result: OK (no security warning)

That's what I expected, since the patches are for file://

.uno: hasn't been addressed yet

@Arrigo: correct me if I am wrong ;-)

You should have just become wrong ;-)

I found out that there are many checks on the URL protocol. I suggest
that the warning was not checked at the right moment, but too soon.

Because we had a report of unexpected _execution_ of malicious links,
I suggest we leave the safety check on hyperlinks _just before calling
the OS to execute them_.

The result is that HTTP, HTTPS, but also "uno:" and all other
protocols already understood by AOO are not checked, and no warnings
will appear. We could argue that their safety must be assured by the
code handling them, as we accepted to delegate the browser for
Internet links.

The latest commit, just pushed to branch bug128453, moves the check
for "safe extensions" (or directory) from the beginning of hyperlinks'
processing, to just before the execution of the link target by the OS.
The protocol is not checked any more, because supported protocols
are already filtered out and processed at that point.

This should make all links to non-files work again, and still warn
users when they are going to open JAR's, EXE's and other unknown
types.

What do you think about this?

I like your thinking on this.
I'll build this branch on Linux and test using some of the test documents
and ones I've made to make sure I understand the different cases.
Then I'll report back.

You can find my 64 bit Linux builds here:
https://home.apache.org/~ardovm/openoffice/bug128453/

I tried the "beta" option of the build script... I hope it works.

Thank you for your cooperation!

Best regards,

I've built the bug128453 branch [1] on Linux CentOS 7 and ran the test suite
that included the hyperlink tests for the dialogs [2].

I put together some test documents here [3].

Very nice, thank you!

[...]

So far everything looks good and I get the warning everywhere I expect to
with one exception.
The smb://nonexistant.url.com link does not display the warning and I get
this output:
---
This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.

gio: smb://nonexistant.url.com/: The specified location is not mounted
---
Note that I build on CentOS 7 and use --enable-gio and --disable-gnome-vfs
in configure.

Maybe there is a reason the SMB protocol is treated differently than the
others when there is only the host section of the url?

I'm not saying this is bad but just different. We can discuss...

Sure.

The smb:// protocol is treated like file://. A proof of this is that
the link to "smb://nonexistant.url.com/evil.jar" shows a warning dialog
because the ".jar" extension is not considered safe.

For the same reason, f you create a link to
"smb://nonexistant.url.com/whatever.ods" it will be opened without
warnings.

The link you are discussing points to "smb://nonexistant.url.com/".
The target ends with a backslash, therefore it is considered a
directory, and thus safe.

Thanks for pointing this out. I intended it to end without the /.
For some reason AOO adds the trailing / for the smb link no matter what 
I try.
But not for the other types.  Even in the automated test since it just 
robots the UI.


I've removed the smb link in the test document and uploaded a new copy.

I'll also disable that specific test in the test suite as well due to 
this behavior.




This is the current logic. It may be worth discussing whether we want
to consider links to directories safe or not.

The warning messages you reported about gio are worth another
discussion: we may need to update the way we "talk to" the OS under
GNOME. But as long as it works on current distributions, I would
refrain from changing it.

I hope that the above makes sense.

Best regards,

So now I'll say everything works as expected.

Thanks again for your work on this!

Best regards,
Carl


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



Re: Hyperlink Warning Message

2021-06-06 Thread Carl Marcum

Hi Arrigo and All,

On 6/5/21 5:53 PM, Arrigo Marchiori wrote:

Hello Carl, All,

On Sat, Jun 05, 2021 at 03:47:12PM -0400, Carl Marcum wrote:


Hi Arrigo,

On 6/5/21 9:50 AM, Arrigo Marchiori wrote:

Dear Matthias, Czesław, All,

On Sat, Jun 05, 2021 at 12:39:16PM +0200, Matthias Seidel wrote:


Hi Czesław,

Am 05.06.21 um 12:35 schrieb Czesław Wolański:

Hi Matthias, all

A preliminary check in Calc (Windows 7, 64-bit)

(1) in-document links beginning with #
test: button with link to other sheet
result: OK (no security warning)

(2) .uno:XXX links
result: security warning

(3) Links to local files
test: the "Hyperlink" dialog, button "WWW Browser"
result: OK (no security warning)

That's what I expected, since the patches are for file://

.uno: hasn't been addressed yet

@Arrigo: correct me if I am wrong ;-)

You should have just become wrong ;-)

I found out that there are many checks on the URL protocol. I suggest
that the warning was not checked at the right moment, but too soon.

Because we had a report of unexpected _execution_ of malicious links,
I suggest we leave the safety check on hyperlinks _just before calling
the OS to execute them_.

The result is that HTTP, HTTPS, but also "uno:" and all other
protocols already understood by AOO are not checked, and no warnings
will appear. We could argue that their safety must be assured by the
code handling them, as we accepted to delegate the browser for
Internet links.

The latest commit, just pushed to branch bug128453, moves the check
for "safe extensions" (or directory) from the beginning of hyperlinks'
processing, to just before the execution of the link target by the OS.
The protocol is not checked any more, because supported protocols
are already filtered out and processed at that point.

This should make all links to non-files work again, and still warn
users when they are going to open JAR's, EXE's and other unknown
types.

What do you think about this?

I like your thinking on this.
I'll build this branch on Linux and test using some of the test documents
and ones I've made to make sure I understand the different cases.
Then I'll report back.

You can find my 64 bit Linux builds here:
https://home.apache.org/~ardovm/openoffice/bug128453/

I tried the "beta" option of the build script... I hope it works.

Thank you for your cooperation!

Best regards,


I've built the bug128453 branch [1] on Linux CentOS 7 and ran the test 
suite that included the hyperlink tests for the dialogs [2].


I put together some test documents here [3].
hyperlink-test-doc.odt has the same 9 links I have in the test suite 
that threw the warning dialog with 4.1.10. plus there is a section of 
http(s) links that should not display it.


There is a button that uses the .uno:Reload command that was throwing 
the dialog in 4.1.10 that doesn't with this test build.


I've also included a section with file:/// links. 2 for the other file 
hyperlink-test-target.odt and one inter-document link to one the 
sections in the same test doc.


So far everything looks good and I get the warning everywhere I expect 
to with one exception.
The smb://nonexistant.url.com link does not display the warning and I 
get this output:

---
This tool has been deprecated, use 'gio open' instead.
See 'gio help open' for more info.

gio: smb://nonexistant.url.com/: The specified location is not mounted
---
Note that I build on CentOS 7 and use --enable-gio and 
--disable-gnome-vfs in configure.


Maybe there is a reason the SMB protocol is treated differently than the 
others when there is only the host section of the url?


I'm not saying this is bad but just different. We can discuss...

Best regards,
Carl


[1] 
https://github.com/apache/openoffice/commit/6652b2eb2edb94addf9b9f84de155dbbbcb89b02


[2] 
https://github.com/apache/openoffice/blob/trunk/test/testgui/source/fvt/gui/sw/hyperlink/WarningDialog.java


[3] http://home.apache.org/~cmarcum/hyperlink-tests/

Best regards,
Carl


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



Re: Hyperlink Warning Message

2021-06-05 Thread Carl Marcum

Hi Arrigo,

On 6/5/21 9:50 AM, Arrigo Marchiori wrote:

Dear Matthias, Czesław, All,

On Sat, Jun 05, 2021 at 12:39:16PM +0200, Matthias Seidel wrote:


Hi Czesław,

Am 05.06.21 um 12:35 schrieb Czesław Wolański:

Hi Matthias, all

A preliminary check in Calc (Windows 7, 64-bit)

(1) in-document links beginning with #
test: button with link to other sheet
result: OK (no security warning)

(2) .uno:XXX links
result: security warning

(3) Links to local files
test: the "Hyperlink" dialog, button "WWW Browser"
result: OK (no security warning)

That's what I expected, since the patches are for file://

.uno: hasn't been addressed yet

@Arrigo: correct me if I am wrong ;-)

You should have just become wrong ;-)

I found out that there are many checks on the URL protocol. I suggest
that the warning was not checked at the right moment, but too soon.

Because we had a report of unexpected _execution_ of malicious links,
I suggest we leave the safety check on hyperlinks _just before calling
the OS to execute them_.

The result is that HTTP, HTTPS, but also "uno:" and all other
protocols already understood by AOO are not checked, and no warnings
will appear. We could argue that their safety must be assured by the
code handling them, as we accepted to delegate the browser for
Internet links.

The latest commit, just pushed to branch bug128453, moves the check
for "safe extensions" (or directory) from the beginning of hyperlinks'
processing, to just before the execution of the link target by the OS.
The protocol is not checked any more, because supported protocols
are already filtered out and processed at that point.

This should make all links to non-files work again, and still warn
users when they are going to open JAR's, EXE's and other unknown
types.

What do you think about this?

I like your thinking on this.
I'll build this branch on Linux and test using some of the test 
documents and ones I've made to make sure I understand the different cases.

Then I'll report back.

Thanks again for your work on this!

Best regards,
Carl



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



Re: JUnit update from 4.10 to 4.13.2 in test automation

2021-06-04 Thread Carl Marcum

Hi All,

adding cc. dev@

On 5/31/21 3:05 PM, Carl Marcum wrote:

Hi All,

Just an FYI I've been working on updating the JUnit library used in 
the test suites for trunk.

Our current 4.10 is ten years old.

I'm doing this in two steps.

First step was the library update to 4.12 in commit 069226d [1]. The 
only effect of this is users that have ran the automated tests and 
have a test/lib folder need to delete the junit.jar before compiling 
the tests again and you will get the 4.12 jar and also hamcrest 2.2 as 
well. A change in 4.11 was the need to separately include a hamcrest 
dependency.


Now that is integrated I've submitted PR-131 [2] to go to JUnit 4.13.2 
which is the latest in the JUnit 4 series.
This required class changes due to changes in JUnit 4.13 which is why 
I chose to split it up.


BTW, JUnit 5 is the new rewrite of this library but it has a Java 8 
dependency and a lot of changes to the API to it's not something I'm 
looking at currently. However just these updates open up many 
improvements that can be made in the tests especially the 
parameterized ones.


*** Anyone who compiles the test suite needs to delete or empty the 
/test/lib directory before compiling to get the correct 
junit.jar and the new hamcrest.jar required. ***


This will need done again after PR-131 is merged.
I'll post a note here after it's integrated.

[1] 
https://github.com/apache/openoffice/commit/069226d344055623fb554fac841132ecefce563a

[2] https://github.com/apache/openoffice/pull/131




The test automation has been updated in trunk and AOO42X to use JUnit 
4.13.2 (latest JUnit 4) and now includes Hamcrest 2.2 (latest).


Anyone who runs the automated test suites will need to remove the 
junit.jar from /test/lib and you should get the new jars 
downloaded next time you compile the tests.


Please let me know if you have any questions.

Thanks,
Carl

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



Re: ReactOS and AOO

2021-06-01 Thread Carl Marcum

Hi Matthias,

Any chance of building AOO on this?

Best regards,
Carl

On 6/1/21 9:56 AM, Matthias Seidel wrote:

Hi all,

My pull request got merged today:

https://github.com/reactos/rapps-db/pull/138

Next step will be an application icon and some other enhancements.

Regards,

    Matthias

Am 18.05.21 um 17:03 schrieb Matthias Seidel:

Hi Peter,

Am 18.05.21 um 07:33 schrieb Peter Kovacs:

On 17.05.21 15:59, Matthias Seidel wrote:

Hi all,

ReactOS [1] has made some great improvements lately and I decided to
install it in VirtualBox and test AOO.

Ohh very nice!

The App Manager only has AOO 4.1.5 listed, so I created a Pull Request
to update the database [2].

AOO still has some repaint issues but I really like the combination...

I have spoken to the Project booth  guy on FOSDEM 2017 I think.

I always wanted to stop by their booth, but didn't manage to.

I have been told if Windows Works and ReactOS has some error it is
most likely an issue on their side and it should be reported there,
since the goal is to be 100% compatible with Windows.

That's most likely, so they can take our project to see how compatible
they are.
However, if they find something on our side we can easily fix it.

Next, I will try a daily build, since there was some progress in memory
management lately.


Also they have said, we should use the Windows SDK for the same reason.

That makes sense.

Regards,

    Matthias


All the best

Peter




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



Re: Hyperlink Warning Message

2021-05-28 Thread Carl Marcum

Hi All,

On 5/28/21 4:46 PM, Peter Kovacs wrote:


On 28.05.21 22:04, Arrigo Marchiori wrote:

Hello all,

replying to an older message in this thread.

On Thu, May 13, 2021 at 07:23:16PM -0400, Carl Marcum wrote:

[...]
Hopefully we can collect the exceptions in the BZ issue noted in 
this thread

and then agree on the direction.

The few I see so far are:
1. in-document links beginning with #.
2. .uno:XXX links
3. Links to local files.

I think all 3 are candidates but that's just me.

I have bad news about number 1. Apparently, when the link is indicated
as "#anchor", it is transformed into "file://path/document.ods#anchor"
and then passed to SfxApplication::OpenDocExec_Impl()

This means that if we want to have warning-less links to the same
document, then we may have to consider the file:// protocol possibly
safe. We should then rely on extensions.

Suprisingly, the OpenDocument extensions do not seem to be included in
the standard list of safe extensions. Such list should be in
main/officecfg/registry/data/org/openoffice/Office/Security.xcu -- I
cannot recall who brought this to my attention and therefore I am
unable to credit him/her, I am sorry.

Does anyone see any possible security issues in considering the
file:// protocol safe and deciding on the target file's extension
whether to show a warning or not?


I would not go for file://. Can we go for a pattern derivated from 
file://path/document.ods#anchor ?



We had CVEs in the past working with file links, based odf definition 
and UNO. Maybe you can try the test files from those CVEs.




I think the file protocol as a hyperlink was considered safe by the 
office right up until this fix.


It seems the uno and file protocols were caught up in the fix and are 
the primary ones causing the users problems.
I don't believe either of these were the subject of the CVE that was 
fixed so I don't think we're harming that one.


I would think we could allow these at least for a test build while also 
going back and verify the previous CVE's didn't get opened up.



Just my thoughts.
Carl

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



Re: Opengrok Repositories updated

2021-05-23 Thread Carl Marcum

Hi Peter,

On 5/22/21 11:06 AM, Peter Kovacs wrote:

Hello all,


at last I managed to update the OpenGrok Repositories.

Following Versions have been removed:

# aoo418

# aoo419

following Versions have been added

# aoo4110

# aoo41x

Versions untouched:

# aoo42x

# trunk


All the best

Peter


Thanks for keeping this updated.
It's a valuable tool for me as I try to learn C++ and my way around the 
codebase.


Best regards,
Carl

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



Re: Hyperlink Warning Message

2021-05-13 Thread Carl Marcum

Hi Matthias,

On 5/13/21 6:32 PM, Matthias Seidel wrote:

Hi Carl,

Am 14.05.21 um 00:26 schrieb Carl Marcum:

Hi Matthias,

On 5/13/21 9:23 AM, Matthias Seidel wrote:

Hi Carl,

Am 13.05.21 um 13:05 schrieb Carl Marcum:

Hi All,

On 5/13/21 3:01 AM, Peter Kovacs wrote:

Does it make sense in addition to create a Wiki page with all types
of Links that we can have?

So we have some sort of Documentation.

Also maybe the ODF specification can give us hints what type there is.

On 12.05.21 22:12, Arrigo Marchiori wrote:

Hello all,

please allow me to top-post as I just need a ``public reminder''.

An Italian user reported another problem [1]: they have links that
point _to the same document_ and trigger the warning.

Even if you do not understand Italian, you can download the
attachment
and look at what the buttons do.

URLs are in the form: "#anchor". Therefore, we should remember to
whitelist all links starting with "#", whatever design choice we
make.

Would not it be nice to file a BugZilla issue to collect all the
reports and URLs, as it happened for other ``popular'' bugs?

1: https://forum.openoffice.org/it/forum/viewtopic.php?f=9=11231

Best regards,

There seem to be quite a lot.

We should probably decide what we're going to allow.
One list I found is in urlobj.cxx [1].

Not sure yet what the differences are in internal, external, and
official and if that may help decide.

I see that INET_PROT_UNO is available.
Maybe that can be allowed the same way as INET_PROT_VND_SUN_STAR_HELP?


Yes that's probably going to be one.

If you have an idea for AOO41X, can you provide a PR? I will then build
for Windows to let people test.


Hopefully we can collect the exceptions in the BZ issue noted in this 
thread and then agree on the direction.


The few I see so far are:
1. in-document links beginning with #.
2. .uno:XXX links
3. Links to local files.

I think all 3 are candidates but that's just me.

@Arrigo, were you planning on a PR for AOO41X ?

If not, I can try at least some of it but again I'm not really a C++ guy 
yet :)


Best regards,
Carl

There is also the suggestion (Dave's maybe?) that we add the 3
security levels (that are already in the code) for links to the UI
settings and let the user lock it down or open it up from where it is
now.

Yes, but that will only work for trunk/AOO42X since we need to update
the translations too.

Regards,

    Matthias


I'm not yet familiar with the UI code to know where to begin.

Best regards,
Carl


Regards,

    Matthias


[1]
http://opengrok.openoffice.org/xref/trunk/main/tools/source/fsys/urlobj.cxx?r=86e1cf34#2080


-
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: Hyperlink Warning Message

2021-05-13 Thread Carl Marcum

Hi Matthias,

On 5/13/21 9:23 AM, Matthias Seidel wrote:


Hi Carl,

Am 13.05.21 um 13:05 schrieb Carl Marcum:

Hi All,

On 5/13/21 3:01 AM, Peter Kovacs wrote:
Does it make sense in addition to create a Wiki page with all types 
of Links that we can have?


So we have some sort of Documentation.

Also maybe the ODF specification can give us hints what type there is.

On 12.05.21 22:12, Arrigo Marchiori wrote:

Hello all,

please allow me to top-post as I just need a ``public reminder''.

An Italian user reported another problem [1]: they have links that
point _to the same document_ and trigger the warning.

Even if you do not understand Italian, you can download the attachment
and look at what the buttons do.

URLs are in the form: "#anchor". Therefore, we should remember to
whitelist all links starting with "#", whatever design choice we make.

Would not it be nice to file a BugZilla issue to collect all the
reports and URLs, as it happened for other ``popular'' bugs?

1: https://forum.openoffice.org/it/forum/viewtopic.php?f=9=11231

Best regards,

There seem to be quite a lot.

We should probably decide what we're going to allow.
One list I found is in urlobj.cxx [1].

Not sure yet what the differences are in internal, external, and 
official and if that may help decide.


I see that INET_PROT_UNO is available.
Maybe that can be allowed the same way as INET_PROT_VND_SUN_STAR_HELP?


Yes that's probably going to be one.

There is also the suggestion (Dave's maybe?) that we add the 3 security 
levels (that are already in the code) for links to the UI settings and 
let the user lock it down or open it up from where it is now.


I'm not yet familiar with the UI code to know where to begin.

Best regards,
Carl


Regards,

   Matthias



[1] 
http://opengrok.openoffice.org/xref/trunk/main/tools/source/fsys/urlobj.cxx?r=86e1cf34#2080



-
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: Hyperlink Warning Message

2021-05-13 Thread Carl Marcum

Hi All,

On 5/13/21 3:01 AM, Peter Kovacs wrote:
Does it make sense in addition to create a Wiki page with all types of 
Links that we can have?


So we have some sort of Documentation.

Also maybe the ODF specification can give us hints what type there is.

On 12.05.21 22:12, Arrigo Marchiori wrote:

Hello all,

please allow me to top-post as I just need a ``public reminder''.

An Italian user reported another problem [1]: they have links that
point _to the same document_ and trigger the warning.

Even if you do not understand Italian, you can download the attachment
and look at what the buttons do.

URLs are in the form: "#anchor". Therefore, we should remember to
whitelist all links starting with "#", whatever design choice we make.

Would not it be nice to file a BugZilla issue to collect all the
reports and URLs, as it happened for other ``popular'' bugs?

1: https://forum.openoffice.org/it/forum/viewtopic.php?f=9=11231

Best regards,

There seem to be quite a lot.

We should probably decide what we're going to allow.
One list I found is in urlobj.cxx [1].

Not sure yet what the differences are in internal, external, and 
official and if that may help decide.


[1] 
http://opengrok.openoffice.org/xref/trunk/main/tools/source/fsys/urlobj.cxx?r=86e1cf34#2080



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



Re: Hyperlink Warning Message

2021-05-12 Thread Carl Marcum

Hi Ken,

I see your Reload button is using an UNO call.
What is the text of the warning when you use your Close button.

Are these buttons using your macros or was it an extension you added?

Thanks,
Carl

On 5/12/21 3:32 AM, k...@kshelton.plus.com wrote:

Hello Marcus

Thanks for your prompt reply.

We also have a ‘Close’ button in our document and this now also gives the same 
warning.   The 'Reload' button is used regularly through the day as there is 
more than one person editing the document.   We would certainly appreciate 
being able to switch off this warning.

Thanks again.

Regards
Keith Shelton


On 4 May 2021, at 17:33, Marcus  wrote:

Am 04.05.21 um 16:05 schrieb k...@kshelton.plus.com:

For some years I've had a Reload button in my Calc document to avoid having to 
use the File menu. Just updated to 4.1.10 and now I get a message when pressing 
Reload button:
This hyperlink is going to open “.uno:Reload”. Do you want to proceed?
Is there a way of switching off this message please?

unfortunately, there is no option to turn it off.

And I think that the use case you have reported happens very often, so a 
solution would be very helpful. ;-)

Marcus


-
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



Fwd: [ANNOUNCE] Apache OpenOffice 4.1.10 released

2021-05-04 Thread Carl Marcum

Hello OpenOffice community,

We want to thank everyone who helped make this release happen.

Best regards,
Carl
(on behalf of the Apache OpenOffice PMC)


 Forwarded Message 
Subject:[ANNOUNCE] Apache OpenOffice 4.1.10 released
Date:   Tue, 4 May 2021 09:59:21 -0400
From:   Carl Marcum 
Organization:   Apache Software Foundation
To: annou...@openoffice.apache.org



04 May 2021 - The Apache OpenOffice project is pleased to announce the
release of Apache OpenOffice 4.1.10.

Apache OpenOffice is a popular Open Source office document productivity 
suite

available in 41 languages on Windows, macOS and Linux.

Apache OpenOffice 4.1.10 is a security release aimed at correcting an issue
with opening non-HTTP(S) links in a document.
This release also includes the latest dictionaries.
All users of Apache OpenOffice 4.1.9 or earlier are advised to upgrade.

For the complete overview see the list in Bugzilla:
https://s.apache.org/AOO-4110changes

Full version of this announcement:
https://s.apache.org/AOO-4110announcement

Apache OpenOffice 4.1.10 Release Notes:
https://s.apache.org/AOO-4110releasenotes

Download the source:
https://openoffice.apache.org/downloads.html

Download Apache OpenOffice 4.1.10 from the original source only:
https://www.openoffice.org/download/

Follow Apache OpenOffice:
Twitter   https://twitter.com/apacheoo
Facebook  https://www.facebook.com/ApacheOO
YouTube   https://www.youtube.com/openoffice
Mail  https://openoffice.apache.org/mailing-lists.html


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



Re: [Issue 128450] add junit tests to verify warning dialog for certain hyperlinks

2021-05-02 Thread Carl Marcum

Hi Matthias,

On 5/2/21 11:43 AM, Matthias Seidel wrote:

Hi Carl,

I think if you change the Assignee, we will not be able to follow the
issue via issues@ mailing list anymore...


I just made a test comment and it went to issues@ so I think it's all good.
Carl


@Marcus: Can you confirm?

Regards,

    Matthias

Am 02.05.21 um 17:40 schrieb bugzi...@apache.org:

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

Carl Marcum  changed:

What|Removed |Added

Assignee|iss...@openoffice.apache.or |cmar...@apache.org
|g   |
   Developer|--- |Medium
  Difficulty||
  Issue Type|DEFECT  |TASK




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



Re: AOO blog karma

2021-04-28 Thread Carl Marcum

Hi Marcus,

On 4/27/21 2:58 PM, Marcus wrote:

Am 27.04.21 um 20:56 schrieb Carl Marcum:
I thought I would work on the blog post for 4.1.10 if you haven't 
already.

If I get an account in time.


Infra can only add you when you login for a first time. Otherwise you 
are not "known" in the Roller system.


Please can you login?


Daniel got me fixed up.
I can author now and can work on the draft posting later today.

Thanks for your help!

Best regards,
Carl


Thanks

Marcus




On 4/27/21 12:54 PM, Marcus wrote:

Am 27.04.21 um 14:53 schrieb Carl Marcum:

How does one request blog author karma?


it seems you have no account to get any permissions.
But I also cannot add you to the Roller instance.

So, I've created a Infra ticket [1] to get your account added.

[1] https://issues.apache.org/jira/browse/INFRA-21801



-
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: [DISCUSS] [VOTE] Release AOO 4.1.10-RC2 as GA

2021-04-28 Thread Carl Marcum

Hi Jim,

On 4/28/21 7:47 AM, Jim Jagielski wrote:

The VOTE is scheduled to close today... anyone opposed if I keep it open for 
another 24-48 hours?


That's fine with me.

Thanks,
Carl

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



Re: AOO blog karma

2021-04-27 Thread Carl Marcum

Thanks Marcus!

I thought I would work on the blog post for 4.1.10 if you haven't already.
If I get an account in time.

Thanks,
Carl

On 4/27/21 12:54 PM, Marcus wrote:

Am 27.04.21 um 14:53 schrieb Carl Marcum:

How does one request blog author karma?


it seems you have no account to get any permissions.
But I also cannot add you to the Roller instance.

So, I've created a Infra ticket [1] to get your account added.

[1] https://issues.apache.org/jira/browse/INFRA-21801

Marcus


-
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



AOO blog karma

2021-04-27 Thread Carl Marcum

How does one request blog author karma?

Thanks,
Carl


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



Re: [VOTE] Release AOO 4.1.10-RC2 as GA

2021-04-26 Thread Carl Marcum

Hi All,

The Release Candidate is good for production/GA:

[X] yes / +1

[ ] no / -1

My vote is based on:

[X] binding (member of PMC)

[X] I have built and tested the RC from source on platform CentOS 7 x86-64

[X] I have tested the binary RC on platform CentOS 7 x86-64

I tested all of the source tarballs for checksum and signature.
I did the same for the Linux_x86-64_ rpm_en-US.tar.gz version of the installer, 
langpack and SDK that I installed and tested.

I manually tested the non-http(s) hyperlink fix and it works as expected.

Against my build from source:
I ran 4 passes of the 47 Automated Build Verification Tests and while a few 
flaky tests remain, all tests passed at least once and 42 passed all 4 times.
I also ran 4 passes of the Functional Verification Tests of the 735 tests that 
run on my system, there are 10 test that randomly fail at least 1 pass.
(I'm using the test-backports PR-125 to get these results)

Best regards,
Carl


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



Re: Apache OpenOffice 4.1.10-RC2

2021-04-21 Thread Carl Marcum




On 4/21/21 6:42 PM, Don Lewis wrote:

On 20 Apr, Jim Jagielski wrote:

Before we call a vote, I'd like to ask as many people as possible to give the 
2nd release candidate of AOO 4.1.10 a good, solid test.

The source files and complimentary community builds for this RC can be found at:

 https://dist.apache.org/repos/dist/dev/openoffice/4.1.10-RC2/

Looking good so far on FreeBSD.



I've been verifing checksums and signatures.
I've installed on CentOS 7 and tested the hyperlink fix.
Everything looks good so far.
Tomorrow I can build the source and run some automated tests against it.

Best regards,
Carl


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



Re: Status of Solver in OpenOffice.Calc?

2021-04-21 Thread Carl Marcum

Hi Rick,

On 4/20/21 1:36 PM, Rick Van Camp wrote:

Hello,

I was recently informed this is out of date and the files on Github agree
with this assertion. Kohei Yoshida is listed as the lead developer here:

https://wiki.openoffice.org/wiki/Optimization_Solver

I am interested in getting involved with this. I have sent Kohei a message
directly but was also encouraged to post on this mailing list.

Please let me know.


Best wishes,

Rick Van Camp



Welcome !

Have you worked on OpenOffice or other Apache projects before?
If not you may want to review the Orientation page [1].

Are you subscribed to the dev@ list?

It's good if you post a little about what you plan in case other may 
want to collaborate.


If it's a lot of work we can create a branch to make it easier for 
others to collaborate and to get in progress work into the repo and test.


[1] https://openoffice.apache.org/orientation/index.html

Best regards,
Carl


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



Re: Apache OpenOffice 4.1.10-RC2

2021-04-20 Thread Carl Marcum

Hi Jim,

On 4/20/21 2:31 PM, Jim Jagielski wrote:

Before we call a vote, I'd like to ask as many people as possible to give the 
2nd release candidate of AOO 4.1.10 a good, solid test.

The source files and complimentary community builds for this RC can be found at:

 https://dist.apache.org/repos/dist/dev/openoffice/4.1.10-RC2/

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


I should be able to review tomorrow evening.

Best regards,
Carl

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



Re: Status of "Solver"

2021-04-20 Thread Carl Marcum

Hi Matthias,

On 4/20/21 9:27 AM, Matthias Seidel wrote:

Hi Carl,

Am 20.04.21 um 15:11 schrieb Carl Marcum:

Hi Rick,

On 4/19/21 8:59 PM, Rick Van Camp wrote:

Hello,

The information I read on the "Spreadsheet Project" does not appear
to be
correct as it regards the solver. Where, or whom can I learn more about
this project?It appears Oracle has, or had something to do with this
but no
one can really determine anything regarding any aspect of "Solver"
from the
information on the webpage.

Can you tell us what page you refer to.  We have many websites and
wikis for the project.

A good place to start is our project website [1].
Oracle donated OpenOffice.org to the ASF and became Apache OpenOffice.

We are a group of volunteers that maintain and release the software,
maintain the infrastructure, support users, etc.

The Solver you mentioned may refer to the output directory structure
created when building the office source.
There was a time when this was provided in a tarball but that was
before my time.
I found this 20 year old page on our user site here [2].

I think he is referring to the Solver included in Calc:

https://wiki.openoffice.org/wiki/Documentation/OOo3_User_Guides/Calc_Guide/Solver

I reworked the dialog for it a while ago, but I really don't know what
it is good for... ;-)

Thanks for the help. I've never used it either :).

Best regards,
Carl



Regards,

    Matthias


[1] https://openoffice.apache.org/
[2] http://www.openoffice.org/dev_docs/source/solver.html

Best regards,
Carl


Thank you,

Rick Van Camp



-
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: Status of "Solver"

2021-04-20 Thread Carl Marcum

Hi Rick,

On 4/19/21 8:59 PM, Rick Van Camp wrote:

Hello,

The information I read on the "Spreadsheet Project" does not appear to be
correct as it regards the solver. Where, or whom can I learn more about
this project?It appears Oracle has, or had something to do with this but no
one can really determine anything regarding any aspect of "Solver" from the
information on the webpage.
Can you tell us what page you refer to.  We have many websites and wikis 
for the project.


A good place to start is our project website [1].
Oracle donated OpenOffice.org to the ASF and became Apache OpenOffice.

We are a group of volunteers that maintain and release the software, 
maintain the infrastructure, support users, etc.


The Solver you mentioned may refer to the output directory structure 
created when building the office source.
There was a time when this was provided in a tarball but that was before 
my time.

I found this 20 year old page on our user site here [2].

[1] https://openoffice.apache.org/
[2] http://www.openoffice.org/dev_docs/source/solver.html

Best regards,
Carl



Thank you,

Rick Van Camp




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



Re: [GitHub] [openoffice] jimjag commented on pull request #127: Allow all https(s) Hyperlinks

2021-04-16 Thread Carl Marcum



I'm building this PR now.  I should have it tested soon.


On 4/16/21 2:02 PM, GitBox wrote:

jimjag commented on pull request #127:
URL: https://github.com/apache/openoffice/pull/127#issuecomment-821368755


+1





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



Re: Request for reviewers: PR 126

2021-04-16 Thread Carl Marcum

Hi Arrigo,

On 4/16/21 12:36 PM, Arrigo Marchiori wrote:

Dear All,

PR 126 [1] is about the "About" dialog (sorry for the word play :-).

It fixes an invalid display of the build number for 4.4.10 that... we
need for the first time, because we hve never reached a two-digit
version until today.

Matthias and I gave our approval but a ``third opinion'' would
greatly be appreciated.

Jim was requested for reviewing but he seems to be quite busy at the
moment. Could anyone else help us, please?

Thank you in advance!

1: https://github.com/apache/openoffice/pull/126

I'll review it soon.

Best regards,
Carl

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



Re: Code execution in Apache OpenOffice via non-http(s) schemes in Hyperlinks

2021-04-16 Thread Carl Marcum
Thank you Dave for all your work and co-ordination with security, the 
reporter, and communications.


Best regards,
Carl

On 4/15/21 4:06 PM, Dave Fisher wrote:

Hi -

Here is some background on the issue which has apparently existed since about 
OpenOffice.org 2.0 in 2005 or so.

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

Some confusion existed between types of hyperlinks and rather than filtering 
they were all allowed to proceed.

Arrigo restored the code and Carl added some protocol checks:
https://github.com/apache/openoffice/commit/aa358bfc895091e0ee5382ad1d25e5d51261463b

This current code will cause a warning for any http(s) hyperlinks that do not 
have an extension in the “whitelist.”

Some think that we should blanket allow all http(s) hyperlinks so I’ve created 
a PR for that:
https://github.com/apache/openoffice/pull/127

Topics for 4.2.0 include:
(1) A better dialog box for the hyperlink security warning
(2) Implement an option to allow users to choose from 3 levels of hyperlink 
security that is in the code, but not the settings. The levels in the code are 
essentially:
- No Security
- What we have now
- And only help links

All The Best,
Dave



On Apr 15, 2021, at 12:34 PM, Dave Fisher  wrote:

Hi -

We are working on releasing 4.1.10 soon do to this security report [1] which 
was announced today.

I’d like to credit Arrigo Marchiori and Carl Marcum for development. Ariel 
Constenla-Haile and Peter Kovacs for our indispensible OpenGrok setup. Matthias 
Seidel, Marcus Lange, Jim Jagielski, and Don Lewis for builds and testing.

All The Best,
Dave

[1] https://positive.security/blog/url-open-rce


On Apr 15, 2021, at 12:18 PM, Dave Fisher  wrote:

Severity: moderate

Description:

The project received a report that all versions of Apache OpenOffice through 
4.1.8 can open non-http(s) hyperlinks. The problem has existed since about 2006 
and the issue is also in 4.1.9. If the link is specifically crafted this could 
lead to untrusted code execution. It is always best practice to be careful 
opening documents from unknown and unverified sources. The mitigation in Apache 
OpenOffice 4.1.10 (unreleased) assures that a security warning is displayed 
giving the user the option of continuing to open the hyperlink.

Credit:

Fabian Bräunlein and Lukas Euler of Positive Security




-
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: AOO 4.1.10-RC1

2021-04-13 Thread Carl Marcum

Hi Jim,

This time to the list :)

On 4/13/21 5:27 PM, Jim Jagielski wrote:

I deem it is time for us to push through with a 4.1.10 release of AOO. I am 
proposing a AOO 4.1.10-RC1 release sometime over the next week. I am currently 
building macOS and Linux 64/32 tests (RC1s) for HEAD of AOO41X
-


That's great Thanks!
Carl

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



Re: [LAZY CONSENSUS] Merge PR-125 into 4.1.X branch

2021-04-12 Thread Carl Marcum

Hi Dave,

I believe all these changes and new tests exist in trunk and 4.2.X.
I cherry-picked these because they were not back-ported to 4.1 and 
didn't involve any files in main.


Best regards,
Carl


On 4/12/21 7:03 PM, Dave Fisher wrote:

Hi -

The PR is all tests. Is it applied to trunk and AOO420?

Regards,
Dave


On Apr 12, 2021, at 3:15 PM, Carl Marcum  wrote:

Hi Marcus,

I will wait until after the next release on this line and propose it again.

If anyone wants to run the tests with these updates they can merge the PR into 
a fork and build and run them against a test build.

Hi Matthias,

Thanks for testing a build with PR.

Best regards,
Carl

On 4/12/21 12:21 PM, Matthias Seidel wrote:

Hi,

Am 12.04.21 um 18:17 schrieb Marcus:

Am 11.04.21 um 20:58 schrieb Carl Marcum:

Since this is a rather large pull request based on many commits I
want to use lazy consensus here.

This PR-125 [1] is based on a lot of work by Damjan and a few others
on fixing flaky automated tests and other improvements that could be
back-ported to the 4.1 line.
Also included is a fix for the 3 FVT tests that hang waiting on the
test runner to accept a dialog.
As I run a lot of these tests I think these are useful to the 4.1 line.

Everything is below the test directory so it should not affect any
builds.

Unless there are objections I plan to pull these in to the 4.1.X
branch after 72 hours.

[1] https://github.com/apache/openoffice/pull/125

please wait until the new release is done.

We have waited much too long. ;-)

Carl did mention that the build itself is not affected.
BTW: I already did a build for Windows without problems.

Matthias


We shouldn't do too many things at the same time on the same loction.

Thanks

Marcus


-
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: [LAZY CONSENSUS] Merge PR-125 into 4.1.X branch

2021-04-12 Thread Carl Marcum

Hi Marcus,

I will wait until after the next release on this line and propose it again.

If anyone wants to run the tests with these updates they can merge the 
PR into a fork and build and run them against a test build.


Hi Matthias,

Thanks for testing a build with PR.

Best regards,
Carl

On 4/12/21 12:21 PM, Matthias Seidel wrote:

Hi,

Am 12.04.21 um 18:17 schrieb Marcus:

Am 11.04.21 um 20:58 schrieb Carl Marcum:

Since this is a rather large pull request based on many commits I
want to use lazy consensus here.

This PR-125 [1] is based on a lot of work by Damjan and a few others
on fixing flaky automated tests and other improvements that could be
back-ported to the 4.1 line.
Also included is a fix for the 3 FVT tests that hang waiting on the
test runner to accept a dialog.
As I run a lot of these tests I think these are useful to the 4.1 line.

Everything is below the test directory so it should not affect any
builds.

Unless there are objections I plan to pull these in to the 4.1.X
branch after 72 hours.

[1] https://github.com/apache/openoffice/pull/125

please wait until the new release is done.

We have waited much too long. ;-)

Carl did mention that the build itself is not affected.
BTW: I already did a build for Windows without problems.

Matthias


We shouldn't do too many things at the same time on the same loction.

Thanks

Marcus


-
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



[LAZY CONSENSUS] Merge PR-125 into 4.1.X branch

2021-04-11 Thread Carl Marcum

Hi All,

Since this is a rather large pull request based on many commits I want 
to use lazy consensus here.


This PR-125 [1] is based on a lot of work by Damjan and a few others on 
fixing flaky automated tests and other improvements that could be 
back-ported to the 4.1 line.
Also included is a fix for the 3 FVT tests that hang waiting on the test 
runner to accept a dialog.

As I run a lot of these tests I think these are useful to the 4.1 line.

Everything is below the test directory so it should not affect any builds.

Unless there are objections I plan to pull these in to the 4.1.X branch 
after 72 hours.


[1] https://github.com/apache/openoffice/pull/125

Best regards,
Carl


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



Re: [DISCUSS] need for a AOO41X branch

2021-03-28 Thread Carl Marcum

Hi Marcus,

On 3/28/21 11:02 AM, Marcus wrote:

Am 28.03.21 um 16:14 schrieb Carl Marcum:
I'm wondering if we should create a branch we can use for 
continuation of the 4.1.x line to have a place to PR cherry-picks, 
bug fixes, etc. in case we need another release on that line.


IMHO we have already agreed in the past that we want to create a new 
AOO41X branch when a release has been published.


Great, can that be done from GitHub or does it have to start with Gitbox?
I only have the GitHub repo.
I've created feature branches from GitHub but not one this important :)

Would it just branch from AOO419 head?

If so and GitHub is fine then I can create it.



For instance I've got a number of commits (about 26) I've cherry 
picked mostly from Damjan's work on fixing flaky tests and new tests 
that never made into the 4.1 line that I don't have a place to put them.


Would be great. Don't forget to place them also into the AOO420 branch 
and trunk if not yet done.


I believe they already exist in both trunk and AOO42X but I'll check.




This is assuming we're not using AOO419 for this.


We shouldn't use 1 branch for 2 or more releases. Then it's not clear 
which commits belong to what release.


That's what I thought.



Marcus


-
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



[DISCUSS] need for a AOO41X branch

2021-03-28 Thread Carl Marcum

Hi All,

I'm wondering if we should create a branch we can use for continuation 
of the 4.1.x line to have a place to PR cherry-picks, bug fixes, etc. in 
case we need another release on that line.


For instance I've got a number of commits (about 26) I've cherry picked 
mostly from Damjan's work on fixing flaky tests and new tests that never 
made into the 4.1 line that I don't have a place to put them.


This is assuming we're not using AOO419 for this.

Best regards,
Carl

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



Re: Macro book

2021-03-13 Thread Carl Marcum

Thanks Francis!

Best regards,
Carl

On 3/13/21 9:44 AM, F Campos Costero wrote:

Hi Carl,
Andrew Pitonyak's website  [https://www.pitonyak.org/oo.php] lists a 4th
edition, which I suppose is up to date.
Francis

On Sat, Mar 13, 2021 at 7:05 AM Carl Marcum  wrote:


Hi Michael,

Where can I find the english version for the 4th edition?

Thanks,
Carl

On 1/29/21 11:04 AM, Dr. Michael Stehmann wrote:

Hello,

Andrew Pitonyak puplished his book "OpenOffice.org Macros Explained"
on 19th of June 2018 (4.th edition).

Now there is an extended german translation available:

https://www.uni-due.de/~abi070/ooo.html

It's a great work. As far as I see it's the only up-to-date and
available book for this subject.

And so it is very relevant.

It has been notified on users...@openoffice.apache.org .

Kind regards
Michael



-
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: Macro book

2021-03-13 Thread Carl Marcum

Thanks Andrew!

Best regards,
Carl

On 3/13/21 10:00 AM, Andrew Pitonyak wrote:

https://www.pitonyak.org/OOME_4_0.odt


On Saturday, March 13, 2021 09:05 EST, Carl Marcum  wrote:
  Hi Michael,

Where can I find the english version for the 4th edition?

Thanks,
Carl

On 1/29/21 11:04 AM, Dr. Michael Stehmann wrote:

Hello,

Andrew Pitonyak puplished his book "OpenOffice.org Macros Explained"
on 19th of June 2018 (4.th edition).

Now there is an extended german translation available:

https://www.uni-due.de/~abi070/ooo.html

It's a great work. As far as I see it's the only up-to-date and
available book for this subject.

And so it is very relevant.

It has been notified on users...@openoffice.apache.org .

Kind regards
Michael



-
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: Macro book

2021-03-13 Thread Carl Marcum

Hi Michael,

Where can I find the english version for the 4th edition?

Thanks,
Carl

On 1/29/21 11:04 AM, Dr. Michael Stehmann wrote:

Hello,

Andrew Pitonyak puplished his book "OpenOffice.org Macros Explained" 
on 19th of June 2018 (4.th edition).


Now there is an extended german translation available:

https://www.uni-due.de/~abi070/ooo.html

It's a great work. As far as I see it's the only up-to-date and 
available book for this subject.


And so it is very relevant.

It has been notified on users...@openoffice.apache.org .

Kind regards
Michael




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



Re: Java 8 and Ant 1.10

2021-02-11 Thread Carl Marcum

Hi Jim,

On 2/11/21 7:30 AM, Jim Jagielski wrote:

Carl, on what platform? TIA.


CentOS 7.




On Feb 11, 2021, at 6:26 AM, Carl Marcum  wrote:

On 2/9/21 6:39 PM, Carl Marcum wrote:

On 2/8/21 8:54 PM, Carl Marcum wrote:

On 2/8/21 7:15 PM, Carl Marcum wrote:

Hi Jim,

On 2/8/21 12:51 PM, Jim Jagielski wrote:

Anyone tried building HEAD of AOO42X w/ Java8 (or later) and
Apache Ant 1.10?

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


Normally I build 4.1 and trunk on the same VM's and use JDK 8 and Ant 1.9.

I've kicked off a build of trunk with Ant 1.10.15 and JDK 15.0.2.
My trunk is not completely up to date but it's withing a few weeks.
configure complained about JAVA_HOME even though I have it set so I added the 
--with-jdk-home flag.

I'll let you know how it goes.

If trunk won't answer your question I can try and up to date 4.2 tomorrow.

Best regards,
Carl

No luck,

7 module(s):
 beanshell
 hsqldb
 apache-commons
 rhino
 saxon
 lucene
 javaunohelper
need(s) to be rebuilt

I'll try with an updated 4.2 branch tomorrow.

Best regards,
Carl


Building with an up to date AOO42X branch and
Ant 1.10.15 and JDK 15.0.2. turned out with similar results.

9 module(s):
 beanshell
 hsqldb
 apache-commons
 rhino
 saxon
 lucene
 qadevOOo
 bean
 odk
need(s) to be rebuilt

I'll test backing down Ant next.

regards,
Carl


So far I've been able to build 4.2 with Ant 1.10.8 and JDK 8 but not 11 or 15.

Best regards,
Carl


-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org 
<mailto:dev-unsubscr...@openoffice.apache.org>
For additional commands, e-mail: dev-h...@openoffice.apache.org 
<mailto: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: Java 8 and Ant 1.10

2021-02-11 Thread Carl Marcum

On 2/9/21 6:39 PM, Carl Marcum wrote:

On 2/8/21 8:54 PM, Carl Marcum wrote:

On 2/8/21 7:15 PM, Carl Marcum wrote:

Hi Jim,

On 2/8/21 12:51 PM, Jim Jagielski wrote:

Anyone tried building HEAD of AOO42X w/ Java8 (or later) and
Apache Ant 1.10?

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



Normally I build 4.1 and trunk on the same VM's and use JDK 8 and 
Ant 1.9.


I've kicked off a build of trunk with Ant 1.10.15 and JDK 15.0.2.
My trunk is not completely up to date but it's withing a few weeks.
configure complained about JAVA_HOME even though I have it set so I 
added the --with-jdk-home flag.


I'll let you know how it goes.

If trunk won't answer your question I can try and up to date 4.2 
tomorrow.


Best regards,
Carl


No luck,

7 module(s):
    beanshell
    hsqldb
    apache-commons
    rhino
    saxon
    lucene
    javaunohelper
need(s) to be rebuilt

I'll try with an updated 4.2 branch tomorrow.

Best regards,
Carl


Building with an up to date AOO42X branch and
Ant 1.10.15 and JDK 15.0.2. turned out with similar results.

9 module(s):
    beanshell
    hsqldb
    apache-commons
    rhino
    saxon
    lucene
    qadevOOo
    bean
    odk
need(s) to be rebuilt

I'll test backing down Ant next.

regards,
Carl

So far I've been able to build 4.2 with Ant 1.10.8 and JDK 8 but not 11 
or 15.


Best regards,
Carl


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



Re: Java 8 and Ant 1.10

2021-02-10 Thread Carl Marcum

Hi Matthias,

On 2/9/21 6:47 PM, Matthias Seidel wrote:

Hi Carl,

Am 10.02.21 um 00:39 schrieb Carl Marcum:

On 2/8/21 8:54 PM, Carl Marcum wrote:

On 2/8/21 7:15 PM, Carl Marcum wrote:

Hi Jim,

On 2/8/21 12:51 PM, Jim Jagielski wrote:

Anyone tried building HEAD of AOO42X w/ Java8 (or later) and
Apache Ant 1.10?

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


Normally I build 4.1 and trunk on the same VM's and use JDK 8 and
Ant 1.9.

I've kicked off a build of trunk with Ant 1.10.15 and JDK 15.0.2.
My trunk is not completely up to date but it's withing a few weeks.
configure complained about JAVA_HOME even though I have it set so I
added the --with-jdk-home flag.

I'll let you know how it goes.

If trunk won't answer your question I can try and up to date 4.2
tomorrow.

Best regards,
Carl

No luck,

7 module(s):
     beanshell
     hsqldb
     apache-commons
     rhino
     saxon
     lucene
     javaunohelper
need(s) to be rebuilt

I'll try with an updated 4.2 branch tomorrow.

Best regards,
Carl


Building with an up to date AOO42X branch and
Ant 1.10.15 and JDK 15.0.2. turned out with similar results.

Ant should be 1.10.9 (typo?). But Java 15 is out of luck, I think.


Yes sorry, Ant 1.10.8. I also have 1.9.15.

BTW I use SDKMAN on Linux and it makes it very easy and fast to swap 
versions of things like Java and Ant.

https://sdkman.io/

Thanks,
Carl


9 module(s):
     beanshell
     hsqldb
     apache-commons
     rhino
     saxon
     lucene
     qadevOOo
     bean
     odk
need(s) to be rebuilt

I'll test backing down Ant next.

Better try to build with Java 8 or 11 (LTS). But I don't think we had a
successful build with Java 11 so far...

Regards,

    Matthias


regards,
Carl


-
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: Java 8 and Ant 1.10

2021-02-09 Thread Carl Marcum

On 2/8/21 8:54 PM, Carl Marcum wrote:

On 2/8/21 7:15 PM, Carl Marcum wrote:

Hi Jim,

On 2/8/21 12:51 PM, Jim Jagielski wrote:

Anyone tried building HEAD of AOO42X w/ Java8 (or later) and
Apache Ant 1.10?

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



Normally I build 4.1 and trunk on the same VM's and use JDK 8 and Ant 
1.9.


I've kicked off a build of trunk with Ant 1.10.15 and JDK 15.0.2.
My trunk is not completely up to date but it's withing a few weeks.
configure complained about JAVA_HOME even though I have it set so I 
added the --with-jdk-home flag.


I'll let you know how it goes.

If trunk won't answer your question I can try and up to date 4.2 
tomorrow.


Best regards,
Carl


No luck,

7 module(s):
    beanshell
    hsqldb
    apache-commons
    rhino
    saxon
    lucene
    javaunohelper
need(s) to be rebuilt

I'll try with an updated 4.2 branch tomorrow.

Best regards,
Carl


Building with an up to date AOO42X branch and
Ant 1.10.15 and JDK 15.0.2. turned out with similar results.

9 module(s):
    beanshell
    hsqldb
    apache-commons
    rhino
    saxon
    lucene
    qadevOOo
    bean
    odk
need(s) to be rebuilt

I'll test backing down Ant next.

regards,
Carl


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



Re: Java 8 and Ant 1.10

2021-02-08 Thread Carl Marcum

On 2/8/21 7:15 PM, Carl Marcum wrote:

Hi Jim,

On 2/8/21 12:51 PM, Jim Jagielski wrote:

Anyone tried building HEAD of AOO42X w/ Java8 (or later) and
Apache Ant 1.10?

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



Normally I build 4.1 and trunk on the same VM's and use JDK 8 and Ant 
1.9.


I've kicked off a build of trunk with Ant 1.10.15 and JDK 15.0.2.
My trunk is not completely up to date but it's withing a few weeks.
configure complained about JAVA_HOME even though I have it set so I 
added the --with-jdk-home flag.


I'll let you know how it goes.

If trunk won't answer your question I can try and up to date 4.2 
tomorrow.


Best regards,
Carl


No luck,

7 module(s):
    beanshell
    hsqldb
    apache-commons
    rhino
    saxon
    lucene
    javaunohelper
need(s) to be rebuilt

I'll try with an updated 4.2 branch tomorrow.

Best regards,
Carl


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



Re: Java 8 and Ant 1.10

2021-02-08 Thread Carl Marcum

Hi Jim,

On 2/8/21 12:51 PM, Jim Jagielski wrote:

Anyone tried building HEAD of AOO42X w/ Java8 (or later) and
Apache Ant 1.10?

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



Normally I build 4.1 and trunk on the same VM's and use JDK 8 and Ant 1.9.

I've kicked off a build of trunk with Ant 1.10.15 and JDK 15.0.2.
My trunk is not completely up to date but it's withing a few weeks.
configure complained about JAVA_HOME even though I have it set so I 
added the --with-jdk-home flag.


I'll let you know how it goes.

If trunk won't answer your question I can try and up to date 4.2 tomorrow.

Best regards,
Carl

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



Re: [PROPOSAL] add an unsubscribe/help footer to recruitment ML

2021-02-07 Thread Carl Marcum

Hi All,

The unsubscribe and help footer has been added to recruitment@ list.

Best regards,
Carl

On 1/25/21 6:45 PM, Carl Marcum wrote:



On 1/19/21 12:23 PM, Marcus wrote:

Am 19.01.21 um 01:08 schrieb Carl Marcum:

On 1/17/21 3:41 PM, Andrea Pescetti wrote:

On 10/01/2021 Peter Kovacs wrote:

On 10.01.21 23:42, Andrea Pescetti wrote:
But we should also be more proactive and remove people when they 
ask for it on the list: Whimsy https://whimsy.apache.org/ ...

The moderators are Patricia, Andrea and Marcus.


I confirm that indeed I use Whimsy to help people unsubscribe the 
recruitment list when their intention is clear and when they are 
confused about how to do it. I hope the new footer will help limit 
these cases.



So should I go ahead with this if we are renaming the list?
I don't to create work for infra if it's not needed.


I haven't seen any objection since days, so I would assume that a) 
renaming the mailing list and b) adding a footer is OK.


Please go ahead. :-)

Marcus


I put in a ticket for the footer [1].

The rename I'll let someone else submit.

[1] https://issues.apache.org/jira/browse/INFRA-21343

Best regards,
Carl




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



FOSDEM 2021 - OpenOffice UNO Programming with Groovy

2021-02-06 Thread Carl Marcum

I have uploaded my talk to YouTube also.

https://youtu.be/izgFWgo0low

Best regards,
Carl


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



Re: Video Uploads for FOSDEM

2021-02-02 Thread Carl Marcum

Hi Peter,

Mine shows a Final Video URL = Final Version and the link starts the 
talk so I think mine is done.

I do need to upload my slide deck this evening though.

Thanks,
Carl

On 2/1/21 6:05 PM, Peter Kovacs wrote:

Hello all,


we need to upload the videos. Current state is according to the 
Organisator List that 2 of 8 are uploaded.


If I look in the registration I find more videos. However in order to 
be finalized, the videos have to be uploaded


in the General Tab -> shedule Box (the one on the bottom) and there 
*Pre-recorded Video Upload URL.*


*
*

*Thank you for all theior work.*

*
*

*All the Best*

*Peter
*




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



Re: [Discussion] Would we enable volunteers that develop extensions

2021-02-01 Thread Carl Marcum

Hi Peter,

On 2/1/21 1:46 AM, Peter Kovacs wrote:

I have a question. How much willing are we to support extensions.
I think for extensions like report builder where the code is donated and 
it's a high-profile extension it makes sense.

Much more so if we build and bundle during a release.

Freedom to do releases is another issue. If they're AOO sub-projects we 
need to do the releases the same way as the Office and that can be 
cumbersome for something as small as an extension when they are done 
independently and frequently and most members may not have the 
toolchains setup.


I ran into this with things like the NetBeans plugin and some other 
developer tools.


I think for the same reason ASF wants a minimum number of developers for 
a project, a lot of extensions are probably one or two developers and we 
could end up with a lot of abandoned code.




I mean we have here a voice recognition questions, there is the 
reporting tool or wiki extension.


We already thinking on creating repos for reporting tool or the wiki 
extensions.


But how do we deal with those topics on the organisatorical level?

Do we form I do not know how to name them, task force around them? Do 
the people who whish to be delevop these functions do this in an 
outside project (independant if this is a Apache project or github 
self sufficient hosted)



I would opt that we agree on some form to enable volunteer to use the 
project infrastructure and provide them with a stronger feeling that 
they are part of the project even if they are only working on an 
extension of none core features.


For most extensions I don't think this is necessary when they have 
GitHub, Sourceforge, etc.




This makes it easier to bring the community together. I mean the 
wording 3rd parties bring a lot of discussion and the need to explain 
things, to the table.


I think there are things we can do as a project to support a community 
which we need to grow.

Some of which like forums and mailing lists we already do.
Extension developers are welcome on the dev@ list.

There is an api@ list for that purpose but I thought it was shut down for lack 
of traffic and I didn't subscribe anymore but I see there are a few recent 
posts within the last year and almost no replies to them :(

Jörg had some good points about Extension Manager support and other tools for 
extensions and you may know I'm working on new extension creation tools as 
well.  We can also make sure the Developer Guide is up to date and things like 
that.




I am just wondering what everyone else thinks.

All the best

Peter




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



Re: [PROPOSAL] add an unsubscribe/help footer to recruitment ML

2021-01-25 Thread Carl Marcum




On 1/19/21 12:23 PM, Marcus wrote:

Am 19.01.21 um 01:08 schrieb Carl Marcum:

On 1/17/21 3:41 PM, Andrea Pescetti wrote:

On 10/01/2021 Peter Kovacs wrote:

On 10.01.21 23:42, Andrea Pescetti wrote:
But we should also be more proactive and remove people when they 
ask for it on the list: Whimsy https://whimsy.apache.org/ ...

The moderators are Patricia, Andrea and Marcus.


I confirm that indeed I use Whimsy to help people unsubscribe the 
recruitment list when their intention is clear and when they are 
confused about how to do it. I hope the new footer will help limit 
these cases.



So should I go ahead with this if we are renaming the list?
I don't to create work for infra if it's not needed.


I haven't seen any objection since days, so I would assume that a) 
renaming the mailing list and b) adding a footer is OK.


Please go ahead. :-)

Marcus


I put in a ticket for the footer [1].

The rename I'll let someone else submit.

[1] https://issues.apache.org/jira/browse/INFRA-21343

Best regards,
Carl


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



Re: [VOTE] Release AOO 4.1.9-RC1 as GA

2021-01-20 Thread Carl Marcum

My Vote follows..

The Release Candidate is good for production/GA:

 [X] yes / +1

 [ ] no / -1

My vote is based on:

 [X] binding (member of PMC)

 [X] I have built and tested the RC from source on platform CentOS 7 x86-64 and 
Ubuntu 18.04 x86-64.

 [X] I have tested the binary RC on platform CentOS 8 Stream (current) x86-64 
and Windows 10 x86-64 (current)

I have verified the checksums and gpg signature as good on both source 
and binaries including the SDK.
I inspected the source release and binaries and verified they contain 
the LICENSE, NOTICE, and README files required.
I ran 3 iterations of our BVT and FVT automated test suites on both 
CentOS 7 and Ubuntu 18.04 on builds from source with good results.


I also performed basic manual verification of saving, editing, and 
re-saving of both existing and new test documents.


Best regards,
Carl

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



Re: [PROPOSAL] add an unsubscribe/help footer to recruitment ML

2021-01-18 Thread Carl Marcum




On 1/17/21 3:41 PM, Andrea Pescetti wrote:

On 10/01/2021 Peter Kovacs wrote:

On 10.01.21 23:42, Andrea Pescetti wrote:
But we should also be more proactive and remove people when they ask 
for it on the list: Whimsy https://whimsy.apache.org/ ...

The moderators are Patricia, Andrea and Marcus.


I confirm that indeed I use Whimsy to help people unsubscribe the 
recruitment list when their intention is clear and when they are 
confused about how to do it. I hope the new footer will help limit 
these cases.


Regards,
  Andrea.

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


So should I go ahead with this if we are renaming the list?
I don't to create work for infra if it's not needed.

Thanks,
Carl



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



Re: [discussion] rename the recruitment list

2021-01-15 Thread Carl Marcum




On 1/13/21 1:05 PM, Dave Fisher wrote:


Sent from my iPhone


On Jan 13, 2021, at 9:55 AM, Marcus  wrote:

Am 13.01.21 um 09:25 schrieb Peter Kovacs:

I wonder if we can rename the recruitment list to something else. My theory is 
that a lot of people do not understand OpenSource in general, and recruitment 
is commonly strongly linked with Job offers. So have the theory people write us 
with the hope on a job.
Maybe a better name would support a better understanding, on how we work or 
what to expect.
Maybe something like enlistasvolunt...@openoffice.apache.org?
Or simply volunt...@openoffice.apache.org or enl...@openoffice.apache.org
what do you think? I am interested in all opinions, even if you are just a 
passive reader or from other projects.

I've also the impression that the expectation of this mail address is different 
to the one we have.

The best is when the name itself says all.

So, what about renaming to "volunteering@" or "IwantToVolunteer@"?

I like volunteer@ - it is a call to action. It is the proper verb.

Regards,
Dave



I also like volunteer@
and add the unsubscribe footer ;)

Best regards,
Carl


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



Re: AOO 4.1.9 Info

2021-01-12 Thread Carl Marcum




On 1/10/21 4:09 PM, Andrea Pescetti wrote:

On 05/01/2021 Arrigo Marchiori wrote:

I tried to ask if there is a procedure to follow for testing [1].
Do we have any? I can follow it for the Italian builds.


Things are very different depending on whether one is testing a dev 
build or a release candidate.


A list of manual tests close to the "checklist" you were looking for 
can be found here (and these apply to all builds):


https://wiki.openoffice.org/wiki/QA/TestCases/#AOO_3.4_General_Testing_Test_Cases 



and, still on the wiki, there is also a more complete dump of the 
former Testlink cases that I cannot find right now.

Maybe these?
https://www.openoffice.org/qa/testcase/



A RC (Release Candidate), instead, is very different. We ship both the 
source code and convenience binaries, but the Apache release process 
focuses mostly on legal checks to be done on the source code.


Details about voting on a RC:
http://www.apache.org/legal/release-policy.html

An example of OpenOffice RC testing (this is what I usually do; but 
other people run different tests):

https://s.apache.org/openoffice-416-tests


There are also automated tests you can run against a build.
https://wiki.openoffice.org/wiki/QA/test_automation_guide

I don't use the eclipse instructions and the Ant command line way is at 
the end.


I've been trying to clean these up and it's work in progress.
The BVT test for trunk are in pretty good shape. All 80 pass for me now.
Some in 4.1 are still flaky though. pass/fail intermittently.
Threading/Processor speeds are my theory.
I'm working on cherry picking a lot of test fixes from trunk to 4.1 but 
they're not ready yet.
There was a lot of API changes included that I don't think we should 
backport.

Anyway it won't matter after 4.2 anyway :)

Best regards,
Carl

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



Re: [proposal} Trying to re-generate the Documentation effort

2021-01-09 Thread Carl Marcum

Hi Keith,

On 1/9/21 4:40 PM, Keith N. McKenna wrote:

On 1/9/2021 12:16 PM, Dennis Hamilton wrote:

I think it is clear, from a continuing doc@oo.a.o thread, that there is no 
cheese to be found developing derivative AOO documentation from the original 
OpenOffice.org 3.2 documentation that was produced outside of OpenOffice.org 
itself.

I wonder if a more vibrant and experienced avenue might be found by consulting 
the Apache OpenOffice Community Forum,
.

  - Dennis

-Original Message-
From: Keith N. McKenna 
Sent: Tuesday, December 8, 2020 14:58
To: d...@openoffice.apache.org
Cc: dev@openoffice.apache.org
Subject: Re: [proposal} Trying to re-generate the Documentation effort

[orcmid] [ ... ]


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


Actually Dennis that may not be true. According to the the Legal FAQ
site https://www.apache.org/foundation/license-faq.html#GPL the Gnu
Public License version 3 is compatible with ALv2.

Regards
Keith


I might be wrong but I'm reading that statement as ALv2 is compatible 
with GPL v3 not the other way around.

It is a statement quoted from the FSF site.

Best regards,
Carl


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



Re: Testing of new version of Apache OpenOffice

2021-01-09 Thread Carl Marcum

Hi Fredrik,

(with corrected address)

Thank you for your continued use of OpenOffice.

The best way to find out about new releases or test builds would be to 
subscribe to this dev@ list by sending an email to 
dev-subscr...@openoffice.apache.org 



If the dev@ list is too much volume we have a qa@ list if you're more 
interested in testing than development activities.
qa-subscr...@openoffice.apache.org 



Best regards,
Carl


On 1/9/21 10:23 AM, Fredrik L wrote:

Hi,
I have a huge OpenOffice calc "application" including many ods files with basic 
code and python code connected with each other.
If you want me to test any upcoming versions of Apache OpenOffice in the future 
with my files that I have to see if anything seams out of the ordinary please 
send me download links of where I can download upcoming versions of Apache 
Openoffice and I will report any issues found. I primarily will test on Windows 
10 but can also test on SparkyLinux if desired.

I also would like to thank everyone of you maintaining Apache OpenOffice as 
Calc in LibreOffice is not an option for me. Too many times strange updates of 
LibreOffice have made my code useless so I have given up on it. With Apache 
OpenOffice my code just keeps running fine with every new release so far.

Best Regards,
Fredrik Lönn in Sweden
Website:www.senib.com





Re: Testing of new version of Apache OpenOffice

2021-01-09 Thread Carl Marcum

Hi Fredrik,

Thank you for your continued use of OpenOffice.

The best way to find out about new releases or test builds would be to 
subscribe to this dev@ list by sending an email to 
dev-subscr...@openoffice.apache.org 



If the dev@ list is too much volume we have a qa@ list if you're more 
interested in testing than development activities.
qa-subscr...@openoffice.apache.org 



Best regards,
Carl


On 1/9/21 10:23 AM, Fredrik L wrote:

Hi,
I have a huge OpenOffice calc "application" including many ods files with basic 
code and python code connected with each other.
If you want me to test any upcoming versions of Apache OpenOffice in the future 
with my files that I have to see if anything seams out of the ordinary please 
send me download links of where I can download upcoming versions of Apache 
Openoffice and I will report any issues found. I primarily will test on Windows 
10 but can also test on SparkyLinux if desired.

I also would like to thank everyone of you maintaining Apache OpenOffice as 
Calc in LibreOffice is not an option for me. Too many times strange updates of 
LibreOffice have made my code useless so I have given up on it. With Apache 
OpenOffice my code just keeps running fine with every new release so far.

Best Regards,
Fredrik Lönn in Sweden
Website: www.senib.com





[PROPOSAL] add an unsubscribe/help footer to recruitment ML

2021-01-08 Thread Carl Marcum

Hi All,

It seems we get a lot of unsubscribe requests to the recruitment@ ML.

I propose we add a unsubscribe footer to that list like we have with 
dev@ and some others.


Sorry this is a proposal without a known solution (on my part) but I 
suspect a ticket to infra may be involved which I could create.


Lazy Consensus in in effect for this and if there are no objections I'll 
figure out how to implement it in 72 hours.


Best regards,
Carl

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



Re: [openoffice] branch trunk updated: 'fakeroot' is no longer optional, but required, when making deb/dpkg so no need to worry about the old hack and seeing if we have fakeroot.

2021-01-03 Thread Carl Marcum

Just FYI that I just built trunk on Ubuntu 18.04 with:

$ ./configure \
--with-system-stdlibs \
--enable-category-b \
--enable-beanshell \
--enable-wiki-publisher \
--enable-bundled-dictionaries \
--enable-dbus  \
--without-junit \
--without-stlport \
--with-package-format="installed" \
--with-dmake-url=https://github.com/jimjag/dmake/archive/v4.13.1/dmake-4.13.1.tar.gz 
\

--with-epm-url=https://github.com/jimjag/epm/archive/v5.0.0/epm-5.0.0.tar.gz

and was able to start it up fine.

For some reason I can't use --enable-gstreamer
(libgstreamer1.0-0, -dev, and -dbg are installed)
or --enable-opengl
libopengl0 is installed (don't see a -dev library available)

But that's probably for another thread. Only noted here as a difference.

Best regards,
Carl

On 1/3/21 10:22 AM, Jim Jagielski wrote:

Followed up on the bugz ticket...


On Jan 3, 2021, at 9:16 AM, Matthias Seidel  wrote:

Hi Jim,

One user has a problem with this commit, see:

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

Could you have a look?

Regards,

Matthias




-
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: Linux virtual machines for release builds

2021-01-02 Thread Carl Marcum

Hi Arrigo,

On 1/2/21 9:12 AM, Arrigo Marchiori wrote:

Dear All,

the wiki page "Step by step building guides for different platforms"
[1] mentions:

  - CentOS 5 for AOO 4.1.x
and lists the commands to prepare a x86_64 VM;

  - CentOS 7 for AOO 4.2.x
but it also states that "the community builds of AOO 4.2.x and
later are built on Fedora19" [2].

  - That Ubuntu 18.04 and Debian 9 will be the choice for AOO 4.2 [3].

Can someone please help me understand:

  1- do we build both AOO 4.1.x 64bit and 32bit releases on a x86_64
 VM? Or do we use a 32bit VM for 32bit builds?

  2- on what distro do we actually build AOO 4.2.x on? (both 32bit and
 64 bit)?

  3- is there a fixed short sequence of commands to prepare the VM for
 AOO 4.2.x, such as provided for the CentOS 5 VM [4]?
In this earlier thread [1] I had documented my notes from setups of VM's 
for building 4.2 on CentOS 7 and Ubuntu 18. There maybe some other 
answers in there as well.


I can also give you my list of dependencies for 4.1 if you need them.

[1] 
https://lists.apache.org/thread.html/r1f6bf5131f3a6a3dcd5c182140a871422c6fe9ab4ff0ac9b6b2b49e3%40%3Cdev.openoffice.apache.org%3E


Best regards,
Carl


I would like to make the wiki page a bit more clear (IMHO) with the
information you will give me.

Thank you in advance and best regards.

References

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

2: 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Fedora19

3: 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Ubuntu_16.04

4: 
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Setup_a_VM



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



Re: Happy new year!

2021-01-01 Thread Carl Marcum

Happy New Year!!

It feels like there is good momentum going forward!

Best regards,
Carl

On 1/1/21 5:06 PM, Matthias Seidel wrote:

Happy new year to all of you!

Let's make 2021 a great year for Apache OpenOffice!

Regards,

    Matthias





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



Re: Policy to deal with old web content - Archiving pages?

2020-12-30 Thread Carl Marcum

Hi Jörg,

On 12/30/20 1:42 AM, Jörg Schmidt wrote:

-Original Message-
From: Carl Marcum [mailto:cmar...@apache.org]
Sent: Tuesday, December 29, 2020 7:55 PM
To: dev@openoffice.apache.org
Subject: Re: Policy to deal with old web content - Archiving pages?

Hi Jörg,

On 12/29/20 3:54 AM, Jörg Schmidt wrote:


How do we want to define "outdated pages"?

Many pages are seemingly(!) outdated, but in reality they

are needed (e.g. for the daily voluntary support on mailing
lists or in forums).

Look e.g. at the extremely important pages with technical

info for the creation of extensions:
https://wiki.openoffice.org/wiki/Documentation/DevGuide/Extens
ions/Extensions

These pages are outdated in parts, but still there is no

more current information.
Can you help identify where the outdated content in this section is?

technical, yes, I can. But there are practical problems:

It is hardly possible to identify obsolete content 'in one piece', because that 
would amount to working as follows:

-read a piece of the Developersguide (e.g. one paragraph).
-knowing what is outdated and marking/updating it _or_ if you don't know 
immediately what is outdated, checking it by testing it

This way of working would take a lot of time.

It would be more practical to mark outdated things whenever _you_ discover them 
while using the Developersguide.
But this is a continuous process.

And there is, for me personally, a problem:
I work daily in the voluntary end user support (on 
users...@openoffice.apache.org and in the forum de.openoffice.info) and I work, 
since a long time, on the update of the German end user documentation - if I 
should update the Developersguide, I would have to give up this work, I don't 
think I want to give it up.



Okay, I thought you may have a specific example.

We all contribute where we a happiest :)

I think for something like the developer guides (Basic included) that it 
is more likely that a paragraph may be outdated rather than a whole page 
and how do we also account for that.


And we need a way that someone who can and wants to fix things can find 
them. Tags, keywords, etc.


Best regards,
Carl

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



Re: Policy to deal with old web content - Archiving pages?

2020-12-29 Thread Carl Marcum

Hi Jörg,

On 12/29/20 3:54 AM, Jörg Schmidt wrote:


How do we want to define "outdated pages"?

Many pages are seemingly(!) outdated, but in reality they are needed (e.g. for 
the daily voluntary support on mailing lists or in forums).
Look e.g. at the extremely important pages with technical info for the creation 
of extensions:
https://wiki.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions

These pages are outdated in parts, but still there is no more current 
information.

Can you help identify where the outdated content in this section is?

I think it is important that the developer guide is brought up to date.

I look at the developer guide more like a book that needs updated than a 
collection of individual pages like much of the wiki and perhaps what we 
decide for general wiki pages and guides are different.


Just my thoughts.

Best regards,
Carl

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



[QA] Verification Test Report macro

2020-12-27 Thread Carl Marcum

Hi All,

For those that run the automated tests after a build.
I wrote a Groovy macro to import the XML results from JUnit into Calc as 
another option besides the HTML reports.


A short video on it's use and where to get it.

https://youtu.be/mpC6gNUuWCY

Please let me know if you have any questions.

Thanks,
Carl

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



Re: New Committer: Arrigo Marchiori

2020-12-27 Thread Carl Marcum

Welcome to being a committer Arrigo!

Thanks again for your help with the MWiki extension.

I'm using the Dev Guide daily again!

Best regards,
Carl

On 12/26/20 4:19 PM, Marcus wrote:

The Apache OpenOffice project is happy to have a new committer on board:

Arrigo Marchiori

Please give him a warm welcome. :-)

Marcus
(on behalf of the Apache OpenOffice PMC)

-
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: MediaWiki Extensions - IDL link improvement

2020-12-22 Thread Carl Marcum

Hi Dave and Matthias,

On 12/22/20 5:18 PM, Dave Fisher wrote:

Hi Carl,

Please proceed.

Thanks,
Dave

Sent from my iPhone


On Dec 22, 2020, at 1:52 PM, Carl Marcum  wrote:

Hi Dave and Matthias,


On 12/22/20 3:47 PM, Matthias Seidel wrote:
Hi Dave,


Am 22.12.20 um 19:51 schrieb Dave Fisher:
Hi -

In OOoIDLtags.php

All of the href are in the old style of 
"http://api.openoffice.org/api/docs/common/ref/“

These should be rewritten in two ways to 
“https://www.openoffice.org/api/docs/common/ref/“

These point to content in 
"/apache/openoffice-org/part2/content/api/docs/common/ref/"

Dave, I can make this update unless you are already working on it.


We had a similar discussion about that somewhere, but we should just try
that.
However this will probably add another icon to the external link (a
padlock).

I also updated two files with:

https://github.com/apache/openoffice-mwiki/commit/99a513911702113d418b06f8fa929f8b0fb251a7

Would be great if this could be activated in our Wiki installation!

I can push these two over also once I find out whether Dave or I are editing 
the php file.

Someone will need to handle the CSS change to remove the padlocks if that's 
something we want.
Or let me know what the diff needs to be :) Sorry but you don't want me writing 
CSS :P

Thanks,
Carl


mwiki/skins/aoo/dl-bg.png
mwiki/skins/aoo/main.css
mwiki/extensions/OOoIDLtags/OOoIDLtags.php

have been replaced.

Best regards,
Carl


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



Re: MediaWiki Extensions - IDL link improvement

2020-12-22 Thread Carl Marcum

Hi Dave and Matthias,

On 12/22/20 3:47 PM, Matthias Seidel wrote:

Hi Dave,

Am 22.12.20 um 19:51 schrieb Dave Fisher:

Hi -

In OOoIDLtags.php

All of the href are in the old style of 
"http://api.openoffice.org/api/docs/common/ref/“

These should be rewritten in two ways to 
“https://www.openoffice.org/api/docs/common/ref/“

These point to content in 
"/apache/openoffice-org/part2/content/api/docs/common/ref/"

Dave, I can make this update unless you are already working on it.


We had a similar discussion about that somewhere, but we should just try
that.
However this will probably add another icon to the external link (a
padlock).

I also updated two files with:

https://github.com/apache/openoffice-mwiki/commit/99a513911702113d418b06f8fa929f8b0fb251a7

Would be great if this could be activated in our Wiki installation!
I can push these two over also once I find out whether Dave or I are 
editing the php file.


Someone will need to handle the CSS change to remove the padlocks if 
that's something we want.
Or let me know what the diff needs to be :) Sorry but you don't want me 
writing CSS :P


Thanks,
Carl

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



Re: Old build Documentation

2020-12-19 Thread Carl Marcum

Hi Peter,

On 12/19/20 12:09 PM, Peter Kovacs wrote:


On 19.12.20 14:38, Carl Marcum wrote:

Hi Peter,

On 12/19/20 8:13 AM, Arrigo Marchiori wrote:

Hello Peter,

On Sat, Dec 19, 2020 at 01:30:21AM +0100, Peter Kovacs wrote:


Hello all,

do we still need the documentation description for:

https://www.openoffice.org/dev_docs/source/build_windows_pre638.html

http://www.openoffice.org/tools/dev_docs/build_windows.html

https://wiki.openoffice.org/wiki/Documentation/Building_Guide

I read quickly through them and vote for: no, please let us get rid of
them.

I mean, the first link is the first relevant result on my search 
results on

duck duck go.

And then you click through the history.

My search words are: OpenOffice windopws build

This is quite infortunate, and (still IMHO) one more reason to get rid
of those pages as quickly as possible.

Or, better, have them redirect straight to
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO so
that who clicks on the outdated links is redirected to the more up to
date documentation.

Best regards,

I hate running into old cruft on the wiki also. However..

I think it comes down to keeping thinks for historical purposes.
If we want to do that we should create an Archive. And we should then 
make shure the stuff can be build by offering all needed dependency.


We keep old sources around so my thinking is that we should somehow 
maintain a place for people to find build instructions.

We have the instruction in our Git Repository.


I do think it would help if they were more specific in exactly what 
versions they were appropriate for and have links to current pages.


These instructions don't always have to be in the form of a wiki page 
since they are historical in nature. PDF maybe?


Kind of like when I recently went looking for information on the 
mwiki IDL extension and found the page was deleted 8 years ago.
There is a difference between old information that we still need and 
out dated Information.
Maybe we could do something with Archive.org? Maybe we find people 
that would look into the stuff and create a plan how to archive this 
stuff.
I agree there is a LOT of wiki pages and other things that are either 
not relevant anymore or just outdated.

I'm not sure about depending on a third party as an archive.

I think a banner paragraph about being outdated with a link to the 
current page is one way to handle it.
A redirect would be another but hard to view it if it's actually needed 
by someone.
Maybe a combination of moving the contents to an archive area, adding 
the redirect and adding a link to the archive somewhere on the new page?


I don't think something like our database backed mwiki is the best going 
forward either if we need to migrate it or upgrade it every few years.

Plus the dev guide breaking issue we just resolved.
I'm much more in favor of a file based solution. But a migration would 
be a huge effort also unless some automation is used.


Maybe this should be a more overall project discussion on how we want to 
handle these cases.


Best regards,
Carl

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



Re: Old build Documentation

2020-12-19 Thread Carl Marcum

Hi Peter,

On 12/19/20 8:13 AM, Arrigo Marchiori wrote:

Hello Peter,

On Sat, Dec 19, 2020 at 01:30:21AM +0100, Peter Kovacs wrote:


Hello all,

do we still need the documentation description for:

https://www.openoffice.org/dev_docs/source/build_windows_pre638.html

http://www.openoffice.org/tools/dev_docs/build_windows.html

https://wiki.openoffice.org/wiki/Documentation/Building_Guide

I read quickly through them and vote for: no, please let us get rid of
them.


I mean, the first link is the first relevant result on my search results on
duck duck go.

And then you click through the history.

My search words are: OpenOffice windopws build

This is quite infortunate, and (still IMHO) one more reason to get rid
of those pages as quickly as possible.

Or, better, have them redirect straight to
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO so
that who clicks on the outdated links is redirected to the more up to
date documentation.

Best regards,

I hate running into old cruft on the wiki also. However..

I think it comes down to keeping thinks for historical purposes.

We keep old sources around so my thinking is that we should somehow 
maintain a place for people to find build instructions.


I do think it would help if they were more specific in exactly what 
versions they were appropriate for and have links to current pages.


These instructions don't always have to be in the form of a wiki page 
since they are historical in nature. PDF maybe?


Kind of like when I recently went looking for information on the mwiki 
IDL extension and found the page was deleted 8 years ago.


Best regards,
Carl

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



Re: Design Docs?

2020-12-18 Thread Carl Marcum

Hi Steve,

On 12/18/20 8:06 PM, Steve Lubbs wrote:

Hi All,

I asked this question in recruitment but this may be the proper place 
for it.


Is there any design documentation, especially related to structure 
(what are the modules, what is their function, how do they interact, 
etc.), however minimal, that you can point me to to help in wading 
through the code? I'm hoping to avoid reverse engineering the code.


If the answer to my query is available somewhere I should have seen 
it, I apologize.


Thanks in advance,

Steve Lubbs



Maybe one of the developers can point you to better information.
I have found a page for the modules here [1].
And links to specifications here [2].


[1] https://wiki.openoffice.org/wiki/Modules
[2] http://www.openoffice.org/specs/

Best regards,
Carl

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



Re: MWiki Developer Guide Blank Pages

2020-12-18 Thread Carl Marcum

Hi Dick,

On 12/18/20 11:25 AM, Dick Groskamp wrote:


On 2020/12/17 23:42:31, Carl Marcum  wrote:

Hi Dick,

On 12/17/20 12:57 PM, Dick Groskamp wrote:

On 2020/12/16 23:53:56, Carl Marcum  wrote:

Hi All,

I think I've fixed the blank pages problem in the Developer Guide.
I've spot checked through all of the spreadsheet pages that had many
broken and they all display now.

Please check any that you have reported and let me know if you find any
that are still blank.

For those interested it was in the OOoIDLtags.php extension and the
solution was pointed out by Arrigo Marchiori as a deprecated method in
new versions of PHP.

So a big thanks to Arrigo!

Thanks,
Carl

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



Just checked the odd 50 pages I worked on this week in case your solution might 
not work.

Guess what.. IT WORKS.

All pages display correct.

Thanks for the fix and your effort, also a big thanks to Rigo for pointing us 
in the right direction.

Did encounter some odd tags  and [IDL: ], but that has nothing to do 
with the solution.
I'll try to find the odd tags and fix them. For now I think all is well,,. 
. as it should be in this times.



And thanks to you for trying to do something to fix it as well.

  From what I can tell from the extension the tags are idl, idlm, idls,
idlmodule, and idltopic [1].

It looks like someone deleted a wiki page about the idl tag extension 8
years ago [2].
Although I don't know if it had any content.

It would be good to have a page about it one day :)

[1] https://github.com/apache/openoffice-mwiki/blob/main/OOoIDLtags.php
[2] http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension


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



Just put up a new page on the wiki
https://wiki.openoffice.org/wiki/MediaWiki_Extension/Extension_IDLTags#IDLTags_extension_for_Mediawiki

Feel free to adjust/add



That was fast.  Nice job and thanks for putting all that together.
I updated the one link I know about that pointed to the old missing page 
here [1].


[1] 
https://wiki.openoffice.org/wiki/Documentation/DevGuide/Contributing_to_the_Developers_Guide#IDL_extension_and_links


Thanks again,
Carl

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



Re: MWiki Developer Guide Blank Pages

2020-12-17 Thread Carl Marcum

Hi Dick,

On 12/17/20 12:57 PM, Dick Groskamp wrote:


On 2020/12/16 23:53:56, Carl Marcum  wrote:

Hi All,

I think I've fixed the blank pages problem in the Developer Guide.
I've spot checked through all of the spreadsheet pages that had many
broken and they all display now.

Please check any that you have reported and let me know if you find any
that are still blank.

For those interested it was in the OOoIDLtags.php extension and the
solution was pointed out by Arrigo Marchiori as a deprecated method in
new versions of PHP.

So a big thanks to Arrigo!

Thanks,
Carl

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



Just checked the odd 50 pages I worked on this week in case your solution might 
not work.

Guess what.. IT WORKS.

All pages display correct.

Thanks for the fix and your effort, also a big thanks to Rigo for pointing us 
in the right direction.

Did encounter some odd tags  and [IDL: ], but that has nothing to do 
with the solution.
I'll try to find the odd tags and fix them. For now I think all is well,,. 
. as it should be in this times.



And thanks to you for trying to do something to fix it as well.

From what I can tell from the extension the tags are idl, idlm, idls, 
idlmodule, and idltopic [1].


It looks like someone deleted a wiki page about the idl tag extension 8 
years ago [2].

Although I don't know if it had any content.

It would be good to have a page about it one day :)

[1] https://github.com/apache/openoffice-mwiki/blob/main/OOoIDLtags.php
[2] http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension


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



MWiki Developer Guide Blank Pages

2020-12-16 Thread Carl Marcum

Hi All,

I think I've fixed the blank pages problem in the Developer Guide.
I've spot checked through all of the spreadsheet pages that had many 
broken and they all display now.


Please check any that you have reported and let me know if you find any 
that are still blank.


For those interested it was in the OOoIDLtags.php extension and the 
solution was pointed out by Arrigo Marchiori as a deprecated method in 
new versions of PHP.


So a big thanks to Arrigo!

Thanks,
Carl

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



Re: Beanshell

2020-12-16 Thread Carl Marcum

That's great Jim!

On 12/16/20 11:13 AM, Jim Jagielski wrote:

Just a FYI: I have been invited to the official BeanShell team and so it is 
likely that my fork will be folded back into beanshell.org as the v2.x version 
while we work on the v3.x version in parallel.

Right now I have a 2.2.0b1 release and I'm looking into seeing how far we can 
take it.


On Dec 15, 2020, at 8:38 AM, Jim Jagielski  wrote:

Just a FYI:

https://twitter.com/jimjag/status/1338840166828568576

TL;DR: I've forked beanshell and beanshell2 into something which maybe we can 
baseline for AOO
-
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: issue with dmake clean

2020-12-15 Thread Carl Marcum




On 12/15/20 3:37 PM, Peter Kovacs wrote:


On 15.12.20 20:14, Jim Jagielski wrote:


On Dec 15, 2020, at 12:57 PM, Matthias Seidel 
 wrote:


Hi Carl,

Am 13.12.20 um 23:43 schrieb Carl Marcum:

Hi Matthias,

On 12/13/20 4:29 PM, Matthias Seidel wrote:

Hi Carl,

Am 13.12.20 um 19:02 schrieb Carl Marcum:

Hi all,

Just ran into something.

I ran 'dmake clean' from main probably without having ran source
 and it removed all of my directories under main.
Tried to do that on Windows (Cygwin64), went into main, did 
"autoconf",

"dmake clean":

$ dmake clean
-bash: dmake: command not found

Only after "source winenv.set.sh" it did clean up what it should...

It could be because I have a built and installed dmake on my system.

Thanks for checking!
If an installed dmake does have this consequence we should have a 
closer

look at it...

It must be getting those commands from a makefile somewhere though... 
dmake itself has no concept of 'clean' independent of what a makefile 
tells it it is AFAIK


there is a makefile on that level. However I think it is for make and 
not for dmake. At least when I want to reset the build for sure I do a 
dmake clean (from instsetoo_native)first, followed by a make clean 
(main).


And the make clean has this rm command and removes all sorts of stuff. 
Could it be that if you execute dmake clean on main folder will let 
dmake read the make file ment for gnumake?


In total I do not have a high confidence in general in our build 
system. It is complicated and complex. And if some things do not fit 
it will do unexpected things.




It could very well be the result of me using the same session for many 
builds and switching back and forth between branches in the same 
terminal session.


I've had it happen twice now and it's a pain when it happens but 
probably not dmake's fault.


I'll see if I can recreate it in a consistent way and report back.

Thanks,
Carl

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



Re: issue with dmake clean

2020-12-13 Thread Carl Marcum

Hi Matthias,

On 12/13/20 4:29 PM, Matthias Seidel wrote:

Hi Carl,

Am 13.12.20 um 19:02 schrieb Carl Marcum:

Hi all,

Just ran into something.

I ran 'dmake clean' from main probably without having ran source
 and it removed all of my directories under main.

Tried to do that on Windows (Cygwin64), went into main, did "autoconf",
"dmake clean":

$ dmake clean
-bash: dmake: command not found

Only after "source winenv.set.sh" it did clean up what it should...

It could be because I have a built and installed dmake on my system.

Thanks for checking!



Regards,

    Matthias


Looks like it ran 'rm -rf */'

Best regards,
Carl

-
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



issue with dmake clean

2020-12-13 Thread Carl Marcum

Hi all,

Just ran into something.

I ran 'dmake clean' from main probably without having ran source 
 and it removed all of my directories under main.


Looks like it ran 'rm -rf */'

Best regards,
Carl

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



Re: [openoffice-mwiki-ext] branch master created (now 61af533)

2020-12-12 Thread Carl Marcum

Hi Matthias,

On 12/12/20 11:44 AM, Matthias Seidel wrote:

Hi Carl,

Am 12.12.20 um 17:40 schrieb Carl Marcum:

Hi Matthias,

On 12/12/20 10:49 AM, Matthias Seidel wrote:

And now we have a branch "master"...

Anyone who can rename it to main?!

Do you mean trunk?

I would have loved "trunk" but GitHub now defaults to main. Somehow ASF
Infra still creates repos with "master".

Our repos for both homepages were already changed to "main"...


I hadn't noticed that change.

Thanks,
Carl



Regards,

    Matthias


Regards,

     Matthias

Am 12.12.20 um 16:41 schrieb di...@apache.org:

This is an automated email from the ASF dual-hosted git repository.

digro pushed a change to branch master
in repository
https://gitbox.apache.org/repos/asf/openoffice-mwiki-ext.git.


    at 61af533  Added original extension IDLTags to repo

This branch includes the following new commits:

   new 61af533  Added original extension IDLTags to repo

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.




-
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-mwiki-ext] branch master created (now 61af533)

2020-12-12 Thread Carl Marcum

Hi Matthias,

On 12/12/20 10:49 AM, Matthias Seidel wrote:

And now we have a branch "master"...

Anyone who can rename it to main?!


Do you mean trunk?



Regards,

    Matthias

Am 12.12.20 um 16:41 schrieb di...@apache.org:

This is an automated email from the ASF dual-hosted git repository.

digro pushed a change to branch master
in repository https://gitbox.apache.org/repos/asf/openoffice-mwiki-ext.git.


   at 61af533  Added original extension IDLTags to repo

This branch includes the following new commits:

  new 61af533  Added original extension IDLTags to repo

The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails.  The revisions
listed as "add" were already present in the repository and have only
been added to this reference.





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



  1   2   3   4   5   >