Re: Question ad Groovy implementation (Re: Beanshell Scripting

[Carl Marcum]

Hi Rony,

On 7/14/20 10:11 AM, Rony G. Flatscher wrote:

Hi Carl,

On 13.07.2020 22:07, Carl Marcum wrote:
... cut ...


Currently my Groovy macro is a standalone extension.

We can discuss later after I announce it's information whether it could be 
added to the office at
some point or left as a soon-to-be-popular extension ;)

Could you briefly explain what your extension does (e.g. generically allowing 
the implementation of
UNO classes/components in Groovy)?

---rony

P.S.: AFAIK Groovy uses Apache BSF. If so it may be helpful to look at the 
ooRexx ScriptProvider
implementation (which uses Apache BSF and which is based on the BeanShell 
implementation of the
ScriptProvider) in case you have not yet implemented the ScriptProvider part 
for Groovy.




I'm planning a more formal announcement as soon as I finish the Readme's 
for a couple of these but...


There are a few inter-dependent projects.

The Groovy UNO Extension [1] extends the Java UNO API's with convenience 
methods for Groovy Extensions and Client apps.

It's documentation is here [2].
It uses Groovy's Extension mechanism to extend the UNO API's.

The OpenOffice-Groovy [3] is the OpenOffice extension to add Groovy to 
the scripting framework. It is heavily influenced by the built-in Beanshell.

I'm using Groovy's GroovyShell to evaluate the script [4].
It includes the Groovy UNO Extension.
You can get it on Bintray here [5].

The third project is OpenOffice-Groovy-Macros [6] an extension to add a 
lot of the sample macros included in AOO rewritten in Groovy.
Probably more useful copy-paste from github since you can't edit these 
from the extension like you can with the built-in macros.

You can get it on Bintray here [7].

I plan to add them to the Extension site after I get some more testing done.

I'm also working on an Extension project generator similar to the 
NetBeans plugin but IDE independent.

Not ready to show that one yet.

I have copies of the 4.1.6 UNO jars for use by Maven, Gradle and Groovy 
scripts in Bintray [8].


Please let me know if you have any questions.

Best regards,
Carl


[1] https://github.com/cbmarcum/guno-extension
[2] https://cbmarcum.github.io/guno-extension/
[3] https://github.com/cbmarcum/openoffice-groovy
[4] http://www.groovy-lang.org/integrating.html#integ-groovyshell
[5] 
https://bintray.com/cmarcum/openoffice-extensions/openoffice-groovy#files

[6] https://github.com/cbmarcum/openoffice-groovy-macros
[7] 
https://bintray.com/cmarcum/openoffice-extensions/openoffice-groovy-macros#files

[8] https://bintray.com/cmarcum/maven


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

Re: 32bits-64bits après migration MacOs Catalina

[B. Ruth Deerfield]

Alors, que dois-je faire avec tous mes documents des dix dernières années?  
Sont-ils totalement irrécupérables?  J'ai 500 pages de mes mémoires et trois 
livres partiellement écrits. Alors, que dois-je faire avec tous mes documents 
des dix dernières années?  Sont-ils totalement irrécupérables?  J'ai 500 pages 
de mes mémoires et trois livres partiellement écrits. 

PostScript

Je n'ai pas pu mettre à jour votre dernière mise à jour, donc j'utilise 
toujours le programme Open Office précédent.  Je vous ai écrit sur mes 
difficultés qui n'ont jamais été résolues donc tout est dans la précédente 
version d'Open Office.  J'ai essayé de convertir l'un des livres que j'ai 
écrits en pages avec succès, mais tout le reste est toujours dans votre 
dernière version d'Open Office.  Bien sûr, tout est écrit en anglais, pas en 
français.


Sent from my iPhone

> On Jul 4, 2020, at 5:38 PM, B. Ruth Deerfield  wrote:
> 
> Alors, que dois-je faire avec tous mes documents des dix dernières années?  
> Sont-ils totalement irrécupérables?  J'ai 500 pages de mes mémoires et trois 
> livres partiellement écrits.
> 
> Sent from my iPhone
> 
 On May 29, 2020, at 6:32 AM, Pedro Lino  wrote:
