Hi :) They have almost all libraries in common, sometimes there are slightly different names to some of the libraries. Variables, calls, stack-pointers (?) (please no Latin quotes!) almost everything is the same and likely to cause conflicts. All kinds of stuff that is way beyond the understanding of non-devs. Most of it all dates back to the way things were set-up in Star Office, hence soffice, swriter, and so on. It's not a trivial issue to be sorted out with a quick find&replace-all. Just the code-clean-up is taking longer than 6 months although we are already seeing a lot of benefits from that, such as smaller downloads, faster start-up and so on.
Regards from Tom :) ________________________________ From: Milos Sramek <[email protected]> To: [email protected] Sent: Thu, 23 June, 2011 13:48:13 Subject: Re: [libreoffice-users] Re: Mac people Dňa 23.06.2011 12:51, Tom Davies wrote / napísal(a): > > > > > ________________________________ > From: Alexander Thurgood <[email protected]> > To: [email protected] > Sent: Thu, 23 June, 2011 10:34:23 > Subject: [libreoffice-users] Re: Mac people > > Le 21/06/11 20:56, Ernest Kurtz a écrit : > > Hi Ernest, > >> If there are any primarily Mac users on this list, please contact me >> off-list? >> >> >> >> My interest is almost exclusively in Writer, and because I work on several >> projects at the same time, I like to have available and open several >> different > >> word processors. When I've tried to run both OOo and LO at the same time, >> LO >> crashes. It works well if I do not open OOo, though I keep OOo on my >> machine. >> >> No conflicts with NisusPro, MyWritings, GeoWord, Bean, but I would like to >> use > >> OOo or NeoOffice. >> >> > I have noticed that with LO 3.3.x and OOo 3.3.x, I could get one or the > other to crash if both were running at the same time. I haven't been > able to pin it down though, as it is somewhat irregular and put it down > to instabilities in both products. I have a theory that the programs > possibly attempt to address the same memory space during certain > operations, which potentially causes the problems. I can't prove it > because trying to run valgrind on two separate OOo/Neo/LibO instances > virtually brings my Mac to a standstill. I would check the output of ldd soffice.bin (for both LO and OOO binaries). Maybe you will see that one uses a shared library of the other. Normally, these programs should be independent. If they influence themselves, they must have something in common. The first thing, which jumps to my mind, is a shared library with the same. Milos > > Alex > > > > Hi :) > That is not specific to Macs. It happens on all platforms afaik (i haven't > heard from Bsd people). That doesn't make it less important tho! > Regards from > Tom :) > -- email & jabber: [email protected] -- Unsubscribe instructions: E-mail to [email protected] In case of problems unsubscribing, write to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted -- Unsubscribe instructions: E-mail to [email protected] In case of problems unsubscribing, write to [email protected] Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette List archive: http://listarchives.libreoffice.org/global/users/ All messages sent to this list will be publicly archived and cannot be deleted
