EK - I've used OOo X11 on Mac, neooffice, OOo aqua and LO. As mentioned below, I do not try to use them on same login as too much trouble. I am still a little leery of OOo v LO, especially since apache announcement - I use LO but have kept OOo on clients machines. There are issues with special to Mac (in fact there was a recent posting about one Alex and I discussed, which may not get resolved simply because the role necessary is vacant.....) but as Tom said most OOo/LO issues are cross platform
On Jun 23, 2011, at 6:15 AM, Ernest Kurtz <[email protected]> wrote: > Thank you, Marc. Might you -- or anyone -- have any thoughts/experience with > NeoOffice and LO? > ek > > On Jun 23, 2011, at 6:27 AM, Marc Grober wrote: > >> You can create two different users to use each of the different apps - only >> way to accomplish this in my opinion unless you go through all options and >> create two different locations for app user profiles, as that is what is >> causing the crashes I believe (I.e, they are reading same user data....) >> >> >> >> On Jun 23, 2011, at 1:34 AM, Alexander Thurgood <[email protected]> >> wrote: >> >>> 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. >>> >>> >>> Alex >>> >>> >>> -- >>> 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 >> >> > > > -- > 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