>> Cher Olivier
>>> J’ai contacté Apple, il semble que mon ordi, suite à la dernière mise à jour
>>> est passé de 32bits à 64bits.
>>> De fait le logiciel Open Office installé n’est plus compatible.
>>> Pouvez vous m’aider à installer la version Open Office compatible
>>> sans perdre tous les documents créés précédemment ?
>> Il n'y a aucun risque pour vôtres documents.
>> Il faut seulement faire une mise à jour do logiciel OpenOffice à la version 
>> 4.1.7 64bits
>> https://sourceforge.net/projects/openofficeorg.mirror/files/4.1.7/binaries/fr/Apache_OpenOffice_4.1.7_MacOS_x86-64_install_fr.dmg/download
>> Si vous avez plusieurs de questions, envoyez les seulement pour 
>> users...@openoffice.apache.org mailto:users...@openoffice.apache.org ou a 
>> mon e-mail personnel
>> (Le français est ma langue tertiaire alors je m'excuse pour les erreurs)
>> Cordialement.
>> Pedro

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

OS/2 (Re: Question ad MacOS 4.2 Developer Build

[Rony G. Flatscher]

Hi Matthias,

On 14.07.2020 16:48, Matthias Seidel wrote:
> Hi Rony,
>
> Am 14.07.20 um 16:34 schrieb Rony G. Flatscher:
>> Hi Matthias,
>>
>> On 14.07.2020 16:14, Matthias Seidel wrote:
>>> Am 14.07.20 um 16:03 schrieb Rony G. Flatscher:
 Hi there,

 yesterday I intended to test the ooRexx macro language oxt file against 
 the MacOS Developer Build
 (4.2) to test whether  
 is fixed.

 As the install script that has been working for more than 10 years on OO 
 (and LO) failed I looked
 into the cause and saw that the "soffice" (and "unoinfo") executable now 
 resides in
 "/Applications/OpenOffice Developer Build.app/Contents/*MacOS*/soffice" 
 whereas it used to be
 located in "/Applications/OpenOffice.app/Contents/*program*/soffice".
>>> As it is a Developer Build the PRODUCTNAME is "OpenOffice Developer Build"
>>> I am pretty sure that your script works as expected with a "normal" build.
>> Yes, this is o.k. (not the problem).
>>
>> The problem is that in the "Contents" directory there is no "program" 
>> subdirectory in the developer
>> build, rather it is named "MacOS" instead.
> I realized that now (see my other mail)
>> The installation script assumes on the Mac that "soffice" and "unoinfo" are 
>> located in
>> "/Applications/OpenOffice[ Developer Build].app/Contents/program". (If this 
>> is intentional I would
>> change the script accordingly.)
> I don't think that was intentional. Let's wait for a "normal" build.
>>> Maybe there is a possibility to get the script recognize the difference?
>>> (the same would apply to a Beta Build)
>>>
>>> @Jim: Could you provide some plain mac builds?
>>>
>>> BTW: I always wanted to test your ooRexx extension, Rexx was my first 
>>> "language" on OS/2.
>> You would be surprised! ;-)
>>
>> Actually "Object-oriented Rexx" was created as an object-oriented 
>> replacement of "Rexx" for OS/2
>> Warp by IBM. The Windows version generated quite some income for IBM when 
>> their user base switched
>> from OS/2 to Windows and learned that there were tons of Rexx programs that 
>> also needed to run on
>> Windows.
>>
>> Later IBM handed the source code over to the non-profit SIG "Rexx Language 
>> Association" which then
>> released an open-source version of it under the name "Open Object Rexx" 
>> (ooRexx) in 2005. Ever since
>> then it got steadily improved and the current 5.0 (officially in beta but in 
>> release quality)
>> release is imminent.
>>
>> The OpenOffice plugin of ooRexx was created using the Java-bridge 
>> "BSF4ooRexx" (Apache BSF and
>> ooRexx), which also has its roots in OS/2 believe it or not: Java played an 
>> important role for OS/2
>> and portable (even GUI) applications became possible with the Java bridge 
>> such that Rexx programs
>> developed under OS/2 ran unchanged on Windows (and vice versa).
>>
>> Today the Java bridge BSF4ooRexx is bi-directionally complete, i.e. Java 
>> classes and Java objects
>> are camouflaged as ooRexx classes and objects, sending them ooRexx messages. 
>> On the other hand Java
>> code can invoke ooRexx methods without realizing that the implementation is 
>> done in ooRexx (e.g.
>> when extending Java classes in ooRexx or implementing abstract Java methods 
>> in ooRexx).
>>
>> Like with Rexx ooRexx is a dynamically typed, interpreted language with a 
>> "human-centric" syntax,
>> such that it can be learned quite fast and programs can be understood quite 
>> easily.
>>
>> So, if you have interest and a little bit of time, it may be very worthwhile 
>> to look into it.
>> Creating ooRexx-macros and/or using OpenOffice from ooRexx programs is 
>> straight-forward and quite easy.
> If I only had the time (and knowledge)... ;-)
>
> But in fact I still use OS/2 (ArcaOS in VirtualBox) with AOO installed.

