Error installing an extension

[Jörg Schmidt]

Hello,

I received a confirmation, because of my help on offer:
http://wiki.openoffice.org/wiki/Extensions_Packager#BasicAddonBuilder_and_AOO_4.x

When installing an S-extension occurs an error message.
Can someone only based on the following error message saying what the problem 
is?

The error-message is:

(com.sun.star.deployment.DeploymentException){{Message="An error occurred while 
enabling: TestProgramMacro". Context = 
(com.sun.star.unoXInterface) @bbe9010}, Cause = 
(any){(com.sun.star.lang.IllegalArgumentException) {{Message = 
"",Context=(com.sun.star.uno.XInterface) @0},ArgumentPosition=(short)0}}}




Greetings,
Jörg



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

Re: [Proposal] Update Icons for AOO 4.1

[Andrea Pescetti]

Jürgen Schmidt wrote:

we should this discuss on the list only ... I have added a comment
already but my preference would be
1. drop it completely or
2. make the Apache logo much smaller and move it down, it is to dominant
at the moment


I wouldn't drop it completely since it's good to have the Apache 
attribution on the splash screen, so that users who do not know about 
Apache can at least have a hint while opening OpenOffice and reading 
"The Apache Software Foundation".


But I agree that the feather should be made smaller, and the text is 
confused and too dark with the current grey colors we use. Maybe 
something like the header of http://www.apache.org/ ?


Feather (smaller in proportion) + text "The Apache Software Foundation"

with the text written in grey instead of black.

Regards,
  Andrea.

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

Re: Please give me CWiki edit permissions

[Andrea Pescetti]

Nikita Fernandez wrote:

Could you please provide Edit Permissions for username: kitafern for the
CWiki.


Done. Whitelisted:
~kitafern Nikita Fernandez

Regards,
  Andrea.

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

RTF

[Patrick]

Hello,


I've received this .rtf file (attachment) with a little 
picture on the left side that i can't see with Open Office. I'm using 
Ubuntu because I hate Microsoft and all their products :) ... So, in 
conclusion, my friend (on Microsoft Office Word) opened this file and 
the picture was here. I'm asking now, could this problem be resolved in 
the future Open Office release?

Best regads,

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

Re: RTF

[Mechtilde]

Hello Patrick,

Am 19.10.2013 12:17, schrieb Patrick:
> Hello,
> 
> 
> I've received this .rtf file (attachment) with a little 
> picture on the left side that i can't see with Open Office. I'm using 
> Ubuntu because I hate Microsoft and all their products :) ... So, in 
> conclusion, my friend (on Microsoft Office Word) opened this file and 
> the picture was here. I'm asking now, could this problem be resolved in 
> the future Open Office release?

Can your friend send it as a *.doc or if (s)he use MS-Office 2010/2013
as an *.odt?
> 
> Best regads,
> 
> Patrick Demarki dipl.ing.
> 
Kind regards

Mechtilde






signature.asc
Description: OpenPGP digital signature

easy task

[Vladislav Stevanovic]

Hello,

Does exist some list of easy tasks that some potential developer for AOO
can see? Idea is that this sort of  list MUST exist, if we want to see here
new developers...

Regards,
Wlada

Re: [proposal] replace build.pl with a central Makefile.

[Kay Schenk]

On Fri, Oct 18, 2013 at 7:52 AM, Andre Fischer  wrote:

> On 18.10.2013 15:58, janI wrote:
>
>> On 18 October 2013 15:00, Andre Fischer  wrote:
>>
>>  On 18.10.2013 14:02, janI wrote:
>>>
>>>  sd


 On 18 October 2013 13:36, Andre Fischer  wrote:

   On 18.10.2013 11:32, janI wrote:

