LibO install in Windows currently follows the go-oo practice of removing
existing OOo installs (without warning). It can of course be installed
in parallel (see my thread "[libreoffice-users] [Windows] LibO in
parallel w/OOo?" on the users list, but that provides several distinct
disadvantages:
1. No system file association or icons.
2. No menu items (user must create their own + desktop icon)
3. Program file names are the same as OOo (soffice, scalc etc) so there
is no easy way to distinguish between _which_ soffice et al that you are
running.
Given that LibO is a "fresh start", it would be nice if LibO can, in the
future, behave in a responsible manner on Windows installs and not trash
a user's version of OOo. After all, the user should have the freedom
(Libre?) of being able to have both OOo and LibO installed on their
system (in the same way one can on linux). I think that new (Windows)
users to LibO might get pretty upset when they find that the install has
trashed their OOo. I'm familiar with the issue of go-oo & Kami's
OxygenOffice version trashing OOo in the install process, but new
users/converts from OOo will not.
Also recommend that the bins be changed from soffice to loffice etc.,
so that it's easy to determine which is which on the system.
Disclaimer: I primarily use only linux, but I also use WinXP/7 for
testing OOo, and now LibO.
--
To unsubscribe, e-mail to discuss+help@documentfoundation.org
All messages you send to this list will be publicly archived and cannot be deleted.
List archives are available at http://www.documentfoundation.org/lists/discuss/
Context
- [tdf-discuss] Windows Install · NoOp
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.