That is remarkable and great indeed!

---rony



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

Re: Question ad MacOS 4.2 Developer Build

[Rony G. Flatscher]

One more problem, observation: while running "unopkg" I experience the 
following error:

e:\DropBox\Dropbox\xfer\mac>type problem.txt
wu114217:Resources rony$ "/Applications/OpenOffice Developer 
Build.app/Contents/MacOS/unopkg" add -f --shared /Library/Frameworks/BSF4o
oRexx.framework/Libraries/ScriptProviderForooRexx.oxt
dyld: Library not loaded: @___URELIB/libuno_cppu.dylib
  Referenced from: /Applications/OpenOffice Developer 
Build.app/Contents/MacOS/uno.bin
  Reason: image not found

^Cwu114217:Resources ronysudo "/Applications/OpenOffice Developer 
Build.app/Contents/MacOS/unopkg" add -f --shared /Library/Frameworks/
BSF4ooRexx.framework/Libraries/ScriptProviderForooRexx.oxt
dyld: Library not loaded: @___URELIB/libuno_cppu.dylib
  Referenced from: /Applications/OpenOffice Developer 
Build.app/Contents/MacOS/uno.bin
  Reason: image not found

The version of AOO 2.0 developer build for MacOSX was downloaded yesterday from 
Jim's site:


---rony


On 14.07.2020 16:03, Rony G. Flatscher wrote:
> Hi there,
>
> yesterday I intended to test the ooRexx macro language oxt file against the 
> MacOS Developer Build
> (4.2) to test whether  is 
> fixed.
>
> As the install script that has been working for more than 10 years on OO (and 
> LO) failed I looked
> into the cause and saw that the "soffice" (and "unoinfo") executable now 
> resides in
> "/Applications/OpenOffice Developer Build.app/Contents/*MacOS*/soffice" 
> whereas it used to be
> located in "/Applications/OpenOffice.app/Contents/*program*/soffice".
>
> Is this an oversight/bug or has the directory structure been changed (and if 
> so on all platforms)?
>
> ---rony
>

Re: Question ad MacOS 4.2 Developer Build

[Matthias Seidel]

Hi Rony,

