incubator-ooo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jürgen Schmidt <jogischm...@googlemail.com>
Subject Re: [PATCH] fieldmaster
Date Fri, 10 Feb 2012 10:34:30 GMT
On 2/9/12 6:40 PM, Dave Fisher wrote:
>
> On Feb 9, 2012, at 9:13 AM, Andrew Rist wrote:
>
>>
>>
>> On 2/8/2012 11:52 PM, Jürgen Schmidt wrote:
>>> On 2/9/12 3:40 AM, Dave Fisher wrote:
>>>> In this case there is more than one file to patch in that directory. There
are possibly more. I'm committing the following and investigating the rest.
>>>>
>>>
>>> I mentioned in already in another email, it's a bad example to explain how to
make minor changes on our web-sites. The mentioned link problem is on generated page and the
source for this comes directly fro our IDL files.
>>>
>>> And the problem is already fixed in the generated reference docu which is part
of the built SDK.
>>>
>>> I will rpelace the whole IDL refernece when we have the 3.4 available.
>> Where is this in the build tree? I can upload it as part of the nightly.  Not looking
to have this be the main destination for this info, just a snapshot of the current state.
>
the IDL reference will be generated as part of the SDK in the module 
"odk". The C++ and Java UNO runtime reference is generated there as well.

> We can then target it into the podling site somehow.
>
> (1) Checkout the api part of the site.
> (2) Generate the IDL.
can be copied from the SDK build. It's in the output directory of the 
module odk and you will find the same directory structure as under the 
api project
../docs/common/ref
../docs/cpp/ref
../docs/java/ref

> (3) Process svn status to remove, add and commit triggering podling site rebuild - followed
by publish.pl. AND/OR, it will involve learning svnpubsub.
>
> We will need a similar process for a release build of the IDL. We'll need to decide if
the IDL goes in a Source Release.
the IDL files will be part of the source release but I don't think that 
we should include the generated reference documentation. But it would be 
good to have a mechanism to update the available online reference for 
every new release. I did that in the past always after a new release.

And of course it's part of the SDK and that is probably the place where 
potential consumers will look for it if they don't use the online reference

