Mailing-List: contact ooo-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ooo-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of jogischmidt@googlemail.com
 designates 209.85.212.175 as permitted sender)
Message-ID: <4F337A43.80008@googlemail.com>
Date: Thu, 09 Feb 2012 08:48:19 +0100
From: =?ISO-8859-1?Q?J=FCrgen_Schmidt?= <jogischmidt@googlemail.com>
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7;
 rv:9.0) Gecko/20111222 Thunderbird/9.0.1
MIME-Version: 1.0
To: ooo-dev@incubator.apache.org
Subject: Re: ANONYMOUS CMS ACCESS (was Re: Bad Link on OOO API Web Page)
References: <COL123-W58E452A36F8B7AAC2B580FB17A0@phx.gbl>
 <1328727918.76149.YahooMailNeo@web160906.mail.bf1.yahoo.com>
In-Reply-To: <1328727918.76149.YahooMailNeo@web160906.mail.bf1.yahoo.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

Hi,

first of all, excuse my top posting here.


Thanks Joe for explaining once more the process how we can easy change 
web-sites using the CMS bookmarklet. I will try it again because I 
wasn't able to use it until now (on MacOS with Firefox).

But anyway the mentioned link problem is part of the generated API 
reference documentation based on the IDL definitions. I don't think it 
make sense to edit these automatic generated docu directly. Otherwise 
the next time we completely replace it (for example with the upcoming 
3.4 reference docu) local changes will be overwritten.

It's better to submit an bugzilla issue for this kind of problems and 
assign the issue to me (jsc).

Juergen


On 2/8/12 8:05 PM, Joe Schaefer wrote:
> I don't know if this level of participation interests you Ric,
> but I'd like to share with the group the process involved in
> producing an actual patch suitable for a committer to apply
> regarding the website documents.
>
> The first thing an interested party needs to do is to install
> the CMS bookmarklet wherever their browser normally keeps bookmarks.
> The url which describes this process is at
>
>      https://cms.apache.org/ooo-site/#bookmark
>
> You will be prompted for credentials when you visit that url:
> non-committers should present a username of anonymous and an
> empty password.  Those creds will grant you full access to
> the CMS.
>
> What you do then is go to the actual page in question:
>
> http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/module-ix.html
>
> and simply click on the bookmarklet.  After a few moments to
> prepare a working copy for you, you will be directed to the
> source page containing the errant html.  Click on the [Edit]
> link and an editor session will let you modify the file to
> make the appropriate changes.  Submit those changes to the
> server and click on the [Diff] link which will show you your
> changes in patch form.  On that page is the option to [Mail Diff]
> whereby you can mail your patch off to this mailing list
> simply by filling out the form.
>
> Yes it's that easy, and committers will know how to incorporate
> your changes into the live site from there.
>
>
> HTH
>
>
>
> ----- Original Message -----
>> From: Ric Gaudet<ricgaudet@hotmail.com>
>> To: ooo-dev@incubator.apache.org
>> Cc:
>> Sent: Wednesday, February 8, 2012 1:22 PM
>> Subject: Bad Link on OOO API Web Page
>>
>>
>> Hi,
>>
>> I found a link on this page that is bad:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/module-ix.html
>>
>>
>>
>>
>> The link is to the tag "fieldmaster" located in the "Nested
>> Modules" area
>> The current link:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/fieldmaster/module-ix.html
>>
>>
>>
>>
>> should instead be:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/FieldMaster/module-ix.html
>>
>> the difference being "FieldMaster" vs. "fieldmaster".
>> However, since the module's name is actually "fieldmaster",
>> perhaps the page  url containing that content should instead be lowercase.
>> I am still a beginner to Uno, so I have not yet figured out all the naming
>> conventions (or even how to navigate easily through the API!).
>> Thanks,
>> Ric Gaudet
>>