Am 14.07.20 um 16:34 schrieb Rony G. Flatscher:
> Hi Matthias,
>
> On 14.07.2020 16:14, Matthias Seidel wrote:
>> Am 14.07.20 um 16:03 schrieb Rony G. Flatscher:
>>> Hi there,
>>>
>>> yesterday I intended to test the ooRexx macro language oxt file against the 
>>> MacOS Developer Build
>>> (4.2) to test whether  is 
>>> fixed.
>>>
>>> As the install script that has been working for more than 10 years on OO 
>>> (and LO) failed I looked
>>> into the cause and saw that the "soffice" (and "unoinfo") executable now 
>>> resides in
>>> "/Applications/OpenOffice Developer Build.app/Contents/*MacOS*/soffice" 
>>> whereas it used to be
>>> located in "/Applications/OpenOffice.app/Contents/*program*/soffice".
>> As it is a Developer Build the PRODUCTNAME is "OpenOffice Developer Build"
>> I am pretty sure that your script works as expected with a "normal" build.
> Yes, this is o.k. (not the problem).
>
> The problem is that in the "Contents" directory there is no "program" 
> subdirectory in the developer
> build, rather it is named "MacOS" instead.
I realized that now (see my other mail)
>
> The installation script assumes on the Mac that "soffice" and "unoinfo" are 
> located in
> "/Applications/OpenOffice[ Developer Build].app/Contents/program". (If this 
> is intentional I would
> change the script accordingly.)
I don't think that was intentional. Let's wait for a "normal" build.
>
>> Maybe there is a possibility to get the script recognize the difference?
>> (the same would apply to a Beta Build)
>>
>> @Jim: Could you provide some plain mac builds?
>>
>> BTW: I always wanted to test your ooRexx extension, Rexx was my first 
>> "language" on OS/2.
> You would be surprised! ;-)
>
> Actually "Object-oriented Rexx" was created as an object-oriented replacement 
> of "Rexx" for OS/2
> Warp by IBM. The Windows version generated quite some income for IBM when 
> their user base switched
> from OS/2 to Windows and learned that there were tons of Rexx programs that 
> also needed to run on
> Windows.
>
> Later IBM handed the source code over to the non-profit SIG "Rexx Language 
> Association" which then
> released an open-source version of it under the name "Open Object Rexx" 
> (ooRexx) in 2005. Ever since
> then it got steadily improved and the current 5.0 (officially in beta but in 
> release quality)
> release is imminent.
>
> The OpenOffice plugin of ooRexx was created using the Java-bridge 
> "BSF4ooRexx" (Apache BSF and
> ooRexx), which also has its roots in OS/2 believe it or not: Java played an 
> important role for OS/2
> and portable (even GUI) applications became possible with the Java bridge 
> such that Rexx programs
> developed under OS/2 ran unchanged on Windows (and vice versa).
>
> Today the Java bridge BSF4ooRexx is bi-directionally complete, i.e. Java 
> classes and Java objects
> are camouflaged as ooRexx classes and objects, sending them ooRexx messages. 
> On the other hand Java
> code can invoke ooRexx methods without realizing that the implementation is 
> done in ooRexx (e.g.
> when extending Java classes in ooRexx or implementing abstract Java methods 
> in ooRexx).
>
> Like with Rexx ooRexx is a dynamically typed, interpreted language with a 
> "human-centric" syntax,
> such that it can be learned quite fast and programs can be understood quite 
> easily.
>
> So, if you have interest and a little bit of time, it may be very worthwhile 
> to look into it.
> Creating ooRexx-macros and/or using OpenOffice from ooRexx programs is 
> straight-forward and quite easy.

If I only had the time (and knowledge)... ;-)

But in fact I still use OS/2 (ArcaOS in VirtualBox) with AOO installed.

Regards,

   Matthias

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



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Question ad MacOS 4.2 Developer Build

[Rony G. Flatscher]

Hi Matthias,

On 14.07.2020 16:14, Matthias Seidel wrote:
> Am 14.07.20 um 16:03 schrieb Rony G. Flatscher:
>> Hi there,
>>
>> yesterday I intended to test the ooRexx macro language oxt file against the 
>> MacOS Developer Build
>> (4.2) to test whether  is 
>> fixed.
>>
>> As the install script that has been working for more than 10 years on OO 
>> (and LO) failed I looked
>> into the cause and saw that the "soffice" (and "unoinfo") executable now 
>> resides in
>> "/Applications/OpenOffice Developer Build.app/Contents/*MacOS*/soffice" 
>> whereas it used to be
>> located in "/Applications/OpenOffice.app/Contents/*program*/soffice".
> As it is a Developer Build the PRODUCTNAME is "OpenOffice Developer Build"
> I am pretty sure that your script works as expected with a "normal" build.