>   Hi.
>
>> due to the discussion in thread "Mentor a new build system", I have
>> made a
>> proposal for a central Makefile located in main.
>>
>>   Hi Jan,
>>
> it is great that you are going to improve this part of the build
> system.
>But I think that we need more details about how the proposed build
> system
> works.  Without them I can not really evaluate the proposal.
>
>   First of all, I agree with juergens remarks that this should be
>
 discussed
 before implemented, hence the wiki page.

 Secondly this has nothing directly to do with the proposed build system,
 its a simple replacement of build.pl in the current system.

  Yes, that is how I understood it.  I just did not know how to call the
>>> build.pl replacement.
>>>
>>>
>>>
>>>  I know that build.pl works, but having a Makefile in main, would make
 us
 one step closer on being compatible with the distros. To me this job is
 a
 simple cleanup, not something we deadly need, but nice to have.


   Some remarks regarding the missing options:

> --from 
>  This is one of the more important options and one that I use
> frequently
> (also in the form --all:).
>  Note that if you are in  and call 'make --from '
> then
> all modules are built
>  a) which  depends on
>  b) but not those that  depends on
>  c) Both  and  are built.
>
>   I have changed the documentation.
>
 I use the --all: myself very often, and have changed the
 documentation, because it is of course supported.

 The difference is that you do the call in main, but that is a minor
 detail
 that can be easily corrected (have /Makefile calling
 main/Makefile.

 I have also changed documentation on --html due to juergens comments.

  I am not sure that we understand --from and --since in the same way so
>>> I
>>> will try to explain what I think they do.
>>>
>>> Let's imagine that we have a simple project with modules A, B, C, D and
>>> E.
>>> where B depends on A, C on B, D on C, and E on D.
>>> A ' make all' would mean 'make E'.  The dependencies would then lead to
>>> building modules A, B, C, D, E in this order.
>>> If I am in E and call 'make --from C' then only C, D, and E should be
>>> built.  A 'make --since C' would only build D and E.
>>>
>>> If I am in D and call 'make --from B' then modules B, C, and D are built.
>>>   Call 'make --since B' to build only C and D.
>>> Note that 'make --from' accepts more than one module name (while 'make
>>> --all:' does not).
>>> Note also that in the above case (stand in D, call 'make --from B')
>>> module
>>> A is not built, regardless of whether there are changes in A or not.
>>>   Whereas a simple call to make (still standing in D) would build all
>>> modules that D depends on, directly or indirectly.  Thus the options
>>> '--from' and '--since' exist to actively exclude modules from being
>>> built.
>>>
>>> The whole thing becomes a little bit more complicated with multiple
>>> options to '--from' (I never use '--since' and also don't know a valid
>>> use
>>> case so I will ignore it for now) and more complex dependencies then in
>>> the
>>> simple example above.  Let's say that if we stand in instsetoo_native and
>>> call 'make --from svx sfx2'.  Note that svx depends on sfx2.  This would
>>> build svx, sfx2 and all modules that depend (directly or indirectly) on
>>> svx
>>> OR sfx2.
>>>
>>>  got it, now I just have one problem, why would you not build the
>> dependent
>> modules, if they needed to be built, thats a scenario I dont understand.
>> With a central makefile, /makefile will not be called so we do not
>> waste cpu cycles.
>>
>> With the .done files, we know when a module was last built and all modules
>> that depend it should be rebuilt which the rule
>> .done : .done
>>
>> will ensure, so If we have A -> B -> C -> D
>>
>> I go in B, and call make, then when I go in D and make, B,C,D will be
>> made.
>>
>> If we have A -> B -> D   C -> D
>> and do the same then only D will be made.
>>
>> So --from is not really saving anything ?
>>
>
> a) In your example you first go into B then, in a second step, into D.
>  The '--from' option lets you do the same (well, not really the same, but
> see below) just from D.
>
> b) You go first to B and call make.  This makes A, if necessary, then B.
>  The making of A is exactly the thing that you want to prevent with the
> '--from' option.  Go into D and call 'make --from B'.  A is not built.
>
> c) After the discussion with you I am not sure if we

Re: easy task

[akshika akalanka]

