Re: "is comprised of"

[Andrea Pescetti]

Rob Weir wrote:

So if we want to change, maybe something like
"Apache OpenOffice consists of..." or "Apache OpenOffice includes..."
or "Apache OpenOffice is a suite of..."


Both "includes" and "consists of" seem easier to understand for an 
international audience than "is comprised of" (regardless that it is 
100% correct English or not).


Regards,
  Andrea.

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

Re: EXTERNAL: Re: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory Fault

[Andre Fischer]

On 04.02.2014 23:58, Steele, Raymond wrote:

Herbert,



Raymond and I have been using the dbx debugger feature of Solaris Studio 12.3 
with an equivalent throw/catch feature (intercept/whocatches) and have found 
that the cases where we tried to intercept exceptions, they were unhandled. 
This includes inside the SidebarController where we have tracked the problem 
origination. We have stepped through the code multiple times and while we have 
found that the problem originates in the SidebarController, we cannot explain 
how it happens.


Hi, my name is Andre.  I am the one who wrote the sidebar framework.   I 
don't know if I can help (I can not reproduce this problem on a platform 
which I have access to) but I will try.


Which exceptions (before the actual crash) do you see?




Using the debug tool we see that the SidebarController constructor doesn't 
complete because the segmentation fault occurs when the 
notifyContextChangeEvent is called a second time. The first time it is called 
it is located in the addContextChangeEventListener where it appears to work as 
expected, even the acquire function appears to call the 
ContextChangeEventMultiplexer without any errors.



The following lines are what we see as we step-by-step through the execution of 
the SidebarController.cxx constructor when we select the Spreadsheet or the 
Text Document.



The first time the notifyContextChangeEvent is called:



SidebarController: Line 147 - addContextChangeEventListener is called

Reference.h: Line 359 - XInterface operator -> is called

Reference.h: Line 217 - castFromXInterface is called

Reference.hxx: Line 134 - castToXInterface is called

Reference.h: Line 232 - function castToXInterface

Reference.hxx: Line 135 - if(_pInterface)

Reference.hxx: Line 136 - _pInterface->acquire();

compbase4.hxx: Line 70- WeakComponentHelperBase::acquire prototype

implbase.hxx: Line 236 - WeakObject::acquire definition

-  ContextChangeEventMultiplexer receives and processes event.

-  In ContextChangeEventMultiplexer addContextChangeEventListener 
adds and calls the notifyContextChangeEvent

-  SidebarController::notifyContextChangeEvent: Line 257 is called. 
The rEvent associated with the notifyContextChangeEvent is a valid address

-  The rEvent STRUCT contains the application name and context name 
references

Context.cxx: Line 51 - msContext(rsContext)

ustring.hxx: Line103 - pData = str.pData

-  Processing continues as normal from this point till line 168 of 
SidebarController.cxx



The second time the notifyContextChangeEvent is called:


I checked what is happening on Windows:

- there should be exactly one call to the SidebarController constructor 
per application window.  The constructor is called from the 
SidebarDockingWindow constructor.  A second call, as described in your 
earlier mail should not take place.  Can you check the stack trace of 
that second call and see who makes that call?


- While in the constructor of SidebarController I see only one call to 
notifyContextChangeEvent().  As you found out it is triggered by the 
SidebarController registering itself as listener (it is being informed 
of the current context). The second call (while inside the constructor) 
is not necessarily an error but I would like to know what triggers it.  
The second call that I see is triggered after the SidebarController is 
constructed and is made (indirectly) from SfxViewFrame::DoActivate().  
Can you show me the stack trace of that second call?






SidebarController: Line 168 - the xWeakController(this) is called

Reference.hxx: Line 134 - castToXInterface is called

Reference.h: Line 232 - function castToXInterface

Reference.hxx: Line 135 - if(_pInterface)

Reference.hxx: Line 136 - _pInterface->acquire(); (Why does this not behave 
like the first call above? Should there be a call to 
WeakComponentHelperBase::acuire? The next step appears to skip all these 
procedures.)