Juergen
>
> I'm willing to help with this.
>
> Regards,
> Dave
>
>> A.
>>>
>>> Juergen
>>>
>>>
>>>> Regards,
>>>> Dave
>>>>
>>>> Index: TextFieldMaster-xref.html
>>>> ===================================================================
>>>> --- TextFieldMaster-xref.html    (revision 1242205)
>>>> +++ TextFieldMaster-xref.html    (working copy)
>>>> @@ -41,11 +41,11 @@
>>>> <td class="subtitle">Services which Include this Service</td>
>>>> </tr>
>>>> <tr>
>>>> -<td>::com::sun::star::text::<a href="fieldmaster/module-ix.html">fieldmaster</a>::<a
href="fieldmaster/Bibliography.html">Bibliography</a><br>
>>>> -::com::sun::star::text::<a href="fieldmaster/module-ix.html">fieldmaster</a>::<a
href="fieldmaster/Database.html">Database</a><br>
>>>> -::com::sun::star::text::<a href="fieldmaster/module-ix.html">fieldmaster</a>::<a
href="fieldmaster/DDE.html">DDE</a><br>
>>>> -::com::sun::star::text::<a href="fieldmaster/module-ix.html">fieldmaster</a>::<a
href="fieldmaster/SetExpression.html">SetExpression</a><br>
>>>> -::com::sun::star::text::<a href="fieldmaster/module-ix.html">fieldmaster</a>::<a
href="fieldmaster/User.html">User</a><br>
>>>> +<td>::com::sun::star::text::<a href="FieldMaster/module-ix.html">FieldMaster</a>::<a
href="FieldMaster/Bibliography.html">Bibliography</a><br>
>>>> +::com::sun::star::text::<a href="FieldMaster/module-ix.html">FieldMaster</a>::<a
href="FieldMaster/Database.html">Database</a><br>
>>>> +::com::sun::star::text::<a href="FieldMaster/module-ix.html">FieldMaster</a>::<a
href="FieldMaster/DDE.html">DDE</a><br>
>>>> +::com::sun::star::text::<a href="FieldMaster/module-ix.html">FieldMaster</a>::<a
href="FieldMaster/SetExpression.html">SetExpression</a><br>
>>>> +::com::sun::star::text::<a href="FieldMaster/module-ix.html">FieldMaster</a>::<a
href="FieldMaster/User.html">User</a><br>
>>>> </td>
>>>> </tr>
>>>> </table>
>>>> Index: module-ix.html
>>>> ===================================================================
>>>> --- module-ix.html    (revision 1242205)
>>>> +++ module-ix.html    (working copy)
>>>> @@ -52,7 +52,7 @@
>>>> <td class="subtitle" colspan="2">Nested Modules</td>
>>>> </tr>
>>>> <tr>
>>>> -<td class="imsum_left"><a href="fieldmaster/module-ix.html">fieldmaster</a></td>
>>>> +<td class="imsum_left"><a href="FieldMaster/module-ix.html">FieldMaster</a></td>
>>>> <td class="imsum_right"/></tr>
>>>> <tr>
>>>> <td class="imsum_left"><a href="textfield/module-ix.html">textfield</a></td>
>>>>
>>>>
>>>> On Feb 8, 2012, at 6:22 PM, Joe Schaefer wrote:
>>>>
>>>>> Well no, but the beauty of svn is that you only need
>>>>> to deal with the section of the tree you are interested
>>>>> in.  So don't check-out all of ooo-site just to apply this
>>>>> tiny patch- look at the patch to see which directory
>>>>> it applies to and just check-out THAT.
>>>>>
>>>>>
>>>>> Applying the patch is a matter of cd'ing to that
>>>>> directory and running
>>>>>
>>>>> % patch<   path/to/email/msg.txt
>>>>> % svn commit -m 'apply fieldmaster patch'
>>>>>
>>>>>
>>>>> ----- Original Message -----
>>>>>> From: Rob Weir<robweir@apache.org>
>>>>>> To: ooo-dev@incubator.apache.org
>>>>>> Cc:
>>>>>> Sent: Wednesday, February 8, 2012 9:17 PM
>>>>>> Subject: Re: [PATCH] fieldmaster
>>>>>>
>>>>>> On Wed, Feb 8, 2012 at 3:22 PM, Joe Schaefer<joe_schaefer@yahoo.com>
>>>>>> wrote:
>>>>>>> No idea if this is sufficient Ric, but I used the CMS
>>>>>>> to email this patch as I explained earlier.
>>>>>>>
>>>>>>
>>>>>> Cool.  But unless we have more committers download ooo-site and set
up
>>>>>> an off-line site build environment, these patches are going to be
slow
>>>>>> to integrate.  I'm guilty as well.  I'll find some time to get this
>>>>>> set up on my machine.
>>>>>>
>>>>>> Or is there any easier way to suck these patches into the CMS?  For
>>>>>> example, it would be really cool if there was an "upload/apply patch"
>>>>>> button in the CMS "edit" view.  That would enable any committer to
>>>>>> review and apply site patches, even the ones not comfortable with
SVN
>>>>>> and command-line tools.
>>>>>>
>>>>>> -Rob
>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> ----- Original Message -----
>>>>>>>> From: Joe Schaefer<joes@apache.org>
>>>>>>>> To: ooo-dev@incubator.apache.org
>>>>>>>> Cc:
>>>>>>>> Sent: Wednesday, December 31, 1969 7:00 PM
>>>>>>>> Subject: [PATCH] fieldmaster
>>>>>>>>
>>>>>>>> Here's the patch for Ric's issue.
>>>>>>> ...
>>>>>>>
>>>>>>
>>>>
>>>
>>
>> --
>>
>> Andrew Rist | Interoperability Architect
>> OracleCorporate Architecture Group
>> Redwood Shores, CA | 650.506.9847
>>
>


Mime
View raw message