Re: [RELEASE]: new snapshot based on rev. 1484675

[Jürgen Schmidt]

On 5/21/13 10:13 AM, Jürgen Schmidt wrote:
> Hi,
> 
> I have moved the snapshot tag to trunk revision 1484675 and propose
> hereby a new snapshot build based on the SNAPSHOT tag.
> 
> After this snapshot I will start to include the translations (that are
> already finished) in the snapshots. We will have one minor translation
> updated as mentioned last week. And Regina is working on a help file for
> the sidebar which will be integrated potentially as well. That means one
> potentially further update in the help project.
> 

trunk revision 1484675 corresponds to snapshot revision 1484679.

MacOS and Windows are already uploaded

http://people.apache.org/~jsc/developer-snapshots/snapshot/macos/Apache_OpenOffice_4.0.0_MacOS_x86_install_en-US.dmg

http://people.apache.org/~jsc/developer-snapshots/snapshot/windows/Apache_OpenOffice_4.0.0_Win_x86_install_en-US.exe

Juergen


PS: the builds are there since yesterday but the mail got lost

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

Re: Layout improvements (Re: [Pootle]Different behaviour on different browsers)

[Herbert Dürr]

On 2013/05/19 12:16 AM, Andrea Pescetti wrote:

On 16/05/2013 Ariel Constenla-Haile wrote:

On Thu, May 16, 2013 at 03:41:11PM +0200, Jürgen Schmidt wrote:

a more generic layout engine for
VCL. Thinking of an extended or modified format to describe dialogs
and include layout info/constraints that are used by the layout engine
etc.

Christian Lippka had this almost finished. I recall the picture from
this thread
http://www.mail-archive.com/dev@de.openoffice.org/msg30669.html it had
a side panel defined in xml. It would be interesting to investigate if
the work was done on some private repository in Hamburg, or if it is in
some CWS on http://hg.services.openoffice.org/; and rescue it, avoiding
to reinvent the wheel.
He was also doing a nice job with the svtools::ToolbarMenu in the
toolbar controllers: http://www.youtube.com/watch?v=_eO0X_eO6Ww


Christian is an Apache OpenOffice committer and already contributed his
improved color picker to Apache OpenOffice, so if he wants he can merge
his improvements any time.

The video seems to be from the "Renaissance4" CWS, still in HG. I
absolutely don't know whether this CWS contains the layout engine
improvement too, though.


I talked to Christian and he confirmed that the video was from the
code in the http://hg.services.openoffice.org/cws/renaissance4/
child workspace.

He doesn't think that the XML-defined sidepanel work got far enough to 
be worth picking.


I'm afraid Christian is too busy in his new job to work further on such 
OpenOffice topics, but everyone knows him to be very constructive and 
cooperative.


I'm BCC'ing him in case he wants to jump in. Hi Christian! :-)

Herbert

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

Self Intro.

[manoj elangovan]

Hi,

Manoj , from Bangalore India.
I am intrested in learning this product. I am beginner to open source
contribution.

Thanks,
Manoj

-- 
Thanks,
Manoj

Re: [buildbot] investigate nightly windows build

[Oliver-Rainer Wittmann]

Hi,

On 21.05.2013 09:53, Oliver-Rainer Wittmann wrote:

Hi,

On 17.05.2013 23:11, Andrew Rist wrote:


[snip]



I have seen that #621 of aoo-win7 also had this error and that you had
again cleaned up the hanging processes.

In order to get some error output I will switch off the HTML output (no
"--html" option) and the multiprocessor build (no "-P2 -- -P2" options)
before the weekly clean build of aoo-win7 and for the aoo-w7ia2 build
which is always clean.



Build #113 of aoo-w7ia2 went well.
The failure occured just because I forgot to disable the collection of 
the HTML build logs.


May be the former errors are related to the multiprocessor build.
I will switch on the multiprocessor build inside each module - "-- -P2" 
option for the next build.


Best regards, Oliver.

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

[RELEASE][TRANSLATION]: last update on UI project triggers again some reviews and changes

[Jürgen Schmidt]

Hi,

it seems that I am the bearer of bad messages ;-) But you can believe me
it's no fun for me as well to update this again and again. And it is the
last "planned" update for AOO 4.0

We discussed some further changes on the About dialog, README, some last
changes in the context of the sidebar ... and I did an update on the
translation source files.

I have already updated the AOO4.0 UI project on the Pootle server and
the po files are available under http://people.apache.org/~jsc/translation/

I also have updated the extensions/source/preload.po for most languages
already because it were 2 minor changes only, one url and a name change.

I apologize in the name of the project to all volunteers who have to
review again some strings. I hope we can improve the localization
process in the future to minimize the effort for all of you.

We should now focus to complete as many as possible languages for 4.0. I
will include completed languages in the snapshots for more detailed testing.

Juergen




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

Re: Writing script for compilation AOO on GNU/Linux

[Andre Fischer]

On 22.05.2013 08:41, Andrea Pescetti wrote:

On 17/05/2013 Albino B Neto wrote:

I am writing a script [1] for compilation AOO on GNU/Linux.
1 - https://github.com/binoanb/scripts/blob/master/compilar_aoo4.sh