SidebarController::notifyContextChangeEvent: Line 257 is called, the rEvent is 
pointing to a reference that cannot be accessed.

-  The dbx dump has an rEvent = STRUCT

-  The dbx print of the rEvent says that it is referenced through a 
nil pointer

Context.cxx: Line 51 - msContext(rsContext)

ustring.hxx: Line103 - pData = str.pData

-  Accessing the pData in the string has been corrupted and causes 
the following Segmentation Fault:

-  Signal SEGV(no mapping at the fault address) in 
rtl::OUString::OUString at line 103 in file ustring.hxx



We are trying to do our due diligence on this problem and we have been 
investigating it as best we can, but we are lacking in knowledge that the 
community can provide, which is why we are seeking help. Also the errors don't 
seem to make sense, so we believe we are dealing with a bug. We hope we are not 
being an inconvenience, and we definitely appreciate the help. We are 
investigating alt

Fwd: [PMCs] Be the first to take the 2014 Future of Open Source Survey

[jan i]

Hi.

You are hereby invited to participate in a opensource survey, that tries to
determine the future for us all. This survey is one of the biggest, most
important of the kind, trying to charter the future of opensource.

All PMCs in all projects have been invited, and like in other projects the
invitation is hereby passed on to the whole community.

the link to the survey is:
https://www.surveymonkey.com/s/2014-future-open-source

the submit (start) is below the sponsor list.


rgds
jan I.



  - Forwarded Message -
 *From:* Megan DeGruttola 
*To:* "s...@apache.org" ; "brett.por...@gmail.com" <
brett.por...@gmail.com>
*Cc:* "Jim Jagielski (jim...@gmail.com)" 
*Sent:* Monday, 3 February 2014, 18:05
*Subject:* Be the first to take the 2014 Future of Open Source Survey

 *Welcome to the 2014 Future of Open Source Survey!*

*Black Duck*  and *North
Bridge*,
in partnership with * Forrester Research Analyst Jeffrey Hammond,* would
like to thank you for your participation as a collaborator in this year's
thought leadership program. As you know, this annual survey provides a
report on the state of the open source industry and analysis of future
trends from influencers and important open source-related organizations
like yours.

*Be the first to take the
survey!*

We will be publically announcing the survey on* February 5th*, but as a
2014 Survey Collaborator you are invited to be one of the first to take
this survey  in
advance of its availability to the broader open source community!

*Opportunities and Highlights*

 · *30+ collaborators*! We'd like to welcome back our returning
industry leaders and the new organizations that have joined this year.
 · *Collaborator logos* are displayed on the live survey, the survey
webpage  and in
all media advisories.
 · The Future of Open Source has a dedicated blog category on Open
Source 
Delivers,
which you are invited to submit content to. For more information, please
contact Megan DeGruttola at mdegrutt...@blackducksoftware.com.
 · *Results revealed in a live webinar!*  The Future of Open Source
Survey sponsors, Black Duck and North Bridge, will host a live panel
discussion revealing this year's survey results on April 3, 2013 at 2 p.m.
ET
.

*Help us reach our goal of 1,000 respondents this year!*

Starting *February 5th*, please distribute the survey link:
https://www.surveymonkey.com/s/2014-future-open-source via newsletters,
e-mails, blogs, tweets, etc. throughout the coming weeks.

*The planned survey close date is March 5, 2014.* Please let us know your
plans for distributing the survey, and how many respondents you hope to
reach. Together we'll make this the most successful survey to date!

*Get social*

Follow all the news and activity around the Future of Open Source Survey *on
Twitter at **@FutureofOSS* ! Join the
conversation by *using the hashtag
**#FutureOSS*.


If you send us your Twitter handles, we'll be sure to follow you. Suggested
tweets coming soon!

*Help with promotions*
 We will provide a link to the survey announcement media advisory, email
templates for you to use in your outreach, along with suggested tweets.

If you have a PR firm, please include them in this effort. We are happy to
send them any official communications from our PR firm, Emanate.