Yes, this is o.k. (not the problem).

The problem is that in the "Contents" directory there is no "program" 
subdirectory in the developer
build, rather it is named "MacOS" instead.

The installation script assumes on the Mac that "soffice" and "unoinfo" are 
located in
"/Applications/OpenOffice[ Developer Build].app/Contents/program". (If this is 
intentional I would
change the script accordingly.)

> Maybe there is a possibility to get the script recognize the difference?
> (the same would apply to a Beta Build)
>
> @Jim: Could you provide some plain mac builds?
>
> BTW: I always wanted to test your ooRexx extension, Rexx was my first 
> "language" on OS/2.

You would be surprised! ;-)

Actually "Object-oriented Rexx" was created as an object-oriented replacement 
of "Rexx" for OS/2
Warp by IBM. The Windows version generated quite some income for IBM when their 
user base switched
from OS/2 to Windows and learned that there were tons of Rexx programs that 
also needed to run on
Windows.

Later IBM handed the source code over to the non-profit SIG "Rexx Language 
Association" which then
released an open-source version of it under the name "Open Object Rexx" 
(ooRexx) in 2005. Ever since
then it got steadily improved and the current 5.0 (officially in beta but in 
release quality)
release is imminent.

The OpenOffice plugin of ooRexx was created using the Java-bridge "BSF4ooRexx" 
(Apache BSF and
ooRexx), which also has its roots in OS/2 believe it or not: Java played an 
important role for OS/2
and portable (even GUI) applications became possible with the Java bridge such 
that Rexx programs
developed under OS/2 ran unchanged on Windows (and vice versa).

Today the Java bridge BSF4ooRexx is bi-directionally complete, i.e. Java 
classes and Java objects
are camouflaged as ooRexx classes and objects, sending them ooRexx messages. On 
the other hand Java
code can invoke ooRexx methods without realizing that the implementation is 
done in ooRexx (e.g.
when extending Java classes in ooRexx or implementing abstract Java methods in 
ooRexx).

Like with Rexx ooRexx is a dynamically typed, interpreted language with a 
"human-centric" syntax,
such that it can be learned quite fast and programs can be understood quite 
easily.

So, if you have interest and a little bit of time, it may be very worthwhile to 
look into it.
Creating ooRexx-macros and/or using OpenOffice from ooRexx programs is 
straight-forward and quite easy.

---rony



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

Re: Question ad MacOS 4.2 Developer Build

[Matthias Seidel]

Hi again,

Am 14.07.20 um 16:14 schrieb Matthias Seidel:
> Hi Rony,
>
> Am 14.07.20 um 16:03 schrieb Rony G. Flatscher:
>> Hi there,
>>
>> yesterday I intended to test the ooRexx macro language oxt file against the 
>> MacOS Developer Build
>> (4.2) to test whether  is 
>> fixed.
>>
>> As the install script that has been working for more than 10 years on OO 
>> (and LO) failed I looked
>> into the cause and saw that the "soffice" (and "unoinfo") executable now 
>> resides in
>> "/Applications/OpenOffice Developer Build.app/Contents/*MacOS*/soffice" 
>> whereas it used to be
>> located in "/Applications/OpenOffice.app/Contents/*program*/soffice".
> As it is a Developer Build the PRODUCTNAME is "OpenOffice Developer Build"
> I am pretty sure that your script works as expected with a "normal" build.

Oh, I realize now that the differnce is between *MacOS* and *program*...

Of course that shouldn't be.

Regards,

   Matthias

>
> Maybe there is a possibility to get the script recognize the difference?
> (the same would apply to a Beta Build)
>
> @Jim: Could you provide some plain mac builds?
>
> BTW: I always wanted to test your ooRexx extension, Rexx was my first
> "language" on OS/2.
>
> Regards,
>
>    Matthias
>
>> Is this an oversight/bug or has the directory structure been changed (and if 
>> so on all platforms)?
>>
>> ---rony
>>
>>



