date:20201211

Hi Carl,

Am 12.12.20 um 00:30 schrieb Carl Marcum:
> So the file is owned by Andrea and I can't edit it.
>
> I have posted the update and the file location to sysadmin@ list
> because someone needs sudo to write to it which I don't have ;)
> Can someone grant me sudo or update the file?

I asked for access a long time ago... I still have 3 updated graphics
for the Wiki.

I could commit them to our new mwiki repo, but there is no branch at the
moment.

Regards,

   Matthias

>
> Thanks,
> Carl
>
> On 12/11/20 5:37 PM, Carl Marcum wrote:
>> It's been awhile since I've done any PHP so I've been doing some
>> testing in an online PHP Sandbox [1].
>>
>> [1] https://sandbox.onlinephpfunctions.com/
>>
>> See below:
>>
>> On 12/11/20 3:30 PM, Dave Fisher wrote:
>>>
>>> Sent from my iPhone
>>>
 On Dec 11, 2020, at 11:46 AM, Dick Groskamp  wrote:

 

> On 2020/12/11 19:34:47, Matthias Seidel
>  wrote:
> Hi Dick,
>
>> Am 11.12.20 um 20:29 schrieb Dick Groskamp:
>>
>> On 2020/12/11 17:23:20, Matthias Seidel
>>  wrote:
>>> Hi Dick,
>>>
>>> Am 11.12.20 um 17:14 schrieb Dick Groskamp:
>>>
>>> The extension is not broken, it is outdated. It cannot be updated
>>> because that would need a newer version of Wiki.
>>> However, our AOO skin for the Wiki must be adapted to the newer
>>> Wiki
>>> version...
>>>
>>> At least that is what I understood from Andrea's posts regarding
>>> the
>>> Wiki server in 2019 [1]
>>>
>> Well, if it is outdated and it doesn't do its job, I think it is
>> broken.
>> What I meant to say is that it doesn't work the way it was
>> designed anymore.
>>> See above, the extension is not ours. It is from mediaWiki.org (?)
>>>
>> Well, I think it is ours. It was especially created by former
>> developers for this purpose and it is probably nowhere else
>> available/usable and just works on our wiki.
> Who would that developer be?! Do you know a name?
 It was somewhere up in this thread:
 // Extension credits that will show up on Special:Version
 $wgExtensionCredits['parserhook'][] = array(
  'name' => 'IDL Tags',
  'version' => '1.0.2',
  'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
>>> This clearly an OOo extension.
>>>
>>> Clayton didn’t really join AOO and Terry did the Forum move but
>>> seemed to get frustrated and left.
>>>
>>> I think that the approach could be separate from Carl’s new Wiki VM
>>> effort.
>>>
>>> Someone will need to look at the current VM and try your idea about
>>> changing the function.
>>>
>>> If Andrea can’t then I’ll have a look early next week.
>>>
>>> Regards,
>>> Dave
>>>
 'description' => 'Manage the IDL links in the OOo Dev Guide ',
  'url' =>
 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
 );
> Isn't it more likely that it is a mediawiki extension like:
>
> https://www.mediawiki.org/wiki/Extension:SyntaxHighlight
>
 That is probably where the confusion comes from. You can develop
 your own extensions if you want, just like our own .oxt's. The
 whole IDLTags extension is the PHP-page Carl copied from the
 configuration. That's all
>> I haven't read Andrea's post yet, I focused more on getting this
>> defective extension IDLTags repaired.
> Well, that would be a workaround for the moment, but we should
> "simply"
> fix the source of the problem...
>
 With "source of the problem" I assume you mean upgrading the wiki
 version and updating the skin
 etc as mentioned in Andrea's post

 As far as I know has Carl a new updated VM  available to go along
 with that, but he has a tiny
 problem getting access. I think that will be the next step.


>>
>> I think Arrigo's finding about the deprecated method may be it.
>>
>> I have commented out the old method call and folled with the
>> replacement.
>> Testing a string that might be used in  tag:
>> > $input = 'com.sun.star.uno.XComponentContext:getServiceManager';
>> print("input = $input \n");
>>
>> // $page = ereg_replace('\.','/',$input);
>> $page = preg_replace('/\./','/',$input);
>> print("page = $page \n");
>>
>> // $anchor = ereg_replace (':','.html#',$page);
>> $anchor = preg_replace ('/:/','.html#',$page);
>> print("anchor = $anchor \n");
>>
>> // $function = ereg_replace ('^.*:','',$page);
>> $function = preg_replace ('/^.*:/','',$page);
>> print("function = $function \n");
>>
>> $output = 'http://api.openoffice.org/docs/common/ref/' .
>> $anchor.'" class="external text">' . $function.'';
>> print("output = $output \n");
>> ?>
>>
>> which outputs:
>> input = com.sun.star.uno.XComponentContext:getServiceManager
>> page = com/sun/star/uno/XComponentContext:getServiceManager
>> anchor = com/sun/star/uno/XComponentContext.html#getServiceManager
>> function = getServiceManager
>> output = > href="http://ap

Re: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

2020-12-11 Thread Carl Marcum

So the file is owned by Andrea and I can't edit it.

I have posted the update and the file location to sysadmin@ list because
someone needs sudo to write to it which I don't have ;)

Can someone grant me sudo or update the file?

Thanks,
Carl

On 12/11/20 5:37 PM, Carl Marcum wrote:
It's been awhile since I've done any PHP so I've been doing some
testing in an online PHP Sandbox [1].

[1] https://sandbox.onlinephpfunctions.com/

See below:

On 12/11/20 3:30 PM, Dave Fisher wrote:

Sent from my iPhone

On Dec 11, 2020, at 11:46 AM, Dick Groskamp wrote:

On 2020/12/11 19:34:47, Matthias Seidel
wrote:

Hi Dick,

Am 11.12.20 um 20:29 schrieb Dick Groskamp:

On 2020/12/11 17:23:20, Matthias Seidel
wrote:

Hi Dick,

Am 11.12.20 um 17:14 schrieb Dick Groskamp:

The extension is not broken, it is outdated. It cannot be updated
because that would need a newer version of Wiki.
However, our AOO skin for the Wiki must be adapted to the newer Wiki
version...

At least that is what I understood from Andrea's posts regarding the
Wiki server in 2019 [1]

Well, if it is outdated and it doesn't do its job, I think it is
broken.
What I meant to say is that it doesn't work the way it was
designed anymore.

See above, the extension is not ours. It is from mediaWiki.org (?)

Well, I think it is ours. It was especially created by former
developers for this purpose and it is probably nowhere else
available/usable and just works on our wiki.

Who would that developer be?! Do you know a name?

This clearly an OOo extension.

Clayton didn’t really join AOO and Terry did the Forum move but
seemed to get frustrated and left.

I think that the approach could be separate from Carl’s new Wiki VM
effort.

Someone will need to look at the current VM and try your idea about
changing the function.

If Andrea can’t then I’ll have a look early next week.

Regards,
Dave

'description' => 'Manage the IDL links in the OOo Dev Guide ',
'url' =>
'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
);

Isn't it more likely that it is a mediawiki extension like:

https://www.mediawiki.org/wiki/Extension:SyntaxHighlight

That is probably where the confusion comes from. You can develop
your own extensions if you want, just like our own .oxt's. The whole
IDLTags extension is the PHP-page Carl copied from the
configuration. That's all
I haven't read Andrea's post yet, I focused more on getting this
defective extension IDLTags repaired.
Well, that would be a workaround for the moment, but we should
"simply"

fix the source of the problem...

With "source of the problem" I assume you mean upgrading the wiki
version and updating the skin

etc as mentioned in Andrea's post

As far as I know has Carl a new updated VM available to go along
with that, but he has a tiny

problem getting access. I think that will be the next step.

I think Arrigo's finding about the deprecated method may be it.

I have commented out the old method call and folled with the replacement.
Testing a string that might be used in tag:
$output = 'http://api.openoffice.org/docs/common/ref/' .
$anchor.'" class="external text">' . $function.'';

print("output = $output \n");
?>

which outputs:
input = com.sun.star.uno.XComponentContext:getServiceManager
page = com/sun/star/uno/XComponentContext:getServiceManager
anchor = com/sun/star/uno/XComponentContext.html#getServiceManager
function = getServiceManager
output = href="http://api.openoffice.org/docs/common/ref/com/sun/star/uno/XComponentContext.html#getServiceManager";
class="external text">getServiceManager

which I think is a correct link.

I can take a shot at the production fix unless someone has concerns.

Best regards,
Carl

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

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

2020-12-11 Thread Keith N. McKenna

On 12/11/2020 10:01 AM, Matthias Seidel wrote:
> Hi Peter,
> 
> I am not sure what you are talking about here...
> 
> The discussion is about a non working extension for our Wiki server.
> 
> The repository is for our Media Wiki extension?
> 
> 2 totally different things...
> 
> Matthias

Matthias;

The repository Peter created is for custom MediaWiki extensions that
were created specifically for our mwiki. The one in particular is the
one raising havoc with many pages in the development section of the
mwiki were multiple pages will not open because some instructions were
deprecated.

Regards
Keith

> Am 11.12.20 um 12:22 schrieb Peter Kovacs:
>> I have created the Repository for MWiki extensions with my Proposed name:
>>
>> openoffice-mwiki-ext.git
>> 
>>
>> It is ready to add our MWiki extensions.
>>
>>
>> On 10.12.20 20:35, Keith N. McKenna wrote:
>>> On 12/9/2020 5:38 PM, Marcus wrote:
 Am 09.12.20 um 18:35 schrieb Peter Kovacs:
> How about we create a OpenOffice-Mwiki-ext Repo in gitbox?
>
> We could do the same for the forums customizations.
>
> So we have more control over our support code.
 +1
 This increases the chance that also others can have a look and give
 some
 hints when problems arise.

 Marcus

>>> +1
>>>
>>> Keith

> On 09.12.20 18:24, Dick Groskamp wrote:
>> On 2020/12/09 11:34:03, Carl Marcum  wrote:
>>> Hi Dick,
>>>
>>> I have copied it out and it's contents are below.
>>>
>>> It should be in github or svn but I haven't had time to do anything
>>> with it.
>>>
>>> On 12/9/20 5:42 AM, Dick Groskamp wrote:
 On 2020/12/08 18:56:25, Carl Marcum  wrote:
> There are still hundreds of broken pages in the dev guide.
> Yes it seems to be idls and ildm tags.
>
> There is a new upgraded VM setup for the wiki waiting to get
> changed to
> but I had hoped to look into before it get switched over.
> But I have had limited time and I haven't been able to do any
> testing
> with it since the URL is being redirected.
> I don't know anything about MediaWiki extensions, yet anyway :)
>
> The Infra ticket for our VM is [1].
>
> The only place I know where the code is in the current wiki under:
> extensions/OOoIDLtags/OOoIDLtags.php
>
>
> [1] https://issues.apache.org/jira/browse/INFRA-20339
>
> Best regards,
> Carl
>
>
> -
>
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
 Carl, thanks i will check into it.

 Is it possible to export/copy the IDLTags extension from the MWiki
 to a more accessible place ?
 That way it might be accessible for editing or reversed
 engineering. I think for now it is not reachable.


>>> The filename is OOoIDLtags.php
>>> 
>>> >> /**
>>>     * IDL Tag extension
>>>     * The IDLTagExtension was written to manage the IDL links in the
>>> OpenOffice.org Developer's Guide.
>>>     * The extension converts Java paths to links back to the
>>> online IDL
>>> documentation.
>>>     * @version 1.0.2
>>>     * @link
>>> http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
>>>     */
>>>
>>> if ( !defined( 'MEDIAWIKI' ) ) {
>>>        die( 'This file is a MediaWiki extension, it is not a
>>> valid entry
>>> point' );
>>> }
>>>
>>> // Extension credits that will show up on Special:Version
>>> $wgExtensionCredits['parserhook'][] = array(
>>>        'name' => 'IDL Tags',
>>>        'version' => '1.0.2',
>>>        'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
>>>        'description' => 'Manage the IDL links in the OOo Dev
>>> Guide ',
>>>        'url' =>
>>> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
>>> );
>>>
>>> global $wgExtIDLtags;
>>> $wgExtIDLtags   = new RenderIDLtags;
>>> $wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );
>>>
>>> class RenderIDLtags {
>>>
>>>        function oooIDLTags() {
>>>            global $wgParser;
>>>            $wgParser->setHook( 'idl', array( &$this, 'renderIDL'
>>> ) );
>>>            $wgParser->setHook( 'idlm', array( &$this,
>>> 'renderIDLM' ) );
>>>            $wgParser->setHook( 'idls', array( &$this,
>>> 'renderIDLS' ) );
>>>            $wgParser->setHook( 'idlmodule', array( &$this,
>>> 'renderIDLMODULE' ) );
>>>            $wgParser->setHook( 'idltopic', array( &$this,
>

Re: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

2020-12-11 Thread Carl Marcum

It's been awhile since I've done any PHP so I've been doing some testing
in an online PHP Sandbox [1].

[1] https://sandbox.onlinephpfunctions.com/

See below:

On 12/11/20 3:30 PM, Dave Fisher wrote:

Sent from my iPhone

On Dec 11, 2020, at 11:46 AM, Dick Groskamp wrote:

On 2020/12/11 19:34:47, Matthias Seidel wrote:
Hi Dick,

Am 11.12.20 um 20:29 schrieb Dick Groskamp:

On 2020/12/11 17:23:20, Matthias Seidel wrote:

Hi Dick,

Am 11.12.20 um 17:14 schrieb Dick Groskamp:

The extension is not broken, it is outdated. It cannot be updated
because that would need a newer version of Wiki.
However, our AOO skin for the Wiki must be adapted to the newer Wiki
version...

At least that is what I understood from Andrea's posts regarding the
Wiki server in 2019 [1]

Well, if it is outdated and it doesn't do its job, I think it is broken.
What I meant to say is that it doesn't work the way it was designed anymore.

See above, the extension is not ours. It is from mediaWiki.org (?)

Well, I think it is ours. It was especially created by former developers for
this purpose and it is probably nowhere else available/usable and just works on
our wiki.

Who would that developer be?! Do you know a name?

This clearly an OOo extension.

Clayton didn’t really join AOO and Terry did the Forum move but seemed to get
frustrated and left.

I think that the approach could be separate from Carl’s new Wiki VM effort.

Someone will need to look at the current VM and try your idea about changing
the function.

If Andrea can’t then I’ll have a look early next week.

Regards,
Dave

'description' => 'Manage the IDL links in the OOo Dev Guide ',
'url' =>
'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
);

Isn't it more likely that it is a mediawiki extension like:

https://www.mediawiki.org/wiki/Extension:SyntaxHighlight

I haven't read Andrea's post yet, I focused more on getting this defective
extension IDLTags repaired.

Well, that would be a workaround for the moment, but we should "simply"
fix the source of the problem...

With "source of the problem" I assume you mean upgrading the wiki version and
updating the skin
etc as mentioned in Andrea's post

As far as I know has Carl a new updated VM available to go along with that,
but he has a tiny
problem getting access. I think that will be the next step.

I think Arrigo's finding about the deprecated method may be it.

print("output = $output \n");
?>

which outputs:
input = com.sun.star.uno.XComponentContext:getServiceManager
page = com/sun/star/uno/XComponentContext:getServiceManager
anchor = com/sun/star/uno/XComponentContext.html#getServiceManager
function = getServiceManager
output = href="http://api.openoffice.org/docs/common/ref/com/sun/star/uno/XComponentContext.html#getServiceManager";
class="external text">getServiceManager

which I think is a correct link.

I can take a shot at the production fix unless someone has concerns.

Best regards,
Carl

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

Re: Fixing not showing pages of DevGuide

2020-12-11 Thread Keith N. McKenna

On 12/11/2020 5:50 AM, Dick Groskamp wrote:
> 
> 
> On 2020/12/10 19:13:38, "Keith N. McKenna"  wrote: 
>> On 12/9/2020 11:42 AM, Dick Groskamp wrote:
>>> Started this morning to fix the pages that are not showing in the DevGuide.
>>> Due to a broken extension tags ,  and  prevent pages 
>>> from displaying content.
>>>
>>> However, content is there.
>>> Content is editable by tweaking the URL of the not showing page
>>>
>>> For instance:
>>> https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic
>>>
>>> needs to become:
>>> https://wiki.openoffice.org/w/index.php?title=Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic&action=edit
>>>
>>> so: replacing wiki/ by w/index.php?title=  and add &action=edit to the end 
>>> of the URL.
>>>
>>> Content is then editable.
>>>
>>> tag  can be changed to  to make it work again
>>> tag  and  need to be replaced by an url to the page.
>>>
>>> Like 
>>> [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XMultiComponentFactory.html#createInstanceWithContext,
>>>  followed by the content of the tag en closing bracket ]
>>>
>>> Like
>>> [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XMultiComponentFactory.html#createInstanceWithContext
>>>  com.sun.star.lang.XMultiComponentFactory:createInstanceWithContext]
>>>
>>> It is a manual job and there are a lot of pages. (I'll be busy :-) )
>>>
>> Dick; I will be more than happy to help if you would like to coordinate
>> what is done and what we each can do.
>>
>> Regards
>> Keith
>>
>>
>>
> Keith,
> 
> thanks for the offer, much appreciated.
> 
> In the other thread 
> https://lists.apache.org/thread.html/r9b07bbcb478d65bb24cb34e41d2dbd68ee6a36ddc734befe391a3148%40%3Cdev.openoffice.apache.org%3E
>  I'm talking to Carl to see if it is possible to make a change to the 
> extension IDLTags by replacing the obsolete ereg_replace function by 
> pereg_replace function, which should work on PHP > 7.0.*
> 
> My suggestion is to see/wait if that is possible on a short term and if not, 
> or if it won't work, to go on with replacing the tags ,  and 
>  by hardcoded URLs. The tag  is still working, probably 
> because it uses str_replace function and not the obsolete ereg_replace 
> function.
> Most frequent tag seems to be , but the problem is that if one of the 
> other tags is on the same page the whole page won't show.
> 
> I hope someone with more knowledge of PHP can help us with this on the short 
> term.
> 
> In the mean time I will check the pages to see where the conflicting tags 
> are, so we have a kind of index to the pages we might have to change.
> That way we have an impression on how much there is to do and how we, if 
> necessary, can divide the workload.
> 
> Does that make sense ?
> 

That makes perfect sense Dick.Will be much better to fix the extension.
I see Peter has set up a a repo for the custom extensions like that on
our gitbox account so once the redirect is removed and someone can get
to those we will be in much better shape to handle this kind of problem
in the future.

If we do need to change things manually it will be great to have the
list of pages so the work can be divided up more easily.

Regards
Keith



signature.asc
Description: OpenPGP digital signature

Re: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

2020-12-11 Thread Rory O'Farrell

On Fri, 11 Dec 2020 12:30:37 -0800
Dave Fisher  wrote:

> 
> 
> Sent from my iPhone
> 
> > On Dec 11, 2020, at 11:46 AM, Dick Groskamp  wrote:
> > 
> > 
> > 
> >> On 2020/12/11 19:34:47, Matthias Seidel  
> >> wrote: 
> >> Hi Dick,
> >> 
> >>> Am 11.12.20 um 20:29 schrieb Dick Groskamp:
> >>> 
> >>> On 2020/12/11 17:23:20, Matthias Seidel  
> >>> wrote: 
>  Hi Dick,
>  
>  Am 11.12.20 um 17:14 schrieb Dick Groskamp:
>  
>  The extension is not broken, it is outdated. It cannot be updated
>  because that would need a newer version of Wiki.
>  However, our AOO skin for the Wiki must be adapted to the newer Wiki
>  version...
>  
>  At least that is what I understood from Andrea's posts regarding the
>  Wiki server in 2019 [1]
>  
> >>> Well, if it is outdated and it doesn't do its job, I think it is broken.
> >>> What I meant to say is that it doesn't work the way it was designed 
> >>> anymore.
>  See above, the extension is not ours. It is from mediaWiki.org (?)
>  
> >>> Well, I think it is ours. It was especially created by former developers 
> >>> for this purpose and it is probably nowhere else available/usable and 
> >>> just works on our wiki.
> >> 
> >> Who would that developer be?! Do you know a name?
> > 
> > It was somewhere up in this thread:
> > // Extension credits that will show up on Special:Version
> > $wgExtensionCredits['parserhook'][] = array(
> > 'name' => 'IDL Tags',
> > 'version' => '1.0.2',
> > 'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
> 
> This clearly an OOo extension.
> 
> Clayton didn’t really join AOO and Terry did the Forum move but seemed to get 
> frustrated and left.


Terry had health problems and, as far as I remember, changed residence to 
Greece about 2010; he has not logged onto en-Forum since Aug 2017.  I have no 
information as to his well-being.

Rory


> 
> I think that the approach could be separate from Carl’s new Wiki VM effort.
> 
> Someone will need to look at the current VM and try your idea about changing 
> the function.
> 
> If Andrea can’t then I’ll have a look early next week.
> 
> Regards,
> Dave
> 
> > 'description' => 'Manage the IDL links in the OOo Dev Guide ',
> > 'url' => 
> > 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
> > );
> >> 
> >> Isn't it more likely that it is a mediawiki extension like:
> >> 
> >> https://www.mediawiki.org/wiki/Extension:SyntaxHighlight
> >> 
> > That is probably where the confusion comes from. You can develop your own 
> > extensions if you want, just like our own .oxt's. The whole IDLTags 
> > extension is the PHP-page Carl copied from the configuration. That's all
> >>> 
> >>> I haven't read Andrea's post yet, I focused more on getting this 
> >>> defective extension IDLTags repaired.
> >> 
> >> Well, that would be a workaround for the moment, but we should "simply"
> >> fix the source of the problem...
> >> 
> > With "source of the problem" I assume you mean upgrading the wiki version 
> > and updating the skin
> > etc as mentioned in Andrea's post
> > 
> > As far as I know has Carl a new updated VM  available to go along with 
> > that, but he has a tiny
> > problem getting access. I think that will be the next step.
> > 
> > -
> > 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
> 


-- 
Rory O'Farrell 

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

Re: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

2020-12-11 Thread Dave Fisher




Sent from my iPhone

> On Dec 11, 2020, at 11:46 AM, Dick Groskamp  wrote:
> 
> 
> 
>> On 2020/12/11 19:34:47, Matthias Seidel  wrote: 
>> Hi Dick,
>> 
>>> Am 11.12.20 um 20:29 schrieb Dick Groskamp:
>>> 
>>> On 2020/12/11 17:23:20, Matthias Seidel  wrote: 
 Hi Dick,
 
 Am 11.12.20 um 17:14 schrieb Dick Groskamp:
 
 The extension is not broken, it is outdated. It cannot be updated
 because that would need a newer version of Wiki.
 However, our AOO skin for the Wiki must be adapted to the newer Wiki
 version...
 
 At least that is what I understood from Andrea's posts regarding the
 Wiki server in 2019 [1]
 
>>> Well, if it is outdated and it doesn't do its job, I think it is broken.
>>> What I meant to say is that it doesn't work the way it was designed anymore.
 See above, the extension is not ours. It is from mediaWiki.org (?)
 
>>> Well, I think it is ours. It was especially created by former developers 
>>> for this purpose and it is probably nowhere else available/usable and just 
>>> works on our wiki.
>> 
>> Who would that developer be?! Do you know a name?
> 
> It was somewhere up in this thread:
> // Extension credits that will show up on Special:Version
> $wgExtensionCredits['parserhook'][] = array(
> 'name' => 'IDL Tags',
> 'version' => '1.0.2',
> 'author' => array( 'Clayton Cornell', 'Terry Ellison' ),

This clearly an OOo extension.

Clayton didn’t really join AOO and Terry did the Forum move but seemed to get 
frustrated and left.

I think that the approach could be separate from Carl’s new Wiki VM effort.

Someone will need to look at the current VM and try your idea about changing 
the function.

If Andrea can’t then I’ll have a look early next week.

Regards,
Dave

> 'description' => 'Manage the IDL links in the OOo Dev Guide ',
> 'url' => 
> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
> );
>> 
>> Isn't it more likely that it is a mediawiki extension like:
>> 
>> https://www.mediawiki.org/wiki/Extension:SyntaxHighlight
>> 
> That is probably where the confusion comes from. You can develop your own 
> extensions if you want, just like our own .oxt's. The whole IDLTags extension 
> is the PHP-page Carl copied from the configuration. That's all
>>> 
>>> I haven't read Andrea's post yet, I focused more on getting this defective 
>>> extension IDLTags repaired.
>> 
>> Well, that would be a workaround for the moment, but we should "simply"
>> fix the source of the problem...
>> 
> With "source of the problem" I assume you mean upgrading the wiki version and 
> updating the skin
> etc as mentioned in Andrea's post
> 
> As far as I know has Carl a new updated VM  available to go along with that, 
> but he has a tiny
> problem getting access. I think that will be the next step.
> 
> -
> 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: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

Hi Dick,

Am 11.12.20 um 20:45 schrieb Dick Groskamp:
>
> On 2020/12/11 19:34:47, Matthias Seidel  wrote: 
>> Hi Dick,
>>
>> Am 11.12.20 um 20:29 schrieb Dick Groskamp:
>>> On 2020/12/11 17:23:20, Matthias Seidel  wrote: 
 Hi Dick,

 Am 11.12.20 um 17:14 schrieb Dick Groskamp:

 The extension is not broken, it is outdated. It cannot be updated
 because that would need a newer version of Wiki.
 However, our AOO skin for the Wiki must be adapted to the newer Wiki
 version...

 At least that is what I understood from Andrea's posts regarding the
 Wiki server in 2019 [1]

>>> Well, if it is outdated and it doesn't do its job, I think it is broken.
>>> What I meant to say is that it doesn't work the way it was designed anymore.
 See above, the extension is not ours. It is from mediaWiki.org (?)

>>> Well, I think it is ours. It was especially created by former developers 
>>> for this purpose and it is probably nowhere else available/usable and just 
>>> works on our wiki.
>> Who would that developer be?! Do you know a name?
> It was somewhere up in this thread:
> // Extension credits that will show up on Special:Version
> $wgExtensionCredits['parserhook'][] = array(
>  'name' => 'IDL Tags',
>  'version' => '1.0.2',
>  'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
>  'description' => 'Manage the IDL links in the OOo Dev Guide ',
>  'url' => 
> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
> );
>> Isn't it more likely that it is a mediawiki extension like:
>>
>> https://www.mediawiki.org/wiki/Extension:SyntaxHighlight
>>
> That is probably where the confusion comes from. You can develop your own 
> extensions if you want, just like our own .oxt's. The whole IDLTags extension 
> is the PHP-page Carl copied from the configuration. That's all

Yes, it seems that this was done "back then".

But I don't think we should try to fix such an old extension if there is
probably a better one included in the Wiki installation.

>>> I haven't read Andrea's post yet, I focused more on getting this defective 
>>> extension IDLTags repaired.
>> Well, that would be a workaround for the moment, but we should "simply"
>> fix the source of the problem...
>>
> With "source of the problem" I assume you mean upgrading the wiki version and 
> updating the skin
> etc as mentioned in Andrea's post
Yes, if I remember it right, Andrea had to use an older PHP version to
get the Wiki running "as is".
>
> As far as I know has Carl a new updated VM  available to go along with that, 
> but he has a tiny
> problem getting access. I think that will be the next step.

Infra wants to update the VM. This probably means we get an even newer
Wiki installation.

Carl has opened a ticket, since we can't test the new VM because of a
redirection.

Regards,

   Matthias

>
> -
> 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: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-




On 2020/12/11 19:34:47, Matthias Seidel  wrote: 
> Hi Dick,
> 
> Am 11.12.20 um 20:29 schrieb Dick Groskamp:
> >
> > On 2020/12/11 17:23:20, Matthias Seidel  wrote: 
> >> Hi Dick,
> >>
> >> Am 11.12.20 um 17:14 schrieb Dick Groskamp:
> >>
> >> The extension is not broken, it is outdated. It cannot be updated
> >> because that would need a newer version of Wiki.
> >> However, our AOO skin for the Wiki must be adapted to the newer Wiki
> >> version...
> >>
> >> At least that is what I understood from Andrea's posts regarding the
> >> Wiki server in 2019 [1]
> >>
> > Well, if it is outdated and it doesn't do its job, I think it is broken.
> > What I meant to say is that it doesn't work the way it was designed anymore.
> >> See above, the extension is not ours. It is from mediaWiki.org (?)
> >>
> > Well, I think it is ours. It was especially created by former developers 
> > for this purpose and it is probably nowhere else available/usable and just 
> > works on our wiki.
> 
> Who would that developer be?! Do you know a name?

It was somewhere up in this thread:
// Extension credits that will show up on Special:Version
$wgExtensionCredits['parserhook'][] = array(
 'name' => 'IDL Tags',
 'version' => '1.0.2',
 'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
 'description' => 'Manage the IDL links in the OOo Dev Guide ',
 'url' => 
'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
);
> 
> Isn't it more likely that it is a mediawiki extension like:
> 
> https://www.mediawiki.org/wiki/Extension:SyntaxHighlight
> 
That is probably where the confusion comes from. You can develop your own 
extensions if you want, just like our own .oxt's. The whole IDLTags extension 
is the PHP-page Carl copied from the configuration. That's all
> >
> > I haven't read Andrea's post yet, I focused more on getting this defective 
> > extension IDLTags repaired.
> 
> Well, that would be a workaround for the moment, but we should "simply"
> fix the source of the problem...
> 
With "source of the problem" I assume you mean upgrading the wiki version and 
updating the skin
etc as mentioned in Andrea's post

As far as I know has Carl a new updated VM  available to go along with that, 
but he has a tiny
problem getting access. I think that will be the next step.

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

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

Hi Dick,

Am 11.12.20 um 20:29 schrieb Dick Groskamp:
>
> On 2020/12/11 17:23:20, Matthias Seidel  wrote: 
>> Hi Dick,
>>
>> Am 11.12.20 um 17:14 schrieb Dick Groskamp:
>>
>> The extension is not broken, it is outdated. It cannot be updated
>> because that would need a newer version of Wiki.
>> However, our AOO skin for the Wiki must be adapted to the newer Wiki
>> version...
>>
>> At least that is what I understood from Andrea's posts regarding the
>> Wiki server in 2019 [1]
>>
> Well, if it is outdated and it doesn't do its job, I think it is broken.
> What I meant to say is that it doesn't work the way it was designed anymore.
>> See above, the extension is not ours. It is from mediaWiki.org (?)
>>
> Well, I think it is ours. It was especially created by former developers for 
> this purpose and it is probably nowhere else available/usable and just works 
> on our wiki.

Who would that developer be?! Do you know a name?

Isn't it more likely that it is a mediawiki extension like:

https://www.mediawiki.org/wiki/Extension:SyntaxHighlight

>
> I haven't read Andrea's post yet, I focused more on getting this defective 
> extension IDLTags repaired.

Well, that would be a workaround for the moment, but we should "simply"
fix the source of the problem...

Regards,

   Matthias

>
> Problem is the deprecation of the ereg_replace function from PHP 7.0.*
> That was the function that was used in this IDLTags extension and made it 
> work as it did. This is the reason that several pages in the DevGuide show 
> blank.
>
> If we can replace the used ereg_replace function by a still usable 
> preg_replace function it should
> work again and all should be well :-)
>
>
>
>
>
> -
> 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: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-




On 2020/12/11 17:23:20, Matthias Seidel  wrote: 
> Hi Dick,
> 
> Am 11.12.20 um 17:14 schrieb Dick Groskamp:
> 
> The extension is not broken, it is outdated. It cannot be updated
> because that would need a newer version of Wiki.
> However, our AOO skin for the Wiki must be adapted to the newer Wiki
> version...
> 
> At least that is what I understood from Andrea's posts regarding the
> Wiki server in 2019 [1]
> 
Well, if it is outdated and it doesn't do its job, I think it is broken.
What I meant to say is that it doesn't work the way it was designed anymore.
> 
> See above, the extension is not ours. It is from mediaWiki.org (?)
> 
Well, I think it is ours. It was especially created by former developers for 
this purpose and it is probably nowhere else available/usable and just works on 
our wiki.

I haven't read Andrea's post yet, I focused more on getting this defective 
extension IDLTags repaired.

Problem is the deprecation of the ereg_replace function from PHP 7.0.*
That was the function that was used in this IDLTags extension and made it work 
as it did. This is the reason that several pages in the DevGuide show blank.

If we can replace the used ereg_replace function by a still usable preg_replace 
function it should
work again and all should be well :-)





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

Re: Call for Proposals: Apache OpenOffice Devroom at FOSDEM 2021 (online)

Hi Andrea,

Wouldn't it be useful to have a link to the CfP also here:

https://fosdem.org/2021/schedule/tracks/

Like the other Dev rooms did it?

Regards,

   Matthias

Am 08.12.20 um 21:51 schrieb Andrea Pescetti:
> ## Call for Proposals
>
> We are happy to announce that we will be running an Apache OpenOffice
> Devroom again at FOSDEM 2021.
>
> The event will be held online on Saturday, February 6th, 2021.
> Participation is free. No registration required.
>
> We are now open to receiving proposals for content for a full day of
> talks, demos and discussions on and around Apache OpenOffice.
>
> ## Important dates
>
> - Submission deadline: Monday Dec 28th 2020
> - Schedule announcement: Thursday December 31st 2020
> - Devroom date: Saturday Feb 6th 2021
>
> ## Topics
>
> Anything related to Apache OpenOffice is welcome:
>
> - Technical talks about Apache OpenOffice itself
> - Apache OpenOffice stories, demos and tutorials
> - Talks about topics related to Apache OpenOffice (ODF, build tools,
> translation tools, community...) may be submitted too
>
> ## Submissions
>
> Submissions are easy: basically just a talk title and short description.
>
> Visit https://penta.fosdem.org/submission/FOSDEM21
>
> - If you do not have an account from previous years, create one
> - Click 'Create Event'
> - Enter your talk details
> - Enter a maximum duration of 45 minutes
> - Be sure to select the Apache OpenOffice Devroom track
> - Submit
>
> Looking forward to seeing your submissions!
>
> Regards,
>   Andrea.
>
> -
> 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: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-




On 2020/12/11 17:57:33, Matthias Seidel  wrote: 
> Hi Peter,
> 
> Am 11.12.20 um 18:47 schrieb Peter Kovacs:
> > +1 for Dave's ideas.
> > I just wanted to enable. In doubt we delete the repo and create new ones.
> >
> > I created it because the feedback did suggest it is good way. Maybe I was 
> > to quick with going forward. I am sorry. 
> 
> No need to be sorry, but maybe the naming was a bit confusing.
> 
> I am +1 to put something like our AOO skin it a Repository.
> And the forum modifications in another.
> 
> Regards,
> 
>    Matthias
OK, clear. I missed the Forum part.

Sounds like a good plan to have two repo's, one for MWiki and one for Forum

+1 for Dave's proposal
> 
> >
> > Am 11. Dezember 2020 17:34:31 MEZ schrieb Dave Fisher 
> > :
> >> Excuse the top post, but I thought Peter had proposed two repositories
> >>
> >> (1) mwiki for all of the mediawiki configuration including this
> >> extension. But somehow this has become a tiny repository for just this
> >> particular extension?
> >>
> >> (2) forums for the forum configuration. I’ll take this one up within
> >> the next month or two. I have notes from the last upgrade and the VM
> >> does need to be upgraded.
> >>
> >> Regards,
> >> Dave
> >>
> >> Sent from my iPhone
> >>
> >>> On Dec 11, 2020, at 8:14 AM, Dick Groskamp  wrote:
> >>>
> >>> 
> >>>
>  On 2020/12/11 15:01:35, Matthias Seidel 
> >> wrote: 
>  Hi Peter,
> 
>  I am not sure what you are talking about here...
> 
>  The discussion is about a non working extension for our Wiki server.
> 
>  The repository is for our Media Wiki extension?
> 
>  2 totally different things...
> 
>  Matthias
> 
> > Am 11.12.20 um 12:22 schrieb Peter Kovacs:
> > I have created the Repository for MWiki extensions with my Proposed
> >> name:
> > openoffice-mwiki-ext.git
> > 
> >
> > It is ready to add our MWiki extensions.
> >
> >
> > On 10.12.20 20:35, Keith N. McKenna wrote:
> >> On 12/9/2020 5:38 PM, Marcus wrote:
> >>> Am 09.12.20 um 18:35 schrieb Peter Kovacs:
>  How about we create a OpenOffice-Mwiki-ext Repo in gitbox?
> 
>  We could do the same for the forums customizations.
> 
>  So we have more control over our support code.
> >>> +1
> >>> This increases the chance that also others can have a look and
> >> give
> >>> some
> >>> hints when problems arise.
> >>>
> >>> Marcus
> >>>
> >> +1
> >>
> >> Keith
>  On 09.12.20 18:24, Dick Groskamp wrote:
> > On 2020/12/09 11:34:03, Carl Marcum  wrote:
> >> Hi Dick,
> >>
> >> I have copied it out and it's contents are below.
> >>
> >> It should be in github or svn but I haven't had time to do
> >> anything
> >> with it.
> >>
> >> On 12/9/20 5:42 AM, Dick Groskamp wrote:
> >>> On 2020/12/08 18:56:25, Carl Marcum 
> >> wrote:
>  There are still hundreds of broken pages in the dev guide.
>  Yes it seems to be idls and ildm tags.
> 
>  There is a new upgraded VM setup for the wiki waiting to get
>  changed to
>  but I had hoped to look into before it get switched over.
>  But I have had limited time and I haven't been able to do
> >> any
>  testing
>  with it since the URL is being redirected.
>  I don't know anything about MediaWiki extensions, yet anyway
> >> :)
>  The Infra ticket for our VM is [1].
> 
>  The only place I know where the code is in the current wiki
> >> under:
>  extensions/OOoIDLtags/OOoIDLtags.php
> 
> 
>  [1] https://issues.apache.org/jira/browse/INFRA-20339
> 
>  Best regards,
>  Carl
> 
> 
> 
> >> -
>  To unsubscribe, e-mail:
> >> dev-unsubscr...@openoffice.apache.org
>  For additional commands, e-mail:
> >> dev-h...@openoffice.apache.org
> 
> >>> Carl, thanks i will check into it.
> >>>
> >>> Is it possible to export/copy the IDLTags extension from the
> >> MWiki
> >>> to a more accessible place ?
> >>> That way it might be accessible for editing or reversed
> >>> engineering. I think for now it is not reachable.
> >>>
> >>>
> >> The filename is OOoIDLtags.php
> >> 
> >>  >> /**
> >> * IDL Tag extension
> >> * The IDLTagExtension was written to manage the IDL links
> >> in the
> >> OpenOffice.org Developer's Guide.
> >> * The extension converts Java paths to links back to the
> >> online IDL

Re: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

Hi Peter,

Am 11.12.20 um 18:47 schrieb Peter Kovacs:
> +1 for Dave's ideas.
> I just wanted to enable. In doubt we delete the repo and create new ones.
>
> I created it because the feedback did suggest it is good way. Maybe I was to 
> quick with going forward. I am sorry. 

No need to be sorry, but maybe the naming was a bit confusing.

I am +1 to put something like our AOO skin it a Repository.
And the forum modifications in another.

Regards,

   Matthias

>
> Am 11. Dezember 2020 17:34:31 MEZ schrieb Dave Fisher :
>> Excuse the top post, but I thought Peter had proposed two repositories
>>
>> (1) mwiki for all of the mediawiki configuration including this
>> extension. But somehow this has become a tiny repository for just this
>> particular extension?
>>
>> (2) forums for the forum configuration. I’ll take this one up within
>> the next month or two. I have notes from the last upgrade and the VM
>> does need to be upgraded.
>>
>> Regards,
>> Dave
>>
>> Sent from my iPhone
>>
>>> On Dec 11, 2020, at 8:14 AM, Dick Groskamp  wrote:
>>>
>>> 
>>>
 On 2020/12/11 15:01:35, Matthias Seidel 
>> wrote: 
 Hi Peter,

 I am not sure what you are talking about here...

 The discussion is about a non working extension for our Wiki server.

 The repository is for our Media Wiki extension?

 2 totally different things...

 Matthias

> Am 11.12.20 um 12:22 schrieb Peter Kovacs:
> I have created the Repository for MWiki extensions with my Proposed
>> name:
> openoffice-mwiki-ext.git
> 
>
> It is ready to add our MWiki extensions.
>
>
> On 10.12.20 20:35, Keith N. McKenna wrote:
>> On 12/9/2020 5:38 PM, Marcus wrote:
>>> Am 09.12.20 um 18:35 schrieb Peter Kovacs:
 How about we create a OpenOffice-Mwiki-ext Repo in gitbox?

 We could do the same for the forums customizations.

 So we have more control over our support code.
>>> +1
>>> This increases the chance that also others can have a look and
>> give
>>> some
>>> hints when problems arise.
>>>
>>> Marcus
>>>
>> +1
>>
>> Keith
 On 09.12.20 18:24, Dick Groskamp wrote:
> On 2020/12/09 11:34:03, Carl Marcum  wrote:
>> Hi Dick,
>>
>> I have copied it out and it's contents are below.
>>
>> It should be in github or svn but I haven't had time to do
>> anything
>> with it.
>>
>> On 12/9/20 5:42 AM, Dick Groskamp wrote:
>>> On 2020/12/08 18:56:25, Carl Marcum 
>> wrote:
 There are still hundreds of broken pages in the dev guide.
 Yes it seems to be idls and ildm tags.

 There is a new upgraded VM setup for the wiki waiting to get
 changed to
 but I had hoped to look into before it get switched over.
 But I have had limited time and I haven't been able to do
>> any
 testing
 with it since the URL is being redirected.
 I don't know anything about MediaWiki extensions, yet anyway
>> :)
 The Infra ticket for our VM is [1].

 The only place I know where the code is in the current wiki
>> under:
 extensions/OOoIDLtags/OOoIDLtags.php


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

 Best regards,
 Carl



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

>>> Carl, thanks i will check into it.
>>>
>>> Is it possible to export/copy the IDLTags extension from the
>> MWiki
>>> to a more accessible place ?
>>> That way it might be accessible for editing or reversed
>>> engineering. I think for now it is not reachable.
>>>
>>>
>> The filename is OOoIDLtags.php
>> 
>> > /**
>> * IDL Tag extension
>> * The IDLTagExtension was written to manage the IDL links
>> in the
>> OpenOffice.org Developer's Guide.
>> * The extension converts Java paths to links back to the
>> online IDL
>> documentation.
>> * @version 1.0.2
>> * @link
>>
>> http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
>> */
>>
>> if ( !defined( 'MEDIAWIKI' ) ) {
>>die( 'This file is a MediaWiki extension, it is not a
>> valid entry
>> point' );
>> }
>>
>> // Extension credits that will show up on Special:Version
>> $wgExtensionCredits['parserhook

Re: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

+1 for Dave's ideas.
I just wanted to enable. In doubt we delete the repo and create new ones.

I created it because the feedback did suggest it is good way. Maybe I was to 
quick with going forward. I am sorry. 

Am 11. Dezember 2020 17:34:31 MEZ schrieb Dave Fisher :
>Excuse the top post, but I thought Peter had proposed two repositories
>
>(1) mwiki for all of the mediawiki configuration including this
>extension. But somehow this has become a tiny repository for just this
>particular extension?
>
>(2) forums for the forum configuration. I’ll take this one up within
>the next month or two. I have notes from the last upgrade and the VM
>does need to be upgraded.
>
>Regards,
>Dave
>
>Sent from my iPhone
>
>> On Dec 11, 2020, at 8:14 AM, Dick Groskamp  wrote:
>> 
>> 
>> 
>>> On 2020/12/11 15:01:35, Matthias Seidel 
>wrote: 
>>> Hi Peter,
>>> 
>>> I am not sure what you are talking about here...
>>> 
>>> The discussion is about a non working extension for our Wiki server.
>>> 
>>> The repository is for our Media Wiki extension?
>>> 
>>> 2 totally different things...
>>> 
>>> Matthias
>>> 
 Am 11.12.20 um 12:22 schrieb Peter Kovacs:
 I have created the Repository for MWiki extensions with my Proposed
>name:
 
 openoffice-mwiki-ext.git
 
 
 It is ready to add our MWiki extensions.
 
 
 On 10.12.20 20:35, Keith N. McKenna wrote:
> On 12/9/2020 5:38 PM, Marcus wrote:
>> Am 09.12.20 um 18:35 schrieb Peter Kovacs:
>>> How about we create a OpenOffice-Mwiki-ext Repo in gitbox?
>>> 
>>> We could do the same for the forums customizations.
>>> 
>>> So we have more control over our support code.
>> +1
>> This increases the chance that also others can have a look and
>give
>> some
>> hints when problems arise.
>> 
>> Marcus
>> 
> +1
> 
> Keith
>> 
>>> On 09.12.20 18:24, Dick Groskamp wrote:
 On 2020/12/09 11:34:03, Carl Marcum  wrote:
> Hi Dick,
> 
> I have copied it out and it's contents are below.
> 
> It should be in github or svn but I haven't had time to do
>anything
> with it.
> 
> On 12/9/20 5:42 AM, Dick Groskamp wrote:
>> On 2020/12/08 18:56:25, Carl Marcum 
>wrote:
>>> There are still hundreds of broken pages in the dev guide.
>>> Yes it seems to be idls and ildm tags.
>>> 
>>> There is a new upgraded VM setup for the wiki waiting to get
>>> changed to
>>> but I had hoped to look into before it get switched over.
>>> But I have had limited time and I haven't been able to do
>any
>>> testing
>>> with it since the URL is being redirected.
>>> I don't know anything about MediaWiki extensions, yet anyway
>:)
>>> 
>>> The Infra ticket for our VM is [1].
>>> 
>>> The only place I know where the code is in the current wiki
>under:
>>> extensions/OOoIDLtags/OOoIDLtags.php
>>> 
>>> 
>>> [1] https://issues.apache.org/jira/browse/INFRA-20339
>>> 
>>> Best regards,
>>> Carl
>>> 
>>> 
>>>
>-
>>> 
>>> To unsubscribe, e-mail:
>dev-unsubscr...@openoffice.apache.org
>>> For additional commands, e-mail:
>dev-h...@openoffice.apache.org
>>> 
>>> 
>> Carl, thanks i will check into it.
>> 
>> Is it possible to export/copy the IDLTags extension from the
>MWiki
>> to a more accessible place ?
>> That way it might be accessible for editing or reversed
>> engineering. I think for now it is not reachable.
>> 
>> 
> The filename is OOoIDLtags.php
> 
>  /**
> * IDL Tag extension
> * The IDLTagExtension was written to manage the IDL links
>in the
> OpenOffice.org Developer's Guide.
> * The extension converts Java paths to links back to the
> online IDL
> documentation.
> * @version 1.0.2
> * @link
>
>http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
> */
> 
> if ( !defined( 'MEDIAWIKI' ) ) {
>die( 'This file is a MediaWiki extension, it is not a
> valid entry
> point' );
> }
> 
> // Extension credits that will show up on Special:Version
> $wgExtensionCredits['parserhook'][] = array(
>'name' => 'IDL Tags',
>'version' => '1.0.2',
>'author' => array( 'Clayton Cornell', 'Terry Ellison'
>),
>'description' => 'Manage the IDL links in the OOo Dev
> Guide ',
>'url' =>
>
>'http://wiki.openoffice.org/wiki/Wiki_ma

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

Hi Dick,

Am 11.12.20 um 17:14 schrieb Dick Groskamp:
> I think there is some confusion. I will try to explain:
I know, that's why I asked. ;-)
>
> There is an extension for AOo, the extension MediaWiki that you repaired for 
> 4.1.8, which is intended to convert text from Writer to Mediawiki content. We 
> are not referring to that one.

Exactly!

But I didn't repair it, it just started to work after we updated several
core component...

>
> There is also an extension for the Mediawiki itself. That extension is called 
> IDLTags en converts tags on the Mediawiki to valid URL's for references to 
> IDL in the DevGuide.
> This is where we are talking about. This last extension has been broken and 
> we couldn't find it anywhere but in the configuration of Mediawiki itself. It 
> was removed from the wiki and it seems the developers left us.

The extension is not broken, it is outdated. It cannot be updated
because that would need a newer version of Wiki.
However, our AOO skin for the Wiki must be adapted to the newer Wiki
version...

At least that is what I understood from Andrea's posts regarding the
Wiki server in 2019 [1]

>
> Carl managed to extract IDLTags from the configuration and now we were 
> looking for a place to store it, so everyone can have a look at it and that 
> it is accessible to everyone.  See it as a safe haven for somehow lost 
> orphans.
>
> Therefore Peter has made this last repo openoffice-mwiki-ext.git
> 

See above, the extension is not ours. It is from mediaWiki.org (?)

Regards,

   Matthias

[1] https://www.mail-archive.com/dev@openoffice.apache.org/msg35741.html

>
> I think you can see it as a vault for precious gems that, not yet, have a 
> place on/in other repo's
>
> Greetings
>
> -
> 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: Java, OOo, ... (Re: [discussion] future embedded DB in AOO

2020-12-11 Thread Rony G Flatscher

Thank you as well, also for the link which I was not aware of! 😊

—-rony

Rony G. Flatscher (mobil/e)

> Am 10.12.2020 um 12:49 schrieb Matthias Seidel :
> 
> Hi all,
> 
>> Am 10.12.20 um 01:59 schrieb Peter Kovacs:
>> Thank you Rony for the Java deep dive.
> 
> +1
> 
> And BTW:
> 
> https://www.youtube.com/watch?v=p4DeOilMOQA
> 
> Regards,
> 
>Matthias
> 
>> 
>>> On 08.12.20 19:11, Rony G. Flatscher (Apache) wrote:
>>> Hmm, just some thoughts and pointers that may be helpful in the
>>> context of the current Java and
>>> possibly HSQL discussions.
>>> 
>>> Ad Java and OpenOffice
>>> 
>>>  IMHO Java has been fulfilling Sun's original promise "write
>>> once, run everywhere" in a very
>>>  impressive way for decades by  now! When Sun (being the inventor
>>> of Java) bought Star Division
>>>  to acquire StarOffice and making the source also available via
>>> openoffice.org, Sun also had the
>>>  Java interfaces put into the office suite, such that Java
>>> programmers would be able to interface
>>>  with OOo (using "OOo" to also mean AOO and the LO-fork) via UNO
>>> to this very day, and also
>>>  enabling Java to become an additional programming language to
>>> C++ to create OOo packages. This
>>>  has been some achievement and to me has been impressive to this
>>> very day!
>>> 
>>>  Java AOO components and Java applications interacting with AOO
>>> have been working for almost
>>>  decades without a need of change! (Also such applications would
>>> be deployable on different
>>>  operating systems without a need to rewrite and recompile them!)
>>> 
>>>  Discussing removing Java dependencies given this history and
>>> integration makes me a little bit
>>>  nervous if looking at some of the arguments, which may go back
>>> to misconceptions, hear-say and
>>>  possibly wrong information published about Java (like Oracle's
>>> change in its license would make
>>>  it impossible for software XXX to continue to use it ... which
>>> simply is not the case).
>>> 
>>>  The scripting interface to OOo is written in Java. Therefore it
>>> has become possible to use the
>>>  Java implemented scripting languages JavaScript and BeanShell to
>>> create OOo macros, besides OOo
>>>  Basic and Python. In addition - as others have done also - I
>>> authored a little package that uses
>>>  the OOo scripting interface in order to make another scripting
>>> language (ooRexx [1]) available
>>>  as an OOo macro language (one package creates a bidirectional
>>> bridge between ooRexx and Java
>>>  [2], the other package camouflages UNO as ooRexx and exploits
>>> the UNO reflection mechanism to
>>>  make it easy on programmers to interface with OOo [3]), so this
>>> is one reason, why being a
>>>  little bit nervous about a possible wrong assessment of Java...
>>> 
>>> Ad Java Distributions
>>> 
>>>  It seems that many people think that Java is only available in a
>>> proprietary form from Oracle
>>>  [4], which changed its license terms for its Java 1.8/8 and up,
>>> around the time when modular
>>>  Java (Java 9) got released. Oracle is regarded to be the owner
>>> of Java and therefore people tend
>>>  to think that there is no open-source, free alternative
>>> available, which is not correct.
>>> 
>>>  Enter "OpenJDK" [5] the open-source version of Java: this allows
>>> you to use Java for free (it is
>>>  GPL with the CLASSPATH exception license such that your code
>>> using it does not fall under GPL
>>>  automatically). With the modular versions of Java, starting with
>>> Java 9, one is even able to
>>>  create one own's Java (runtime environment, JRE) by combining
>>> the Java modules one wishes to
>>>  deploy[6]. (This would even open up the opportunity for OOo to
>>> create and distribute its own
>>>  tailored JRE, should such a need arise.)
>>> 
>>>  If you do not feel inclined to create your own JRE (Java
>>> runtime-environment) then you can
>>>  download Java=OpenJDK JRE for your particular platform from e.g.
>>> AdoptOpenJDK [7], Liberica [8]
>>>  or Zulu [9] to name a few.
>>> 
>>>  So Java is available in an open-source and free form with the
>>> term OpenJDK (open Java
>>>  development kit) [5].
>>> 
>>>  One tidbit in this "license" context: programmers who wish to
>>> contribute to Java/OpenJDK must
>>>  sign an "OCA" (Oracle contributer agreement [15]) giving more or
>>> less all rights on the
>>>  contributed software to Oracle which then makes the software
>>> available to the OpenJDK with GPL
>>>  and the CLASSPATH exception. Something that Sun had done with
>>> software contributed to OOo. This
>>>  BTW allowed later Oracle (after buying Sun and acquiring all of
>>> Sun's software rights) to
>>>  contribute the OOo source code to the Apache software
>>> foundation, making it in the end possible
>>>  to create and release AOO under

Re: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

2020-12-11 Thread Dave Fisher

Excuse the top post, but I thought Peter had proposed two repositories

(1) mwiki for all of the mediawiki configuration including this extension. But 
somehow this has become a tiny repository for just this particular extension?

(2) forums for the forum configuration. I’ll take this one up within the next 
month or two. I have notes from the last upgrade and the VM does need to be 
upgraded.

Regards,
Dave

Sent from my iPhone

> On Dec 11, 2020, at 8:14 AM, Dick Groskamp  wrote:
> 
> 
> 
>> On 2020/12/11 15:01:35, Matthias Seidel  wrote: 
>> Hi Peter,
>> 
>> I am not sure what you are talking about here...
>> 
>> The discussion is about a non working extension for our Wiki server.
>> 
>> The repository is for our Media Wiki extension?
>> 
>> 2 totally different things...
>> 
>> Matthias
>> 
>>> Am 11.12.20 um 12:22 schrieb Peter Kovacs:
>>> I have created the Repository for MWiki extensions with my Proposed name:
>>> 
>>> openoffice-mwiki-ext.git
>>> 
>>> 
>>> It is ready to add our MWiki extensions.
>>> 
>>> 
>>> On 10.12.20 20:35, Keith N. McKenna wrote:
 On 12/9/2020 5:38 PM, Marcus wrote:
> Am 09.12.20 um 18:35 schrieb Peter Kovacs:
>> How about we create a OpenOffice-Mwiki-ext Repo in gitbox?
>> 
>> We could do the same for the forums customizations.
>> 
>> So we have more control over our support code.
> +1
> This increases the chance that also others can have a look and give
> some
> hints when problems arise.
> 
> Marcus
> 
 +1
 
 Keith
> 
>> On 09.12.20 18:24, Dick Groskamp wrote:
>>> On 2020/12/09 11:34:03, Carl Marcum  wrote:
 Hi Dick,
 
 I have copied it out and it's contents are below.
 
 It should be in github or svn but I haven't had time to do anything
 with it.
 
 On 12/9/20 5:42 AM, Dick Groskamp wrote:
> On 2020/12/08 18:56:25, Carl Marcum  wrote:
>> There are still hundreds of broken pages in the dev guide.
>> Yes it seems to be idls and ildm tags.
>> 
>> There is a new upgraded VM setup for the wiki waiting to get
>> changed to
>> but I had hoped to look into before it get switched over.
>> But I have had limited time and I haven't been able to do any
>> testing
>> with it since the URL is being redirected.
>> I don't know anything about MediaWiki extensions, yet anyway :)
>> 
>> The Infra ticket for our VM is [1].
>> 
>> The only place I know where the code is in the current wiki under:
>> extensions/OOoIDLtags/OOoIDLtags.php
>> 
>> 
>> [1] https://issues.apache.org/jira/browse/INFRA-20339
>> 
>> Best regards,
>> Carl
>> 
>> 
>> -
>> 
>> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>> 
>> 
> Carl, thanks i will check into it.
> 
> Is it possible to export/copy the IDLTags extension from the MWiki
> to a more accessible place ?
> That way it might be accessible for editing or reversed
> engineering. I think for now it is not reachable.
> 
> 
 The filename is OOoIDLtags.php
 
 >>> /**
 * IDL Tag extension
 * The IDLTagExtension was written to manage the IDL links in the
 OpenOffice.org Developer's Guide.
 * The extension converts Java paths to links back to the
 online IDL
 documentation.
 * @version 1.0.2
 * @link
 http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
 */
 
 if ( !defined( 'MEDIAWIKI' ) ) {
die( 'This file is a MediaWiki extension, it is not a
 valid entry
 point' );
 }
 
 // Extension credits that will show up on Special:Version
 $wgExtensionCredits['parserhook'][] = array(
'name' => 'IDL Tags',
'version' => '1.0.2',
'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
'description' => 'Manage the IDL links in the OOo Dev
 Guide ',
'url' =>
 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
 );
 
 global $wgExtIDLtags;
 $wgExtIDLtags   = new RenderIDLtags;
 $wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );
 
 class RenderIDLtags {
 
function oooIDLTags() {
global $wgParser;
$wgParser->setHook( 'idl', array( &$this, 'renderIDL'

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-




On 2020/12/11 15:01:35, Matthias Seidel  wrote: 
> Hi Peter,
> 
> I am not sure what you are talking about here...
> 
> The discussion is about a non working extension for our Wiki server.
> 
> The repository is for our Media Wiki extension?
> 
> 2 totally different things...
> 
> Matthias
> 
> Am 11.12.20 um 12:22 schrieb Peter Kovacs:
> > I have created the Repository for MWiki extensions with my Proposed name:
> >
> > openoffice-mwiki-ext.git
> > 
> >
> > It is ready to add our MWiki extensions.
> >
> >
> > On 10.12.20 20:35, Keith N. McKenna wrote:
> >> On 12/9/2020 5:38 PM, Marcus wrote:
> >>> Am 09.12.20 um 18:35 schrieb Peter Kovacs:
>  How about we create a OpenOffice-Mwiki-ext Repo in gitbox?
> 
>  We could do the same for the forums customizations.
> 
>  So we have more control over our support code.
> >>> +1
> >>> This increases the chance that also others can have a look and give
> >>> some
> >>> hints when problems arise.
> >>>
> >>> Marcus
> >>>
> >> +1
> >>
> >> Keith
> >>>
>  On 09.12.20 18:24, Dick Groskamp wrote:
> > On 2020/12/09 11:34:03, Carl Marcum  wrote:
> >> Hi Dick,
> >>
> >> I have copied it out and it's contents are below.
> >>
> >> It should be in github or svn but I haven't had time to do anything
> >> with it.
> >>
> >> On 12/9/20 5:42 AM, Dick Groskamp wrote:
> >>> On 2020/12/08 18:56:25, Carl Marcum  wrote:
>  There are still hundreds of broken pages in the dev guide.
>  Yes it seems to be idls and ildm tags.
> 
>  There is a new upgraded VM setup for the wiki waiting to get
>  changed to
>  but I had hoped to look into before it get switched over.
>  But I have had limited time and I haven't been able to do any
>  testing
>  with it since the URL is being redirected.
>  I don't know anything about MediaWiki extensions, yet anyway :)
> 
>  The Infra ticket for our VM is [1].
> 
>  The only place I know where the code is in the current wiki under:
>  extensions/OOoIDLtags/OOoIDLtags.php
> 
> 
>  [1] https://issues.apache.org/jira/browse/INFRA-20339
> 
>  Best regards,
>  Carl
> 
> 
>  -
> 
>  To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
>  For additional commands, e-mail: dev-h...@openoffice.apache.org
> 
> 
> >>> Carl, thanks i will check into it.
> >>>
> >>> Is it possible to export/copy the IDLTags extension from the MWiki
> >>> to a more accessible place ?
> >>> That way it might be accessible for editing or reversed
> >>> engineering. I think for now it is not reachable.
> >>>
> >>>
> >> The filename is OOoIDLtags.php
> >> 
> >>  >> /**
> >>     * IDL Tag extension
> >>     * The IDLTagExtension was written to manage the IDL links in the
> >> OpenOffice.org Developer's Guide.
> >>     * The extension converts Java paths to links back to the
> >> online IDL
> >> documentation.
> >>     * @version 1.0.2
> >>     * @link
> >> http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
> >>     */
> >>
> >> if ( !defined( 'MEDIAWIKI' ) ) {
> >>        die( 'This file is a MediaWiki extension, it is not a
> >> valid entry
> >> point' );
> >> }
> >>
> >> // Extension credits that will show up on Special:Version
> >> $wgExtensionCredits['parserhook'][] = array(
> >>        'name' => 'IDL Tags',
> >>        'version' => '1.0.2',
> >>        'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
> >>        'description' => 'Manage the IDL links in the OOo Dev
> >> Guide ',
> >>        'url' =>
> >> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
> >> );
> >>
> >> global $wgExtIDLtags;
> >> $wgExtIDLtags   = new RenderIDLtags;
> >> $wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );
> >>
> >> class RenderIDLtags {
> >>
> >>        function oooIDLTags() {
> >>            global $wgParser;
> >>            $wgParser->setHook( 'idl', array( &$this, 'renderIDL'
> >> ) );
> >>            $wgParser->setHook( 'idlm', array( &$this,
> >> 'renderIDLM' ) );
> >>            $wgParser->setHook( 'idls', array( &$this,
> >> 'renderIDLS' ) );
> >>            $wgParser->setHook( 'idlmodule', array( &$this,
> >> 'renderIDLMODULE' ) );
> >>            $wgParser->setHook( 'idltopic', array( &$this,
> >> 'renderIDLTOPIC'
> >> ) );
> >>        }
> >>
> >>        function renderIDL( $input, $args, $parser ) {
> >>            $parser->disableCache();
> >>

Re: Does AOO 4.1.8 run under macOS Big Sur?

Hi Jim,

Am 11.12.20 um 12:47 schrieb Jim Jagielski:
>> On Dec 11, 2020, at 5:27 AM, Bidouille  wrote:
>>
>>> Which is why we need to get 4.2.0 out asap :/
>> Any news?
>> TDF blog publish on this bug: https://tinyurl.com/y6zjvp2j
>> Bad advice :-(
> I love that group. They are like immature kids. Or bitter ex-boy/girl-friends.
>
> What's next? Sticking out their tongues and going "Nyah Nyah Nyah! Apache 
> OpenOffice
> are a bunch of poopie-heads!" ? :)

I am sure they already did...

At least that is what I expect from these people! ;-)

Matthias

> -
> 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: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-

Hi Peter,

I am not sure what you are talking about here...

The discussion is about a non working extension for our Wiki server.

The repository is for our Media Wiki extension?

2 totally different things...

Matthias

Am 11.12.20 um 12:22 schrieb Peter Kovacs:
> I have created the Repository for MWiki extensions with my Proposed name:
>
> openoffice-mwiki-ext.git
> 
>
> It is ready to add our MWiki extensions.
>
>
> On 10.12.20 20:35, Keith N. McKenna wrote:
>> On 12/9/2020 5:38 PM, Marcus wrote:
>>> Am 09.12.20 um 18:35 schrieb Peter Kovacs:
 How about we create a OpenOffice-Mwiki-ext Repo in gitbox?

 We could do the same for the forums customizations.

 So we have more control over our support code.
>>> +1
>>> This increases the chance that also others can have a look and give
>>> some
>>> hints when problems arise.
>>>
>>> Marcus
>>>
>> +1
>>
>> Keith
>>>
 On 09.12.20 18:24, Dick Groskamp wrote:
> On 2020/12/09 11:34:03, Carl Marcum  wrote:
>> Hi Dick,
>>
>> I have copied it out and it's contents are below.
>>
>> It should be in github or svn but I haven't had time to do anything
>> with it.
>>
>> On 12/9/20 5:42 AM, Dick Groskamp wrote:
>>> On 2020/12/08 18:56:25, Carl Marcum  wrote:
 There are still hundreds of broken pages in the dev guide.
 Yes it seems to be idls and ildm tags.

 There is a new upgraded VM setup for the wiki waiting to get
 changed to
 but I had hoped to look into before it get switched over.
 But I have had limited time and I haven't been able to do any
 testing
 with it since the URL is being redirected.
 I don't know anything about MediaWiki extensions, yet anyway :)

 The Infra ticket for our VM is [1].

 The only place I know where the code is in the current wiki under:
 extensions/OOoIDLtags/OOoIDLtags.php


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

 Best regards,
 Carl


 -

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


>>> Carl, thanks i will check into it.
>>>
>>> Is it possible to export/copy the IDLTags extension from the MWiki
>>> to a more accessible place ?
>>> That way it might be accessible for editing or reversed
>>> engineering. I think for now it is not reachable.
>>>
>>>
>> The filename is OOoIDLtags.php
>> 
>> > /**
>>     * IDL Tag extension
>>     * The IDLTagExtension was written to manage the IDL links in the
>> OpenOffice.org Developer's Guide.
>>     * The extension converts Java paths to links back to the
>> online IDL
>> documentation.
>>     * @version 1.0.2
>>     * @link
>> http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
>>     */
>>
>> if ( !defined( 'MEDIAWIKI' ) ) {
>>        die( 'This file is a MediaWiki extension, it is not a
>> valid entry
>> point' );
>> }
>>
>> // Extension credits that will show up on Special:Version
>> $wgExtensionCredits['parserhook'][] = array(
>>        'name' => 'IDL Tags',
>>        'version' => '1.0.2',
>>        'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
>>        'description' => 'Manage the IDL links in the OOo Dev
>> Guide ',
>>        'url' =>
>> 'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
>> );
>>
>> global $wgExtIDLtags;
>> $wgExtIDLtags   = new RenderIDLtags;
>> $wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );
>>
>> class RenderIDLtags {
>>
>>        function oooIDLTags() {
>>            global $wgParser;
>>            $wgParser->setHook( 'idl', array( &$this, 'renderIDL'
>> ) );
>>            $wgParser->setHook( 'idlm', array( &$this,
>> 'renderIDLM' ) );
>>            $wgParser->setHook( 'idls', array( &$this,
>> 'renderIDLS' ) );
>>            $wgParser->setHook( 'idlmodule', array( &$this,
>> 'renderIDLMODULE' ) );
>>            $wgParser->setHook( 'idltopic', array( &$this,
>> 'renderIDLTOPIC'
>> ) );
>>        }
>>
>>        function renderIDL( $input, $args, $parser ) {
>>            $parser->disableCache();
>>            $output = $parser->recursiveTagParse( $input );
>>            $output = '> href="http://api.openoffice.org/docs/common/ref/' .
>>                str_replace ('.','/',$output).'.html" class="external
>> text">'.$output.'';
>>            return $output;
>>        }
>>
>>        function renderIDLM( $input

Re: Does AOO 4.1.8 run under macOS Big Sur?

I have an en-US and fr LANG test builds of AOO 4.2.0 available via:

http://home.apache.org/~jim/AOO-builds/ 


Also, these include my fork of beanshell (https://github.com/jimjag/beanshell2 
)

> On Dec 11, 2020, at 9:08 AM, Jim Jagielski  wrote:
> 
> I'm building a dev version of 4.2.0 w/ lang fr as we speak
> 
>> On Dec 11, 2020, at 8:28 AM, Bidouille  wrote:
>> 
>>> Who is running Big Sur?
>> We have end users on french forum.
>> Able (and motivated) to test it soon as possible :)
>> 
>> -
>> 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: Does AOO 4.1.8 run under macOS Big Sur?

I'm building a dev version of 4.2.0 w/ lang fr as we speak

> On Dec 11, 2020, at 8:28 AM, Bidouille  wrote:
> 
>> Who is running Big Sur?
> We have end users on french forum.
> Able (and motivated) to test it soon as possible :)
> 
> -
> 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: Does AOO 4.1.8 run under macOS Big Sur?

2020-12-11 Thread Bidouille

> Who is running Big Sur?
We have end users on french forum.
Able (and motivated) to test it soon as possible :)

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

Re: Does AOO 4.1.8 run under macOS Big Sur?




> On Dec 11, 2020, at 7:27 AM, Peter Kovacs  wrote:
> 
> 
> On 11.12.20 12:47, Jim Jagielski wrote:
>>> On Dec 11, 2020, at 5:27 AM, Bidouille  wrote:
>>> 
 Which is why we need to get 4.2.0 out asap :/
>>> Any news?
>>> TDF blog publish on this bug: https://tinyurl.com/y6zjvp2j
>>> Bad advice :-(
>> I love that group. They are like immature kids. Or bitter 
>> ex-boy/girl-friends.
> I told them they should do their own marketing. Just ignore it.
>> 
>> What's next? Sticking out their tongues and going "Nyah Nyah Nyah! Apache 
>> OpenOffice
>> are a bunch of poopie-heads!" ? :)
> 
> Hehe, I do believe some think that way. And that for quite soime time now.
> 
> However do you have any Idea by now what goes wrong?

That's what I've been working on w/ the various UNO fixes to macOS. My hope is
to have a test 4.2.0-dev build for someone w/ Big Sur to test on...

Who is running Big Sur?


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

Re: Does AOO 4.1.8 run under macOS Big Sur?




On 11.12.20 12:47, Jim Jagielski wrote:

On Dec 11, 2020, at 5:27 AM, Bidouille  wrote:


Which is why we need to get 4.2.0 out asap :/

Any news?
TDF blog publish on this bug: https://tinyurl.com/y6zjvp2j
Bad advice :-(

I love that group. They are like immature kids. Or bitter ex-boy/girl-friends.

I told them they should do their own marketing. Just ignore it.


What's next? Sticking out their tongues and going "Nyah Nyah Nyah! Apache 
OpenOffice
are a bunch of poopie-heads!" ? :)


Hehe, I do believe some think that way. And that for quite soime time now.

However do you have any Idea by now what goes wrong?
--
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

Re: Does AOO 4.1.8 run under macOS Big Sur?

> On Dec 11, 2020, at 5:27 AM, Bidouille  wrote:
> 
>> Which is why we need to get 4.2.0 out asap :/
> 
> Any news?
> TDF blog publish on this bug: https://tinyurl.com/y6zjvp2j
> Bad advice :-(

I love that group. They are like immature kids. Or bitter ex-boy/girl-friends.

What's next? Sticking out their tongues and going "Nyah Nyah Nyah! Apache 
OpenOffice
are a bunch of poopie-heads!" ? :)
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-mail: dev-h...@openoffice.apache.org

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-


I have created the Repository for MWiki extensions with my Proposed name:

openoffice-mwiki-ext.git 



It is ready to add our MWiki extensions.


On 10.12.20 20:35, Keith N. McKenna wrote:

On 12/9/2020 5:38 PM, Marcus wrote:

Am 09.12.20 um 18:35 schrieb Peter Kovacs:

How about we create a OpenOffice-Mwiki-ext Repo in gitbox?

We could do the same for the forums customizations.

So we have more control over our support code.

+1
This increases the chance that also others can have a look and give some
hints when problems arise.

Marcus


+1

Keith



On 09.12.20 18:24, Dick Groskamp wrote:

On 2020/12/09 11:34:03, Carl Marcum  wrote:

Hi Dick,

I have copied it out and it's contents are below.

It should be in github or svn but I haven't had time to do anything
with it.

On 12/9/20 5:42 AM, Dick Groskamp wrote:

On 2020/12/08 18:56:25, Carl Marcum  wrote:

There are still hundreds of broken pages in the dev guide.
Yes it seems to be idls and ildm tags.

There is a new upgraded VM setup for the wiki waiting to get
changed to
but I had hoped to look into before it get switched over.
But I have had limited time and I haven't been able to do any testing
with it since the URL is being redirected.
I don't know anything about MediaWiki extensions, yet anyway :)

The Infra ticket for our VM is [1].

The only place I know where the code is in the current wiki under:
extensions/OOoIDLtags/OOoIDLtags.php


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

Best regards,
Carl


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



Carl, thanks i will check into it.

Is it possible to export/copy the IDLTags extension from the MWiki
to a more accessible place ?
That way it might be accessible for editing or reversed
engineering. I think for now it is not reachable.



The filename is OOoIDLtags.php

http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension
    */

if ( !defined( 'MEDIAWIKI' ) ) {
       die( 'This file is a MediaWiki extension, it is not a valid entry
point' );
}

// Extension credits that will show up on Special:Version
$wgExtensionCredits['parserhook'][] = array(
       'name' => 'IDL Tags',
       'version' => '1.0.2',
       'author' => array( 'Clayton Cornell', 'Terry Ellison' ),
       'description' => 'Manage the IDL links in the OOo Dev Guide ',
       'url' =>
'http://wiki.openoffice.org/wiki/Wiki_maintenance/IDLTagExtension',
);

global $wgExtIDLtags;
$wgExtIDLtags   = new RenderIDLtags;
$wgExtensionFunctions[] = array( &$wgExtIDLtags, 'oooIDLTags' );

class RenderIDLtags {

       function oooIDLTags() {
           global $wgParser;
           $wgParser->setHook( 'idl', array( &$this, 'renderIDL' ) );
           $wgParser->setHook( 'idlm', array( &$this, 'renderIDLM' ) );
           $wgParser->setHook( 'idls', array( &$this, 'renderIDLS' ) );
           $wgParser->setHook( 'idlmodule', array( &$this,
'renderIDLMODULE' ) );
           $wgParser->setHook( 'idltopic', array( &$this,
'renderIDLTOPIC'
) );
       }

       function renderIDL( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $output = 'http://api.openoffice.org/docs/common/ref/' .
               str_replace ('.','/',$output).'.html" class="external
text">'.$output.'';
           return $output;
       }

       function renderIDLM( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $page = ereg_replace ('\.','/',$output);
           $anchor = ereg_replace (':','.html#',$page);
           $function = ereg_replace ('^.*:','',$page);
           $output = 'http://api.openoffice.org/docs/common/ref/' .
               $anchor.'" class="external text">'.$function.'';
           return $output;
       }

       function renderIDLS( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $function = ereg_replace ('^.*\.','',$output);
           $output = 'http://api.openoffice.org/docs/common/ref/' .
               ereg_replace ('\.','/',$output).'.html" class="external
text">'.$function.'';
           return $output;
       }

       function renderIDLMODULE( $input, $args, $parser ) {
           $parser->disableCache();
           $output = $parser->recursiveTagParse( $input );
           $function = ereg_replace ('^.*\.','',$output);
           $output = 'http://api.openoffice.org/docs/common/ref/' .
               ereg_replace ('\.','/',$output).'/module-ix.html"
class="external text">'.$output.'';
           return $output;
       }

       function renderIDLTOPIC( $input, $args, $parser ) {
           $parser->disableCache();
           return '';
       }
}


Be

Re: Call for Proposals: Apache OpenOffice Devroom at FOSDEM 2021 (online)


Hi all,

I have also entered a lecture. I would like to try if we can use the 
event to proceed to use as a public think tank.


The talk will be prerecorded, and so I can focus on the discussion with 
interested folks.


Title: The future of Base

Here is my abstract:

In this talk I will be talking about base. Base is the Database focused 
Application within Apache OpenOffice.
We will start of with a short Description where Base comes from, and 
what the Idea behind base has been.

I will sum up discussions that have taken place on development Mailinglist.
And I would like to take some visions up from the previous discussions 
and talk a bit about what Base

would needs if we would go into the direction of analytics and big data.


All the Best

Peter


On 11.12.20 01:13, Carl Marcum wrote:

Hi Andrea,

Thanks for the information!

I submitted the OpenOffice UNO Programming with Groovy talk I did at 
ApacheCon this year.


Best regards,
Carl

On 12/8/20 3:51 PM, Andrea Pescetti wrote:

## Call for Proposals

We are happy to announce that we will be running an Apache OpenOffice 
Devroom again at FOSDEM 2021.


The event will be held online on Saturday, February 6th, 2021. 
Participation is free. No registration required.


We are now open to receiving proposals for content for a full day of 
talks, demos and discussions on and around Apache OpenOffice.


## Important dates

- Submission deadline: Monday Dec 28th 2020
- Schedule announcement: Thursday December 31st 2020
- Devroom date: Saturday Feb 6th 2021

## Topics

Anything related to Apache OpenOffice is welcome:

- Technical talks about Apache OpenOffice itself
- Apache OpenOffice stories, demos and tutorials
- Talks about topics related to Apache OpenOffice (ODF, build tools, 
translation tools, community...) may be submitted too


## Submissions

Submissions are easy: basically just a talk title and short description.

Visit https://penta.fosdem.org/submission/FOSDEM21

- If you do not have an account from previous years, create one
- Click 'Create Event'
- Enter your talk details
- Enter a maximum duration of 45 minutes
- Be sure to select the Apache OpenOffice Devroom track
- Submit

Looking forward to seeing your submissions!

Regards,
  Andrea.

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




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


--
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

Re: Fixing not showing pages of DevGuide




On 2020/12/10 19:13:38, "Keith N. McKenna"  wrote: 
> On 12/9/2020 11:42 AM, Dick Groskamp wrote:
> > Started this morning to fix the pages that are not showing in the DevGuide.
> > Due to a broken extension tags ,  and  prevent pages 
> > from displaying content.
> > 
> > However, content is there.
> > Content is editable by tweaking the URL of the not showing page
> > 
> > For instance:
> > https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic
> > 
> > needs to become:
> > https://wiki.openoffice.org/w/index.php?title=Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic&action=edit
> > 
> > so: replacing wiki/ by w/index.php?title=  and add &action=edit to the end 
> > of the URL.
> > 
> > Content is then editable.
> > 
> > tag  can be changed to  to make it work again
> > tag  and  need to be replaced by an url to the page.
> > 
> > Like 
> > [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XMultiComponentFactory.html#createInstanceWithContext,
> >  followed by the content of the tag en closing bracket ]
> > 
> > Like
> > [http://api.openoffice.org/docs/common/ref/com/sun/star/lang/XMultiComponentFactory.html#createInstanceWithContext
> >  com.sun.star.lang.XMultiComponentFactory:createInstanceWithContext]
> > 
> > It is a manual job and there are a lot of pages. (I'll be busy :-) )
> > 
> Dick; I will be more than happy to help if you would like to coordinate
> what is done and what we each can do.
> 
> Regards
> Keith
> 
> 
> 
Keith,

thanks for the offer, much appreciated.

In the other thread 
https://lists.apache.org/thread.html/r9b07bbcb478d65bb24cb34e41d2dbd68ee6a36ddc734befe391a3148%40%3Cdev.openoffice.apache.org%3E
 I'm talking to Carl to see if it is possible to make a change to the extension 
IDLTags by replacing the obsolete ereg_replace function by pereg_replace 
function, which should work on PHP > 7.0.*

My suggestion is to see/wait if that is possible on a short term and if not, or 
if it won't work, to go on with replacing the tags ,  and 
 by hardcoded URLs. The tag  is still working, probably because 
it uses str_replace function and not the obsolete ereg_replace function.
Most frequent tag seems to be , but the problem is that if one of the 
other tags is on the same page the whole page won't show.

I hope someone with more knowledge of PHP can help us with this on the short 
term.

In the mean time I will check the pages to see where the conflicting tags are, 
so we have a kind of index to the pages we might have to change.
That way we have an impression on how much there is to do and how we, if 
necessary, can divide the workload.

Does that make sense ?



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

Re: Fwd: Broken_Link: "https://wiki.openoffice.org/wiki/Documentation/DevGuide/Basic/Accessing_Libraries_from_Basic"-rm201208-