Please contact: Megan DeGruttola at +1-781-425-4432
mdegrutt...@blackducksoftware.com or Jacqueline Ganim-DeFalco 978-283-8333
jac...@marketingrecon.com for any questions regarding the survey.

Best,

*Megan DeGruttola*
Communications Manager
*Black Duck | Connect. Code. Create.*
mdegrutt...@blackducksoftware.com
Twitter: @megandegruttola  | Skype:
blackduck_mdegruttola
www.blackducksoftware.com

 


  

  

RE: EXTERNAL: Re: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory Fault

[Steele, Raymond]

Hi Andre,

Thanks for the response. We are looking at that now.

In the constructor of SidebarController at line 168 "WeakReference...", on your 
system, does the code step to  Reference.h: Line 359 - XInterface operator, as 
it does during our run?

It appears  that at runtime Reference.hxx: Line 136 - _pInterface->acquire()  
that occurs after "WeakReference.."  does not  execute as it does after 
addContextChangeEventListener a few lines above WeakReference. Do you see a 
similar behavior?  Can you provide the first 5-10 steps your code takes after 
WeakReference (line 168)?

Thanks!

Raymond

From: Steele, Raymond
Sent: Tuesday, February 04, 2014 3:59 PM
To: a...@openoffice.apache.org; Herbert Duerr (h...@apache.org); 
dev@openoffice.apache.org
Cc: Meffe, David K
Subject: RE: EXTERNAL: Re: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory 
Fault


Herbert,



Raymond and I have been using the dbx debugger feature of Solaris Studio 12.3 
with an equivalent throw/catch feature (intercept/whocatches) and have found 
that the cases where we tried to intercept exceptions, they were unhandled. 
This includes inside the SidebarController where we have tracked the problem 
origination. We have stepped through the code multiple times and while we have 
found that the problem originates in the SidebarController, we cannot explain 
how it happens.



Using the debug tool we see that the SidebarController constructor doesn't 
complete because the segmentation fault occurs when the 
notifyContextChangeEvent is called a second time. The first time it is called 
it is located in the addContextChangeEventListener where it appears to work as 
expected, even the acquire function appears to call the 
ContextChangeEventMultiplexer without any errors.



The following lines are what we see as we step-by-step through the execution of 
the SidebarController.cxx constructor when we select the Spreadsheet or the 
Text Document.



The first time the notifyContextChangeEvent is called:



SidebarController: Line 147 - addContextChangeEventListener is called

Reference.h: Line 359 - XInterface operator -> is called

Reference.h: Line 217 - castFromXInterface is called

Reference.hxx: Line 134 - castToXInterface is called

Reference.h: Line 232 - function castToXInterface

Reference.hxx: Line 135 - if(_pInterface)

Reference.hxx: Line 136 - _pInterface->acquire();

compbase4.hxx: Line 70- WeakComponentHelperBase::acquire prototype

implbase.hxx: Line 236 - WeakObject::acquire definition

-  ContextChangeEventMultiplexer receives and processes event.

-  In ContextChangeEventMultiplexer addContextChangeEventListener 
adds and calls the notifyContextChangeEvent

-  SidebarController::notifyContextChangeEvent: Line 257 is called. 
The rEvent associated with the notifyContextChangeEvent is a valid address

-  The rEvent STRUCT contains the application name and context name 
references

Context.cxx: Line 51 - msContext(rsContext)

ustring.hxx: Line103 - pData = str.pData

-  Processing continues as normal from this point till line 168 of 
SidebarController.cxx



The second time the notifyContextChangeEvent is called:



SidebarController: Line 168 - the xWeakController(this) is called

Reference.hxx: Line 134 - castToXInterface is called

Reference.h: Line 232 - function castToXInterface

Reference.hxx: Line 135 - if(_pInterface)

Reference.hxx: Line 136 - _pInterface->acquire(); (Why does this not behave 
like the first call above? Should there be a call to 
WeakComponentHelperBase::acuire? The next step appears to skip all these 
procedures.)