I think the main difficulty for people who build for their first time 
under Linux is getting all build dependencies right. We needn't 
automate the classic autoconf/configure/bootstrap/build part, or at 
least this is something that someone who wants to build OpenOffice 
should be prepared to do.


So I see the main value here in providing the proper "yum install" / 
"apt-get install" command (in a wiki page or in a script, but the wiki 
page could be enough) to get dependencies right for the most popular 
distributions.


Wiki pages:

for Ubuntu 12.04:
http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Step_by_step#Ubuntu_12.04

for other distributions (probably not quite up-to-date anymore):
http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO/Building_on_Linux

-Andre



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

Re: Writing script for compilation AOO on GNU/Linux

[janI]

On 22 May 2013 13:18, Andre Fischer  wrote:

> On 22.05.2013 08:41, Andrea Pescetti wrote:
>
>> On 17/05/2013 Albino B Neto wrote:
>>
>>> I am writing a script [1] for compilation AOO on GNU/Linux.
>>> 1 - 
>>> https://github.com/binoanb/**scripts/blob/master/compilar_**aoo4.sh
>>>
>>
>> I think the main difficulty for people who build for their first time
>> under Linux is getting all build dependencies right. We needn't automate
>> the classic autoconf/configure/bootstrap/**build part, or at least this
>> is something that someone who wants to build OpenOffice should be prepared
>> to do.
>>
>> So I see the main value here in providing the proper "yum install" /
>> "apt-get install" command (in a wiki page or in a script, but the wiki page
>> could be enough) to get dependencies right for the most popular
>> distributions.
>>
>
> Wiki pages:
>
> for Ubuntu 12.04:
> http://wiki.openoffice.org/**wiki/Documentation/Building_**
> Guide_AOO/Step_by_step#Ubuntu_**12.04
>
> The 12.04 is also not quite updated. I had a problem with epm (see
https://issues.apache.org/ooo/show_bug.cgi?id=121290), The epm package in
12.04 is never than what our configure expect, so it does not try to
download AND patch a versionmeaning the last build step goes wrong
because of an unpatched epm.

The right solution would be to change the build to use a "normal" epm, but
admitted I was lazy and simply removed the ubuntu supplied epm.

rgds
jan I.

for other distributions (probably not quite up-to-date anymore):
> http://wiki.openoffice.org/**wiki/Documentation/Building_**
> Guide_AOO/Building_on_Linux
>
> -Andre
>
>
>
>> Regards,
>>   Andrea.
>>
>> --**--**-
>> To unsubscribe, e-mail: 
>> dev-unsubscribe@openoffice.**apache.org
>> For additional commands, e-mail: dev-h...@openoffice.apache.org
>>
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

mac build bot (and also for the rest of us).

[janI]

Hi.

I have been strugling to get VMs up and running on my local server, so I
can test my changes throughout our supported platforms.

I found this article:
http://lifehacker.com/5583650/run-mac-os-x-in-virtualbox-on-windows

And have talked to a couple of virtualbox people, it actually worksso
this is a recipe to get macOS without having a mac.

Now I need to find a macOS image, but that is different story.

rgds
jan I.

Re: mac build bot (and also for the rest of us).

[Andre Fischer]

On 22.05.2013 14:01, janI wrote:

Hi.

I have been strugling to get VMs up and running on my local server, so I
can test my changes throughout our supported platforms.

I found this article:
http://lifehacker.com/5583650/run-mac-os-x-in-virtualbox-on-windows

And have talked to a couple of virtualbox people, it actually worksso
this is a recipe to get macOS without having a mac.


This may be technically possible, but is it legal?  I thought that the 
MacOSX license only allows to run MacOSX on a virtual machine that runs 
itself on MacOSX.  Does anybody know more?


-Andre



Now I need to find a macOS image, but that is different story.

rgds
jan I.




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

Re: Help needed! questions and confusion about "partial build" information

[Andre Fischer]

On 22.05.2013 00:04, Kay Schenk wrote:

We are seeing a fair number of folks who want to work on a specific aspect
or module of AOO. This is not unexpected, of course.

This is the information for how to do partial builds from the new Build
Guide:

[1]
http://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO#Partial_Builds

This is the information from the old Tools information:

[2a] http://www.openoffice.org/tools/build_env_tools.html
[2b] http://www.openoffice.org/tools/tools/build.html

I actually used the  "build --all:" for what I was doing...

So my questions.

I don't know if new developers should necessarily know if a change is
compatible or not.
Would just ONE set of instructions in the Building Guide work for both
cases?


Well, yes.  You can always do a clean build.  But that is probably not 
what you mean.  But: the motivation to do a compatible build is to have 
turn around times as small as possible.  This can only be achieved by


a) improving our build system or

b) by taking shortcuts

Option b) requires you to provide additional knowledge.  That is usually 
of the form: I changed file X.cxx in  but I know/believe/are 
fairly certain that only library Y.dll has to be rebuild and nothing 
else.  Afterwards you have to copy Y.dll (or Y.so or Y.dylib ...) into 
your office installation.
In other words, you have to know what you are doing.  Otherwise use the 
standard mechanism and be patient :-)


I agree that this should be better documented.  Both the technical steps 
(building one directory/library, copying this library into an installed 
office) and the rules of thumb when to build just one library or a whole 
module or everything.




...and

Would the dmake instructions work for both dmake and make? (Something I
think is probably another point of confusion for new developers.)


To some degree we already have that.  For example call 'build debug=t' 
in the top-level directory of a dmake or gbuild module and the module is 
built with debug information.


-Andre



...and

Could we use a syntax that is more like what is found in [2b] for all cases?






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

Re: Help needed! questions and confusion about "partial build" information

[janI]

On 22 May 2013 16:00, Andre Fischer  wrote:

> On 22.05.2013 00:04, Kay Schenk wrote:
>
>> We are seeing a fair number of folks who want to work on a specific aspect
>> or module of AOO. This is not unexpected, of course.
>>
>> This is the information for how to do partial builds from the new Build
>> Guide:
>>
>> [1]
>> http://wiki.openoffice.org/**wiki/Documentation/Building_**
>> Guide_AOO#Partial_Builds
>>
>> This is the information from the old Tools information:
>>
>> [2a] 
>> http://www.openoffice.org/**tools/build_env_tools.html
>> [2b] 
>> http://www.openoffice.org/**tools/tools/build.html
>>
>> I actually used the  "build --all:" for what I was doing...
>>
>> So my questions.
>>
>> I don't know if new developers should necessarily know if a change is
>> compatible or not.
>> Would just ONE set of instructions in the Building Guide work for both
>> cases?
>>
>
> Well, yes.  You can always do a clean build.  But that is probably not
> what you mean.  But: the motivation to do a compatible build is to have
> turn around times as small as possible.  This can only be achieved by
>
> a) improving our build system or
>
> b) by taking shortcuts
>
> Option b) requires you to provide additional knowledge.  That is usually
> of the form: I changed file X.cxx in  but I know/believe/are fairly
> certain that only library Y.dll has to be rebuild and nothing else.
>  Afterwards you have to copy Y.dll (or Y.so or Y.dylib ...) into your
> office installation.
> In other words, you have to know what you are doing.  Otherwise use the
> standard mechanism and be patient :-)
>
> I agree that this should be better documented.  Both the technical steps
> (building one directory/library, copying this library into an installed
> office) and the rules of thumb when to build just one library or a whole
> module or everything.
>
>
>> ...and
>>
>> Would the dmake instructions work for both dmake and make? (Something I
>> think is probably another point of confusion for new developers.)
>>
>
> To some degree we already have that.  For example call 'build debug=t' in
> the top-level directory of a dmake or gbuild module and the module is built
> with debug information.
>
> -Andre
>

I might be lazy, but when even if I only change a single file, I run build
--all, please remember in many cases (not all modules).

I have ubuntu running in virtualbox with win7 as host (ugly I know it), and
build -all take 4minutes 12 seconds...and then I am sure everything is
correct.

rgds
jan I.


>
>> ...and
>>
>> Could we use a syntax that is more like what is found in [2b] for all
>> cases?
>>
>>
>>
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: Help needed! questions and confusion about "partial build" information

[Kay Schenk]

On Wed, May 22, 2013 at 7:00 AM, Andre Fischer  wrote:

> On 22.05.2013 00:04, Kay Schenk wrote:
>
>> We are seeing a fair number of folks who want to work on a specific aspect
>> or module of AOO. This is not unexpected, of course.
>>
>> This is the information for how to do partial builds from the new Build
>> Guide:
>>
>> [1]
>> http://wiki.openoffice.org/**wiki/Documentation/Building_**
>> Guide_AOO#Partial_Builds
>>
>> This is the information from the old Tools information:
>>
>> [2a] 
>> http://www.openoffice.org/**tools/build_env_tools.html
>> [2b] 
>> http://www.openoffice.org/**tools/tools/build.html
>>
>> I actually used the  "build --all:" for what I was doing...
>>
>> So my questions.
>>
>> I don't know if new developers should necessarily know if a change is
>> compatible or not.
>> Would just ONE set of instructions in the Building Guide work for both
>> cases?
>>
>
> Well, yes.  You can always do a clean build.  But that is probably not
> what you mean.


no...it isn't. I guess I didn't make myself clear.

In the current "new" Building Guide [1], there are different build
instructions for "Compatible" vs "Incompatible" builds.

There is also this statement:

IncompatibleUse for code changes that modify exported C++ or IDL
interfaces, that modify resources that are used by other modules, or when
you are not sure.

What I'm saying is that I would think new developers would always use
instructions for "Incompatible" build because it is likely they are not
sure. So, we can change the wording to somehow explain this.


Ok, so we can deal with this aspect.


What about the dmake vs make business? Or, should the "Compatible" build
information be put someplace else -- like in "Advanced Topics" or
something, toward the bottom? Maybe I will just make these kinds of changes
and see what everyone thinks. :/




>  But: the motivation to do a compatible build is to have turn around times
> as small as possible.  This can only be achieved by
>
> a) improving our build system or
>
> b) by taking shortcuts
>
> Option b) requires you to provide additional knowledge.  That is usually
> of the form: I changed file X.cxx in  but I know/believe/are fairly
> certain that only library Y.dll has to be rebuild and nothing else.
>  Afterwards you have to copy Y.dll (or Y.so or Y.dylib ...) into your
> office installation.
> In other words, you have to know what you are doing.  Otherwise use the
> standard mechanism and be patient :-)
>
> I agree that this should be better documented.  Both the technical steps
> (building one directory/library, copying this library into an installed
> office)


AHA! Yes, we are definitely missing this piece! OK, I will make changes to
the current Building Guide, and put in a section for this, which,
hopefully, someone can augment with this very important information.


> and the rules of thumb when to build just one library or a whole module or
> everything.


Agreed...thanks for your input.


>
>
>> ...and
>>
>> Would the dmake instructions work for both dmake and make? (Something I
>> think is probably another point of confusion for new developers.)
>>
>
> To some degree we already have that.  For example call 'build debug=t' in
> the top-level directory of a dmake or gbuild module and the module is built
> with debug information.
>
> -Andre
>
>
>
>> ...and
>>
>> Could we use a syntax that is more like what is found in [2b] for all
>> cases?
>>
>>
>>
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>


-- 

MzK

"You can't believe one thing and do another.
 What you believe and what you do are the same thing."
 -- Leonard Peltier

Re: Help needed! questions and confusion about "partial build" information

[Andre Fischer]

On 22.05.2013 16:25, janI wrote:

On 22 May 2013 16:00, Andre Fischer  wrote:


On 22.05.2013 00:04, Kay Schenk wrote:


We are seeing a fair number of folks who want to work on a specific aspect
or module of AOO. This is not unexpected, of course.

This is the information for how to do partial builds from the new Build
Guide:

[1]
http://wiki.openoffice.org/**wiki/Documentation/Building_**
Guide_AOO#Partial_Builds

This is the information from the old Tools information:

[2a] 
http://www.openoffice.org/**tools/build_env_tools.html
[2b] 
http://www.openoffice.org/**tools/tools/build.html

I actually used the  "build --all:" for what I was doing...

So my questions.

I don't know if new developers should necessarily know if a change is
compatible or not.
Would just ONE set of instructions in the Building Guide work for both
cases?


Well, yes.  You can always do a clean build.  But that is probably not
what you mean.  But: the motivation to do a compatible build is to have
turn around times as small as possible.  This can only be achieved by

a) improving our build system or

b) by taking shortcuts

Option b) requires you to provide additional knowledge.  That is usually
of the form: I changed file X.cxx in  but I know/believe/are fairly
certain that only library Y.dll has to be rebuild and nothing else.
  Afterwards you have to copy Y.dll (or Y.so or Y.dylib ...) into your
office installation.
In other words, you have to know what you are doing.  Otherwise use the
standard mechanism and be patient :-)

I agree that this should be better documented.  Both the technical steps
(building one directory/library, copying this library into an installed
office) and the rules of thumb when to build just one library or a whole
module or everything.



...and

Would the dmake instructions work for both dmake and make? (Something I
think is probably another point of confusion for new developers.)


To some degree we already have that.  For example call 'build debug=t' in
the top-level directory of a dmake or gbuild module and the module is built
with debug information.

-Andre


I might be lazy, but when even if I only change a single file, I run build
--all, please remember in many cases (not all modules).


Yes, that is the safe way.  And if you make an incompatible change it 
still may not be enough.  If you really want to be on the safe side then 
you should do a 'build --prepare --from ' first.




I have ubuntu running in virtualbox with win7 as host (ugly I know it), and
build -all take 4minutes 12 seconds...and then I am sure everything is
correct.


1) There are cases of incompatible changes where 'build --all' would not 
be enough


2) When you change a file that eg requires sw to be rebuild then even on 
Linux it will probably take longer.


3) On Windows takes a lot longer.  And if you do a lot of debugging then 
the Window platform with its Developer Studio becomes a lot more attractive.


4) 4 minutes is still a long time to wait when you do it often enough.

-Andre



rgds
jan I.



...and

Could we use a syntax that is more like what is found in [2b] for all
cases?





--**--**-
To unsubscribe, e-mail: 
dev-unsubscribe@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

Is 3.4.1 still "incubating"?

[Donald Whytock]

I see on the downloads page (http://openoffice.apache.org/downloads.html)
that the current version is listed as "*Current Version 3.4.1
(incubating)".  *Since 3.4.1 is the current official release, and since
"incubating" has more to do with Apache internal policies than the release
itself, should the release still be called "(incubating)"?

Could shorten the actual filenames too, but I suppose we're stuck with
those for now...?

Don

Need commit help

[Regina Henschel]

Hi,

with commit http://svn.apache.org/r1485263 I have got the message

Propchange: 
openoffice/trunk/main/helpcontent2/source/text/shared/guide/sidebar_window.xhp

--
svn:executable = *

Is all okay or do I have something to do?

Kind regards
Regina

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

Re: Is 3.4.1 still "incubating"?

[Raphael Bircher]

Am 22.05.13 18:04, schrieb Donald Whytock:

I see on the downloads page (http://openoffice.apache.org/downloads.html)
that the current version is listed as "*Current Version 3.4.1
(incubating)".  *Since 3.4.1 is the current official release, and since
"incubating" has more to do with Apache internal policies than the release
itself, should the release still be called "(incubating)"?
I don't think so, The incubating release is released by the incubator, 
not by the project. The PPMC votes ar no binding votes.


Greetings Raphael

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

Re: Need commit help

[Ariel Constenla-Haile]

Hi Regina,

On Wed, May 22, 2013 at 06:10:23PM +0200, Regina Henschel wrote:
> Hi,
> 
> with commit http://svn.apache.org/r1485263 I have got the message
> 
> Propchange: 
> openoffice/trunk/main/helpcontent2/source/text/shared/guide/sidebar_window.xhp
> --
> svn:executable = *
> 
> Is all okay or do I have something to do?

This means it was committed with the executable bit on:

[ariel@localhost trunk]$ ls -l 
main/helpcontent2/source/text/shared/guide/sidebar_window.xhp
-rwxrwxr-x. 1 ariel ariel 11266 May 22 13:14 
main/helpcontent2/source/text/shared/guide/sidebar_window.xhp


According to subversion manual, you have to 

svn propdel svn:executable 

Are you using subversion or git-svn?


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpXmuVydZUtg.pgp
Description: PGP signature

Re: Need commit help

[Regina Henschel]

Hi Ariel,

Ariel Constenla-Haile schrieb:

Hi Regina,

On Wed, May 22, 2013 at 06:10:23PM +0200, Regina Henschel wrote:

Hi,

with commit http://svn.apache.org/r1485263 I have got the message

Propchange: 
openoffice/trunk/main/helpcontent2/source/text/shared/guide/sidebar_window.xhp
--
 svn:executable = *

Is all okay or do I have something to do?


This means it was committed with the executable bit on:

[ariel@localhost trunk]$ ls -l 
main/helpcontent2/source/text/shared/guide/sidebar_window.xhp
-rwxrwxr-x. 1 ariel ariel 11266 May 22 13:14 
main/helpcontent2/source/text/shared/guide/sidebar_window.xhp


How can I correct it? I think a .xhp file should not be executable.




According to subversion manual, you have to

svn propdel svn:executable 

Are you using subversion or git-svn?


I use git-svn. How can I avoid such problem?

Kind regards
Regina


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

Re: Need commit help

[Regina Henschel]

Hi Ariel,

thank you for correcting it.

I have seen the wrong flag in my local source now. I hope, I remember 
next time, that inside Cygwin is not Windows and I have to use "ls -l" 
and not "dir".


Kind regards
Regina


Ariel Constenla-Haile schrieb:

Hi Regina,

On Wed, May 22, 2013 at 06:10:23PM +0200, Regina Henschel wrote:

Hi,

with commit http://svn.apache.org/r1485263 I have got the message

Propchange: 
openoffice/trunk/main/helpcontent2/source/text/shared/guide/sidebar_window.xhp
--
 svn:executable = *

Is all okay or do I have something to do?


This means it was committed with the executable bit on:

[ariel@localhost trunk]$ ls -l 
main/helpcontent2/source/text/shared/guide/sidebar_window.xhp
-rwxrwxr-x. 1 ariel ariel 11266 May 22 13:14 
main/helpcontent2/source/text/shared/guide/sidebar_window.xhp


According to subversion manual, you have to

svn propdel svn:executable 

Are you using subversion or git-svn?


Regards




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

Re: mac build bot (and also for the rest of us).

[janI]

On 22 May 2013 15:42, Andre Fischer  wrote:

> On 22.05.2013 14:01, janI wrote:
>
>> Hi.
>>
>> I have been strugling to get VMs up and running on my local server, so I
>> can test my changes throughout our supported platforms.
>>
>> I found this article:
>> http://lifehacker.com/5583650/**run-mac-os-x-in-virtualbox-on-**windows
>>
>> And have talked to a couple of virtualbox people, it actually worksso
>> this is a recipe to get macOS without having a mac.
>>
>
> This may be technically possible, but is it legal?  I thought that the
> MacOSX license only allows to run MacOSX on a virtual machine that runs
> itself on MacOSX.  Does anybody know more?
>

At least you can buy it (one example):
http://store.apple.com/us/product/MC573Z/A/mac-os-x-106-snow-leopard
and I dont think apple can dictate you which machines you run it on

rgds
jan I

>
> -Andre
>
>
>
>> Now I need to find a macOS image, but that is different story.
>>
>> rgds
>> jan I.
>>
>>
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Just an idea for the AOO UI

[Guy Waterval]

Hi all,

For some users who don't use AOO  intensively, the software can sometimes
seem difficult to take in hands due to its  many features, and those people
may feel easily  "a little lost."
I am often asked if it could possible or not to manage three levels of
users through three different folders  profiles. Since I'm not a
programmer, I'm just wondering if an extension could take care of that by
installing three different profiles and allowing the user to switch from
one profile to another depending on the level of his expertise with the
software or as he  wants to do a work requiring no advanced features.  In
fact, there would be nothing really deleted in the application, simply
hidden features according to the user level.
I have used  in the past a PIM that worked like that, it was very nice.
Please, consider that this is not a feature request, I'm just trying to
find out about the difficulty of achieving such functionality.

A+
-- 
gw

Re: Need commit help

[Ariel Constenla-Haile]

Hi Regina,

On Wed, May 22, 2013 at 06:42:27PM +0200, Regina Henschel wrote:
> >This means it was committed with the executable bit on:
> >
> >[ariel@localhost trunk]$ ls -l 
> >main/helpcontent2/source/text/shared/guide/sidebar_window.xhp
> >-rwxrwxr-x. 1 ariel ariel 11266 May 22 13:14 
> >main/helpcontent2/source/text/shared/guide/sidebar_window.xhp
> 
> How can I correct it? I think a .xhp file should not be executable.

I corrected it with http://svn.apache.org/r1485289

Note that if using subversion, one should avoid (according to the
manual) using chmod +x / chmod -x, but with git-svn this works,
svn:executable is the only  SVN property not ignored
(https://www.kernel.org/pub/software/scm/git/docs/git-svn.html).

So the steps to fix an already committed file:

[ariel@localhost trunk]$ chmod -x 
main/helpcontent2/source/text/shared/guide/sidebar_window.xhp
[ariel@localhost trunk]$ git commit -a --message="Remove executable bit"
[ariel@localhost trunk]$ git svn dcommit

The -x removes the executable bit.

> >Are you using subversion or git-svn?
> 
> I use git-svn. How can I avoid such problem?

If you want to avoid this before committing, you can make a pre-commit
hook (this is a script that is run before committing and aborts the
commit if it returns error code), or perform some checks manually;
searching in Google for "git windows executable bit" gives several
results, this seems a common problem on Win; for example
https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium-dev/0EdNev3NNsw
which suggests setting

git config core.filemode false


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpDLcSPr1v4X.pgp
Description: PGP signature

Re: mac build bot (and also for the rest of us).

[Tsutomu Uchino]

Hi,

2013/5/22, Andre Fischer :
> On 22.05.2013 14:01, janI wrote:
>> Hi.
>>
>> I have been strugling to get VMs up and running on my local server, so I
>> can test my changes throughout our supported platforms.
>>
>> I found this article:
>> http://lifehacker.com/5583650/run-mac-os-x-in-virtualbox-on-windows
>>
>> And have talked to a couple of virtualbox people, it actually worksso
>> this is a recipe to get macOS without having a mac.
>
> This may be technically possible, but is it legal?  I thought that the
> MacOSX license only allows to run MacOSX on a virtual machine that runs
> itself on MacOSX.  Does anybody know more?
License agreements for Apple softwares can be found in:
http://www.apple.com/legal/sla/
For MacOSX 10.8.2: http://images.apple.com/legal/sla/docs/OSX1082.pdf
The section 2 (starting at the end of first page) describes about the
valid use of
the copy of the OS. It always says on "Apple-branded computer".
So we need it, it seems.
>
> -Andre
>
>>
>> Now I need to find a macOS image, but that is different story.
>>
>> rgds
>> jan I.
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>
-Tsutomu

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

Re: mac build bot (and also for the rest of us).

[Alexander Thurgood]

Le 22/05/13 19:30, janI a écrit :

Hi all,

> 
> At least you can buy it (one example):
> http://store.apple.com/us/product/MC573Z/A/mac-os-x-106-snow-leopard
> and I dont think apple can dictate you which machines you run it on
> 

It doesn't matter whether you can buy it, what you can do with it is in
the Terms & Conditions of the licence agreement, and last time I read
them (Lion upgrade), such a system (i.e. a VM running OSX on non-Apple
hardware) wasn't allowed. That may have changed of course.


Alex


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

Re: [buildbot] investigate nightly windows build

[Andrew Rist]

On 5/22/2013 3:30 AM, Oliver-Rainer Wittmann wrote:

Hi,

On 21.05.2013 09:53, Oliver-Rainer Wittmann wrote:

Hi,

On 17.05.2013 23:11, Andrew Rist wrote:


[snip]



I have seen that #621 of aoo-win7 also had this error and that you had
again cleaned up the hanging processes.

In order to get some error output I will switch off the HTML output (no
"--html" option) and the multiprocessor build (no "-P2 -- -P2" options)
before the weekly clean build of aoo-win7 and for the aoo-w7ia2 build
which is always clean.



Build #113 of aoo-w7ia2 went well.
The failure occured just because I forgot to disable the collection of 
the HTML build logs.
I'm confused - was there something wrong with the w7ia2 build.  The 
previous two builds were clean: http://ci.apache.org/builders/aoo-w7ia2
Other than stumbling over hung processes, I don't think there is an 
issue with ia2.

A.




May be the former errors are related to the multiprocessor build.
I will switch on the multiprocessor build inside each module - "-- 
-P2" option for the next build.


Best regards, Oliver.

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



--

Andrew Rist | Interoperability Architect
OracleCorporate Architecture Group
Redwood Shores, CA | 650.506.9847

Re: mac build bot (and also for the rest of us).

[Andrew Rist]

I'm pretty sure that is not allowed by the Apple license.  So that 
doesn't solve our problem.
(also, I've not had very good success when trying this type approach in 
the past)


The real solution is to get a Mac buildbot, and we requested this almost 
a year ago: https://issues.apache.org/jira/browse/INFRA-4902


Andrew



On 5/22/2013 5:01 AM, janI wrote:

Hi.

I have been strugling to get VMs up and running on my local server, so I
can test my changes throughout our supported platforms.

I found this article:
http://lifehacker.com/5583650/run-mac-os-x-in-virtualbox-on-windows

And have talked to a couple of virtualbox people, it actually worksso
this is a recipe to get macOS without having a mac.

Now I need to find a macOS image, but that is different story.

rgds
jan I.




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

Re: Self Intro.

[Regina Henschel]

Hi Manoj,

welcome at the Apache OpenOffice project.

manoj elangovan schrieb:

Hi,

Manoj , from Bangalore India.
I am intrested in learning this product. I am beginner to open source
contribution.


We have collected some informations at 
http://openoffice.apache.org/orientation/index.html


Please have look and then tell about which area you would like to learn 
more.


I have CC you, because I don't know, whether you have already subscribed 
to the mailing list.


Kind regards
Regina

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

[Translation] %VARIABLE% thesaurus

[FR web forum]

Hello list,
I'm looking for the meaning of the environment variables.
PRODUCTNAME = Apache OpenOffce
PRODUCTVERSION = ...
etc
Does that exists or not?

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

Re: [Translation] %VARIABLE% thesaurus

[Ariel Constenla-Haile]

Hi,

On Wed, May 22, 2013 at 09:13:08PM +0200, FR web forum wrote:
> Hello list,
> I'm looking for the meaning of the environment variables.
> PRODUCTNAME = Apache OpenOffce
> PRODUCTVERSION = ...
> etc
> Does that exists or not?

Do you mean real environment variables that you can export on a terminal
and affect the program execution? Or these variables that are set at
build time or internally at runtime?


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgpvDVgwfkZQl.pgp
Description: PGP signature

Re: [Translation] %VARIABLE% thesaurus

[FR web forum]

>Do you mean real environment variables that you can export on a terminal
>and affect the program execution? Or these variables that are set at
>build time or internally at runtime?
Sorry, I express myself badly.
Just to clarify sentences translation for Pootle.

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

Re: Is 3.4.1 still "incubating"?

[Marcus (OOo)]

Am 05/22/2013 06:04 PM, schrieb Donald Whytock:

I see on the downloads page (http://openoffice.apache.org/downloads.html)
that the current version is listed as "*Current Version 3.4.1
(incubating)".  *Since 3.4.1 is the current official release, and since
"incubating" has more to do with Apache internal policies than the release
itself, should the release still be called "(incubating)"?


The AOO project was still incubating as the version was released. So, 
it's correct when it is still listed as "incubating".



Could shorten the actual filenames too, but I suppose we're stuck with
those for now...?


It won't work as long as you don't change the filenames on the 
SourceForge servers, their download scripting, our download scripting. 
And believe me, you don't want to do this just for 3.4.1. ;-)


Or do you mean just the displayed filenames? Yes, this could be changed 
but I don't know if it is worth it.


Of course AOO 4.0.0 will be completely different in this regard.

Marcus


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

Re: Is 3.4.1 still "incubating"?

[Juergen Schmidt]

Am Mittwoch, 22. Mai 2013 um 22:16 schrieb Marcus (OOo):
> Am 05/22/2013 06:04 PM, schrieb Donald Whytock:
> > I see on the downloads page (http://openoffice.apache.org/downloads.html)
> > that the current version is listed as "*Current Version 3.4.1
> > (incubating)". *Since 3.4.1 is the current official release, and since
> > "incubating" has more to do with Apache internal policies than the release
> > itself, should the release still be called "(incubating)"?
> > 
> 
> 
> The AOO project was still incubating as the version was released. So, 
> it's correct when it is still listed as "incubating".
> 
> > Could shorten the actual filenames too, but I suppose we're stuck with
> > those for now...?
> > 
> 
> 
> It won't work as long as you don't change the filenames on the 
> SourceForge servers, their download scripting, our download scripting. 
> And believe me, you don't want to do this just for 3.4.1. ;-)
> 
> Or do you mean just the displayed filenames? Yes, this could be changed 
> but I don't know if it is worth it.
> 
> Of course AOO 4.0.0 will be completely different in this regard.

Please, nobody should spend any time on this. It's not worth the effort.

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

Re: [Translation] %VARIABLE% thesaurus

[Ariel Constenla-Haile]

Hi

On Wed, May 22, 2013 at 09:45:41PM +0200, FR web forum wrote:
> >Do you mean real environment variables that you can export on a terminal
> >and affect the program execution? Or these variables that are set at
> >build time or internally at runtime?
> Sorry, I express myself badly.
> Just to clarify sentences translation for Pootle.

For some of those strings there are some generic variables, and in other
cases their meaning is defined in a particular piece of code.

For the cases you quoted, there is a general procedure to handle them.

In Pootle, you may find these variables in strings that come from *.src
files, for example 
https://translate.apache.org/fr/aoo40/translate.html#search=%25FULLPRODUCT&sfields=source,locations
cui/source/dialogs.po has the strings in cui/source/about.src

The most common variables are:

%PRODUCTNAME  "OpenOffice"  
/org.openoffice.Setup/Product/ooName
%FULLPRODUCTNAME  "Apache OpenOffice"   
/org.openoffice.Setup/Product/ooFullname
%PRODUCTVERSION   "4.0.0"   
/org.openoffice.Setup/Product/ooSetupVersion
%ABOUTBOXPRODUCTVERSION   "4.0.0"   
/org.openoffice.Setup/Product/ooSetupVersionAboutBox
%OOOVENDOR"Apache Software Foundation"  
/org.openoffice.Setup/Product/ooVendor

The complete list of variables from resource strings that are replaced at 
runtime is:

%PRODUCT
%FULLPRODUCT
%PRODUCTNAME
%FULLPRODUCTNAME
%PRODUCTVERSION
%ABOUTBOXPRODUCTVERSION
%PRODUCTEXTENSION
%PRODUCTXMLFILEFORMATNAME
%PRODUCTXMLFILEFORMATVERSION
%OOOVENDOR
%WRITERCOMPATIBILITYVERSIONOOO11

It is taken from desktop/source/app/app.cxx.

Desktop::Main() registers void ReplaceStringHookProc( UniString& rStr)
at the resource manager (ResMgr::SetReadStringHook(
ReplaceStringHookProc );) to perform this replacement.

The replacement string is taken from the Office configuration.

In the source code, the configuration files have the variables in the
form of ${VARIABLE_NAME}, these variables are replaced at build time
with strings from variables defined in
instsetoo_native/util/openoffice.lst (or passed to ./configure).

For strings in user interface elements (toolbars, menubar, statusbar)
that are defined in XxxCommands.xcu, only "%PRODUCTNAME" is replaced,
this is done in
framework::ConfigurationAccess_UICommand::fillInfoFromResult().


But in most cases, it is up to the particular code, to set the
variables, for example "Delete %SLIDES slides." in the Presentation
Minimizer code, where %SLIDES is to be replaced be the number of slides
that will be deleted.


Regards
-- 
Ariel Constenla-Haile
La Plata, Argentina


pgph5lt9JAzqZ.pgp
Description: PGP signature

Re: [RELEASE][TRANSLATION]: last update on UI project triggers again some reviews and changes

[RGB ES]

2013/5/22 Jürgen Schmidt 

> Hi,
>
> it seems that I am the bearer of bad messages ;-) But you can believe me
> it's no fun for me as well to update this again and again. And it is the
> last "planned" update for AOO 4.0
>
> We discussed some further changes on the About dialog, README, some last
> changes in the context of the sidebar ... and I did an update on the
> translation source files.
>
> I have already updated the AOO4.0 UI project on the Pootle server and
> the po files are available under
> http://people.apache.org/~jsc/translation/
>
> I also have updated the extensions/source/preload.po for most languages
> already because it were 2 minor changes only, one url and a name change.
>
> I apologize in the name of the project to all volunteers who have to
> review again some strings. I hope we can improve the localization
> process in the future to minimize the effort for all of you.
>
> We should now focus to complete as many as possible languages for 4.0. I
> will include completed languages in the snapshots for more detailed
> testing.
>
> Juergen
>

Working on the ES pootle ;)

Regards
Ricardo



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

Re: [RELEASE][TRANSLATION]: last update on UI project triggers again some reviews and changes

[RGB ES]

2013/5/22 RGB ES 

> 2013/5/22 Jürgen Schmidt 
>
>> Hi,
>>
>> it seems that I am the bearer of bad messages ;-) But you can believe me
>> it's no fun for me as well to update this again and again. And it is the
>> last "planned" update for AOO 4.0
>>
>> We discussed some further changes on the About dialog, README, some last
>> changes in the context of the sidebar ... and I did an update on the
>> translation source files.
>>
>> I have already updated the AOO4.0 UI project on the Pootle server and
>> the po files are available under
>> http://people.apache.org/~jsc/translation/
>>
>> I also have updated the extensions/source/preload.po for most languages
>> already because it were 2 minor changes only, one url and a name change.
>>
>> I apologize in the name of the project to all volunteers who have to
>> review again some strings. I hope we can improve the localization
>> process in the future to minimize the effort for all of you.
>>
>> We should now focus to complete as many as possible languages for 4.0. I
>> will include completed languages in the snapshots for more detailed
>> testing.
>>
>> Juergen
>>
>
> Working on the ES pootle ;)
>

Now, it's 100% again ;)


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

Re: [RELEASE][TRANSLATION]: last update on UI project triggers again some reviews and changes

[Albino B Neto]

2013/5/22 RGB ES :
>> Working on the ES pootle ;)
>>
>
> Now, it's 100% again ;)

Cool.

We are working. :-D

  Albino

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