Good idea :-)
 On Oct 19, 2013 10:53 PM, "Vladislav Stevanovic" <
stevanovicvladis...@gmail.com> wrote:

> Hello,
>
> Does exist some list of easy tasks that some potential developer for AOO
> can see? Idea is that this sort of  list MUST exist, if we want to see here
> new developers...
>
> Regards,
> Wlada
>

Re: easy task

[janI]

On 19 October 2013 20:28, akshika akalanka wrote:

> Good idea :-)
>  On Oct 19, 2013 10:53 PM, "Vladislav Stevanovic" <
> stevanovicvladis...@gmail.com> wrote:
>
> > Hello,
> >
> > Does exist some list of easy tasks that some potential developer for AOO
> > can see? Idea is that this sort of  list MUST exist, if we want to see
> here
> > new developers...
>

We have bugzilla, where you can see all open issues. But apart from that, I
think its easier to connect with one of us developers.

What language do you want to program in ? at what skill level ?

I f.x. work on a new translation workflow, and can use a hand getting it
finished and tested.

I also work at slowly improving the build system, makefiles etc, and there
we need a lot more than just a hand.

rgds
jan I.


> >
> > Regards,
> > Wlada
> >
>

Re: easy task

[Andrea Pescetti]

Vladislav Stevanovic wrote:

Does exist some list of easy tasks that some potential developer for AOO
can see? Idea is that this sort of  list MUST exist, if we want to see here
new developers...


It seems it's a bit hidden, but we've had it for months.

Usually we point new developers to

http://openoffice.apache.org/orientation/intro-development.html

that has a chapter named "Finding Easy Tasks" with two predefined 
Bugzilla queries for "easy" (really introductory) and "simple" tasks.


There are currently more than 40 tasks ready there.

Regards,
  Andrea.

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

Re: easy task

[Vladislav Stevanovic]

>It seems it's a bit hidden

It is a bit hidden, indeed! And my impression of  this page is distant,
cold tone. No emotions, no pictures to show where is problem, there is no
directly approach to the potential developers.  Also, I can not see list of
features what we want to see in AOO in near future, or maybe this list
existed on other place. These features we can split on "easy task",
"moderate" and "heavy task". Maybe
We must improved this. If this is not a problem, I have a  good will to try
something in that area with some ideas. Is it OK?

Regards,
Wlada



2013/10/19 Andrea Pescetti 

> Vladislav Stevanovic wrote:
>
>> Does exist some list of easy tasks that some potential developer for AOO
>> can see? Idea is that this sort of  list MUST exist, if we want to see
>> here
>> new developers...
>>
>
> It seems it's a bit hidden, but we've had it for months.
>
> Usually we point new developers to
>
> http://openoffice.apache.org/**orientation/intro-development.**html
>
> that has a chapter named "Finding Easy Tasks" with two predefined Bugzilla
> queries for "easy" (really introductory) and "simple" tasks.
>
> There are currently more than 40 tasks ready there.
>
> Regards,
>   Andrea.
>
> --**--**-
> To unsubscribe, e-mail: 
> dev-unsubscribe@openoffice.**apache.org
> For additional commands, e-mail: dev-h...@openoffice.apache.org
>
>

Re: easy task

[akshika akalanka]

I would +1 that idea Wlada, you are really thoughtful. It would definitely
help new developers like us. Thank you. :-)
 On Oct 20, 2013 7:40 AM, "Vladislav Stevanovic" <
stevanovicvladis...@gmail.com> wrote:

> >It seems it's a bit hidden
>
> It is a bit hidden, indeed! And my impression of  this page is distant,
> cold tone. No emotions, no pictures to show where is problem, there is no
> directly approach to the potential developers.  Also, I can not see list of
> features what we want to see in AOO in near future, or maybe this list
> existed on other place. These features we can split on "easy task",
> "moderate" and "heavy task". Maybe
> We must improved this. If this is not a problem, I have a  good will to try
> something in that area with some ideas. Is it OK?
>
> Regards,
> Wlada
>
>
>
> 2013/10/19 Andrea Pescetti 
>
> > Vladislav Stevanovic wrote:
> >
> >> Does exist some list of easy tasks that some potential developer for AOO
> >> can see? Idea is that this sort of  list MUST exist, if we want to see
> >> here
> >> new developers...
> >>
> >
> > It seems it's a bit hidden, but we've had it for months.
> >
> > Usually we point new developers to
> >
> > http://openoffice.apache.org/**orientation/intro-development.**html<
> http://openoffice.apache.org/orientation/intro-development.html>
> >
> > that has a chapter named "Finding Easy Tasks" with two predefined
> Bugzilla
> > queries for "easy" (really introductory) and "simple" tasks.
> >
> > There are currently more than 40 tasks ready there.
> >
> > Regards,
> >   Andrea.
> >
> > --**--**-
> > To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<
> dev-unsubscr...@openoffice.apache.org>
> > For additional commands, e-mail: dev-h...@openoffice.apache.org
> >
> >
>

Re: easy task

[Glenn Harvey Liwanag]

Another +1 here. I'm actually just reading the e-mails ever since I got
here to see if I can get something from those.

I checked https://issues.apache.org/ooo/query.cgi?format=report-table and
https://issues.apache.org/ooo/describecomponents.cgi

Maybe adding some hot links to common bug lists would help everyone a lot
and so that the search is not limited by product category. Links to stuff
like: Easy, Intermediate, Difficult, Popular,. Giving new ones like us a
big list of things that we think can handle, I think, is much efficient
that just us looking for things to work on by category. It's just a
suggestion at best though.

On Sun, Oct 20, 2013 at 12:41 PM, akshika akalanka <
akshikaakala...@gmail.com> wrote:

> I would +1 that idea Wlada, you are really thoughtful. It would definitely
> help new developers like us. Thank you. :-)
>  On Oct 20, 2013 7:40 AM, "Vladislav Stevanovic" <
> stevanovicvladis...@gmail.com> wrote:
>
> > >It seems it's a bit hidden
> >
> > It is a bit hidden, indeed! And my impression of  this page is distant,
> > cold tone. No emotions, no pictures to show where is problem, there is no
> > directly approach to the potential developers.  Also, I can not see list
> of
> > features what we want to see in AOO in near future, or maybe this list
> > existed on other place. These features we can split on "easy task",
> > "moderate" and "heavy task". Maybe
> > We must improved this. If this is not a problem, I have a  good will to
> try
> > something in that area with some ideas. Is it OK?
> >
> > Regards,
> > Wlada
> >
> >
> >
> > 2013/10/19 Andrea Pescetti 
> >
> > > Vladislav Stevanovic wrote:
> > >
> > >> Does exist some list of easy tasks that some potential developer for
> AOO
> > >> can see? Idea is that this sort of  list MUST exist, if we want to see
> > >> here
> > >> new developers...
> > >>
> > >
> > > It seems it's a bit hidden, but we've had it for months.
> > >
> > > Usually we point new developers to
> > >
> > > http://openoffice.apache.org/**orientation/intro-development.**html<
> > http://openoffice.apache.org/orientation/intro-development.html>
> > >
> > > that has a chapter named "Finding Easy Tasks" with two predefined
> > Bugzilla
> > > queries for "easy" (really introductory) and "simple" tasks.
> > >
> > > There are currently more than 40 tasks ready there.
> > >
> > > Regards,
> > >   Andrea.
> > >
> > >
> --**--**-
> > > To unsubscribe, e-mail: dev-unsubscribe@openoffice.**apache.org<
> > dev-unsubscr...@openoffice.apache.org>
> > > For additional commands, e-mail: dev-h...@openoffice.apache.org
> > >
> > >
> >
>


*
*

No CWiki edit permissions

[Tae Wong]

Please give you CWiki edit permissions.

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