SidebarController::notifyContextChangeEvent: Line 257 is called, the rEvent is 
pointing to a reference that cannot be accessed.

-  The dbx dump has an rEvent = STRUCT

-  The dbx print of the rEvent says that it is referenced through a 
nil pointer

Context.cxx: Line 51 - msContext(rsContext)

ustring.hxx: Line103 - pData = str.pData

-  Accessing the pData in the string has been corrupted and causes 
the following Segmentation Fault:

-  Signal SEGV(no mapping at the fault address) in 
rtl::OUString::OUString at line 103 in file ustring.hxx



We are trying to do our due diligence on this problem and we have been 
investigating it as best we can, but we are lacking in knowledge that the 
community can provide, which is why we are seeking help. Also the errors don't 
seem to make sense, so we believe we are dealing with a bug. We hope we are not 
being an inconvenience, and we definitely appreciate the help. We are 
investigating alternatives, but would really like to get this to work. Our 
current applications use OpenOffice extensively.  Since we had to move to 
Solaris 11, we are forced to get this working or find another solution, which 
we'd rather not pursue.



Hopefully you or a member of the community can help us make some headway. We'd 
appreciate it. Thanks.



David Meffe

How Apache project works

[Reem Elnagar]

Hi I started working now on " how the Apache project works" 

Re: Introduction to Contributing to Apache OpenOffice

[Andrea Pescetti]

On 27/01/2014 Cuau Maga wrote:

Hello, my name is Cuauhtemoc Magaña, I'm from Mexico(Guadalajara
City), i like to follow dev issues, I'm working in a C# and C++
solution that need export data to XLS and ODT documents then i like
participate and obtain new implementation for my project for example
i need update our components to not use any Microsoft DLL then i need
understand this framework.


Welcome to OpenOffice! If you want to participate in development, you 
should have a look at

http://openoffice.apache.org/orientation/intro-development.html
and then your first step will be to build it. There are instructions at
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
but this is often a difficult step and we can help you if you write to 
this list.


Please either subscribe to the dev list (you will find all details at 
the link above) or mention, when you write, that you are not subscribed 
yet, so that we know we should CC you.


Regards,
  Andrea.

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

Finishing ( How Apache project works)

[Reem Elnagar]

Hi again 
I finished the module how Apache project works 

RE: EXTERNAL: Re: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory Fault

[Steele, Raymond]

Andre,

We are not seeing any exception before the actual crash. Maybe I am not looking 
in the right place, but we've been using dbx intercept command to track any. 
Any other suggestions?

  Also, I've attached the stack trace of the first and second 
notifyContextChangeEvent.  They are different.

Raymond

From: Steele, Raymond
Sent: Wednesday, February 05, 2014 9:48 AM
To: 'a...@openoffice.apache.org'; Herbert Duerr (h...@apache.org); 
dev@openoffice.apache.org
Cc: Meffe, David K; 'awf@gmail.com'
Subject: RE: EXTERNAL: Re: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory 
Fault

Hi Andre,

Thanks for the response. We are looking at that now.

In the constructor of SidebarController at line 168 "WeakReference...", on your 
system, does the code step to  Reference.h: Line 359 - XInterface operator, as 
it does during our run?

It appears  that at runtime Reference.hxx: Line 136 - _pInterface->acquire()  
that occurs after "WeakReference.."  does not  execute as it does after 
addContextChangeEventListener a few lines above WeakReference. Do you see a 
similar behavior?  Can you provide the first 5-10 steps your code takes after 
WeakReference (line 168)?

Thanks!

Raymond

From: Steele, Raymond
Sent: Tuesday, February 04, 2014 3:59 PM
To: a...@openoffice.apache.org; Herbert 
Duerr (h...@apache.org); 
dev@openoffice.apache.org
Cc: Meffe, David K
Subject: RE: EXTERNAL: Re: OO 4.01 Compiled for Solaris 11 x86 Runtime Memory 
Fault


Herbert,