smime.p7s
Description: S/MIME Cryptographic Signature

Re: Question ad MacOS 4.2 Developer Build

[Matthias Seidel]

Hi Rony,

Am 14.07.20 um 16:03 schrieb Rony G. Flatscher:
> Hi there,
>
> yesterday I intended to test the ooRexx macro language oxt file against the 
> MacOS Developer Build
> (4.2) to test whether  is 
> fixed.
>
> As the install script that has been working for more than 10 years on OO (and 
> LO) failed I looked
> into the cause and saw that the "soffice" (and "unoinfo") executable now 
> resides in
> "/Applications/OpenOffice Developer Build.app/Contents/*MacOS*/soffice" 
> whereas it used to be
> located in "/Applications/OpenOffice.app/Contents/*program*/soffice".

As it is a Developer Build the PRODUCTNAME is "OpenOffice Developer Build"
I am pretty sure that your script works as expected with a "normal" build.

Maybe there is a possibility to get the script recognize the difference?
(the same would apply to a Beta Build)

@Jim: Could you provide some plain mac builds?

BTW: I always wanted to test your ooRexx extension, Rexx was my first
"language" on OS/2.

Regards,

   Matthias

>
> Is this an oversight/bug or has the directory structure been changed (and if 
> so on all platforms)?
>
> ---rony
>
>



smime.p7s
Description: S/MIME Cryptographic Signature

Question ad Groovy implementation (Re: Beanshell Scripting

[Rony G. Flatscher]

Hi Carl,

On 13.07.2020 22:07, Carl Marcum wrote:
... cut ...

> Currently my Groovy macro is a standalone extension.
>
> We can discuss later after I announce it's information whether it could be 
> added to the office at
> some point or left as a soon-to-be-popular extension ;)

Could you briefly explain what your extension does (e.g. generically allowing 
the implementation of
UNO classes/components in Groovy)?

---rony

P.S.: AFAIK Groovy uses Apache BSF. If so it may be helpful to look at the 
ooRexx ScriptProvider
implementation (which uses Apache BSF and which is based on the BeanShell 
implementation of the
ScriptProvider) in case you have not yet implemented the ScriptProvider part 
for Groovy.



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

Question ad MacOS 4.2 Developer Build

[Rony G. Flatscher]

Hi there,

yesterday I intended to test the ooRexx macro language oxt file against the 
MacOS Developer Build
(4.2) to test whether  is 
fixed.

As the install script that has been working for more than 10 years on OO (and 
LO) failed I looked
into the cause and saw that the "soffice" (and "unoinfo") executable now 
resides in
"/Applications/OpenOffice Developer Build.app/Contents/*MacOS*/soffice" whereas 
it used to be
located in "/Applications/OpenOffice.app/Contents/*program*/soffice".

Is this an oversight/bug or has the directory structure been changed (and if so 
on all platforms)?

---rony

[GitHub] [openoffice] Pilot-Pirx commented on pull request #90: Possible patch for Bugzilla Issue 128395

[GitBox]

Pilot-Pirx commented on pull request #90:
URL: https://github.com/apache/openoffice/pull/90#issuecomment-658122082


   OK, we need some additional logic to exclude Help pages in that list...
   See: https://bz.apache.org/ooo/show_bug.cgi?id=5



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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

[GitHub] [openoffice] Pilot-Pirx opened a new pull request #90: Possible patch for Bugzilla Issue 128395

[GitBox]

Pilot-Pirx opened a new pull request #90:
URL: https://github.com/apache/openoffice/pull/90


   See: https://bz.apache.org/ooo/show_bug.cgi?id=128395
   
   I took over the logic from 
https://github.com/apache/openoffice/blob/trunk/main/sw/source/ui/utlui/navipi.cxx#L1217
   
   But since I am not a coder, I am not sure if that is enough. A test build on 
Windows was successful and did show the (inactive) entries.



This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org



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