Raymond and I have been using the dbx debugger feature of Solaris Studio 12.3 
with an equivalent throw/catch feature (intercept/whocatches) and have found 
that the cases where we tried to intercept exceptions, they were unhandled. 
This includes inside the SidebarController where we have tracked the problem 
origination. We have stepped through the code multiple times and while we have 
found that the problem originates in the SidebarController, we cannot explain 
how it happens.



Using the debug tool we see that the SidebarController constructor doesn't 
complete because the segmentation fault occurs when the 
notifyContextChangeEvent is called a second time. The first time it is called 
it is located in the addContextChangeEventListener where it appears to work as 
expected, even the acquire function appears to call the 
ContextChangeEventMultiplexer without any errors.



The following lines are what we see as we step-by-step through the execution of 
the SidebarController.cxx constructor when we select the Spreadsheet or the 
Text Document.



The first time the notifyContextChangeEvent is called:



SidebarController: Line 147 - addContextChangeEventListener is called

Reference.h: Line 359 - XInterface operator -> is called

Reference.h: Line 217 - castFromXInterface is called

Reference.hxx: Line 134 - castToXInterface is called

Reference.h: Line 232 - function castToXInterface

Reference.hxx: Line 135 - if(_pInterface)

Reference.hxx: Line 136 - _pInterface->acquire();

compbase4.hxx: Line 70- WeakComponentHelperBase::acquire prototype

implbase.hxx: Line 236 - WeakObject::acquire definition

-  ContextChangeEventMultiplexer receives and processes event.

-  In ContextChangeEventMultiplexer addContextChangeEventListener 
adds and calls the notifyContextChangeEvent

-  SidebarController::notifyContextChangeEvent: Line 257 is called. 
The rEvent associated with the notifyContextChangeEvent is a valid address

-  The rEvent STRUCT contains the application name and context name 
references

Context.cxx: Line 51 - msContext(rsContext)

ustring.hxx: Line103 - pData = str.pData

-  Processing continues as normal from this point till line 168 of 
SidebarController.cxx



The second time the notifyContextChangeEvent is called:



SidebarController: Line 168 - the xWeakController(this) is called

Reference.hxx: Line 134 - castToXInterface is called

Reference.h: Line 232 - function castToXInterface

Reference.hxx: Line 135 - if(_pInterface)

Reference.hxx: Line 136 - _pInterface->acquire(); (Why does this not behave 
like the first call above? Should there be a call to 
WeakComponentHelperBase::acuire? The next step appears to skip all these 
procedures.)

SidebarController::notifyContextChangeEvent: Line 257 is called, the rEvent is 
pointing to a reference that cannot be accessed.

-  The dbx dump has an rEvent = STRUCT

-  The dbx print of the rEvent says that it is referenced through a 
nil pointer

Context.cxx: Line 51 - msContext(rsContext)

ustring.hxx: Line103 - pData = str.pData

-  Accessing the pData in the string has been corrupted and causes 
the following Segmentation Fault:

-  Signal SEGV(no mapping at the fault address) in 
rtl::OUString::OUString at line 103 in file ustring.hxx



We are trying to do our due diligence on this problem and we ha

Re: How Apache project works

[jan i]

On 5 February 2014 19:28, Reem Elnagar  wrote:

> Hi I started working now on " how the Apache project works"


Just for my understanding do you mean  the title, then the ML should be the
general community list. If you mean how AOO works, then its the correct
list.

but in any case I am not to sure what your goal is, and if some of the
information isnt already at hand.

rgds
jan I.

Re: How Apache project works

[Rob Weir]

On Wed, Feb 5, 2014 at 4:45 PM, jan i  wrote:
> On 5 February 2014 19:28, Reem Elnagar  wrote:
>
>> Hi I started working now on " how the Apache project works"
>
>
> Just for my understanding do you mean  the title, then the ML should be the
> general community list. If you mean how AOO works, then its the correct
> list.
>
> but in any case I am not to sure what your goal is, and if some of the
> information isnt already at hand.
>

I think the reference is to this webpage:
http://openoffice.apache.org/orientation/how-aoo-project-works.html

It asks new volunteers to "check in" on the dev list when they are
getting started.  This gives us a chance to say "Hi" and welcome them.

Regards,

-Rob

> rgds
> jan I.

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

Re: New Dev Volunteer

[Andrea Pescetti]

On 01/02/2014 Tenzin Chhosphel wrote:

Although I have experience in several programming languages such as
C, Java, Objective-C, and so forth, I primary code in C++. So, as
OpenOffice is coded in C++, I think I can contribute to the project.


Welcome, Tenzin! There are lots of opportunities for a good C++ 
programmer to contribute to OpenOffice.


But you must start with the basics: please read
http://openoffice.apache.org/orientation/intro-development.html
and build OpenOffice. There are instructions at
https://wiki.openoffice.org/wiki/Documentation/Building_Guide_AOO
but feel free to ask the list if you have any difficulties, the first 
build is often a bit painful since we use many non-standard tools.



I want to leave with few questions. I like to get to know more
specifics about current happenings, who is working on what, that sort
of thing. I also like to know which specific part of the project can
I contribute should I be a volunteer at OpenOffice. Thank you.


We don't have any specific preferences at the moment. Recent major 
changes included the Sidebar (and I think Andre -Andre Fischer- may want 
to extend it further), the Accessibility work by Steve Yin, the OOXML 
filter improvements by Oliver-Rainer Wittmann with ongoing work by 
Clarence for the OOXML export, graphics improvements by Armin Le Grand, 
a lot of infrastructural work by Herbert Duerr and Juergen Schmidt, 
dozens of small fixes and improvements by Hanya, the ongoing 
localization work by Jan Iversen, and hundreds of other developments and 
bugfixes that I'm not mentioning but are still very valuable. So I 
recommend that you start by getting your own build ready, and then we 
have thousands of bug reports you can choose from if you want to help 
with coding! Just let us know when you manage to build.


Regards,
  Andrea.

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

Re: Introduction to Contributing to Apache OpenOffice

[Alexandro Colorado]

I would recomend to join the ODFToolkit project since your project seems to
be more on the developer / framework side.
https://incubator.apache.org/odftoolkit/
 That said you can also look at projects such as oooconv which implement
openoffice as a service to provide features as a service through different
interfaces (web, command line, etc).
http://oooconv.free.fr/index_en.html


On Mon, Jan 27, 2014 at 12:03 PM, Cuau Maga  wrote:

> Hello, my name is Cuauhtemoc Magaña, I'm from Mexico(Guadalajara City), i
> like to follow dev issues, I'm working in a C# and C++ solution that need
> export data to XLS and ODT documents then i like participate and obtain new
> implementation for my project for example i need update our components to
> not use any Microsoft DLL then i need understand this framework.
>
>
> Regards
>
>
> Cuauhtemoc Magaña
>
>




-- 
Alexandro Colorado
Apache OpenOffice Contributor
http://www.openoffice.org
882C 4389 3C27 E8DF 41B9  5C4C 1DB7 9D1C 7F4C 2614

Reporting a problem with the OpenOffice website

[Gwen Hodder]

Hello I’m have a problem with Apache open office.this is what comes up belowThe last time you opened OpenOffice, it unexpectedly quit while reopening windows. Do you want to try to reopen its windows again?Then I click on cancel or reopen but it stays there and does nothing,The only way I can close down my computer now is to turn it off at button.Can you please advise me on how to fix this problem.I have the latest open office download, but it still hasn’t solved the problem.My computer is a MAC OSX 10.9.1I look forward to your replayKind regards Gwen Gwen HodderLife Enhancement Coachwww.gwenhodder.com0417 426 593

Reporting a problem with the OpenOffice website

[Carol Miller]

Your product keeps downloading itself onto my computer. I do not want it!
How do I stop this? 

 

Carol Miller



---
This email is free from viruses and malware because avast! Antivirus protection 
is active.
http://www.avast.com