Date: prev next · Thread: first prev next last
2016 Archives by date, by thread · List index

[tdf-discuss] Re: Deprecation (was Re: Remove ActiveX from LibreOffice)

In addition, everything thru Windows 10 currently supports ActiveX, and of
all the various versions of Windows still seen in the wild, Windows 8, 8.1,
and 10 account for only 23% of all OSes, and 26% of Windows OSes.  Windows
7 accounts for 56%, and Windows XP comes in at #2 accounting for 11%.

Windows OSes that support these features are not going away anytime soon.
Microsoft may even remove them from future releases, but there will be
users who will not so easily let go of their former feature sets.  There
are too many powerful features in 32-bit Windows and 64-bit Windows to let
them all go.  Microsoft and the rest of the business world may want to move
us all to browser-based operating systems, but there is no real computing
power there.  It changes the user base from owners to renters, and there
are many who will not stand for that, and it will be those people who
continue to use LibreOffice, for example, as they are looking for real
ownership of their machine, and not just being a renter.

Allodial Title -- it makes all the difference. :-)

Best regards,
Rick C. Hodgin

On Wed, Jan 13, 2016 at 1:36 AM, James E Lang <> wrote:

But Bryan, Rick is pointing out that ActiveX usage is not limited to
browsers only. If its usage is deprecated then I assume there is a
functionally equivalent alternative but the *effective* life cycle of
applications that use ActiveX is almost certain to stretch past the start
of LO 6.

I would define effective life cycle of an application as being AT LEAST
two half lives of the application beyond the first release of the
application that replaces the final LEGITIMATE release with an 18 month
minimum (36 months if there is no subsequent application update release).

All support for Windows XP has been discontinued by Microsoft yet many
computers still use it. Requiring a Windows XP upgrade to support EXISTING
functionality in LO is quite possibly premature even now.

Depreciation means to me that products should cease requiring use of
something in ongoing development cycles but that for its effective life
cycle its use WRT previously developed programs will not be abridged.

I'm told that ActiveX has been a security nightmare since it was first
released. That's probably a better reason to not support it than citing its
depreciation status.

I realize that on volunteer projects such as LO such standards are a bit
of a burden but they warrant at least a nodding recognition.


-----Original Message-----
From: Bryan Quigley <>
To: "Rick C. Hodgin" <>
Cc: Chris Sherlock <>, Ashod Nakashian <>, libreoffice <>
Sent: Tue, 12 Jan 2016 20:27
Subject: Re: Remove ActiveX from LibreOffice

Hi Rick,

ActiveX is deprecated by Microsoft and will be less useful (or not at
all) on newer MS browsers.  I'm unsure if it ever worked (or was
supposed to) let you embed ActiveX controls into LibreOffice itself.

Kind regards,

On Mon, Jan 11, 2016 at 10:08 PM, Rick C. Hodgin
<> wrote:
Why are you removing ActiveX from LibreOffice? Excel supports it, and it
desirable for integration with Windows apps like C#, Visual Basic, Visual
FoxPro. It allows those other apps to integrate the app directly into

I have tried to use it previously, but could not find documentation for
If it's an unused feature, I'd suggest that's why than for other reasons.

Best regards,
Rick C. Hodgin

-------- Original Message --------
From: Chris Sherlock
Sent: Mon, 11/01/2016 08:21 PM
To: Ashod Nakashian
CC: libreoffice ; Bryan Quigley
Subject: Re: Remove ActiveX from LibreOffice

That sounds pretty reasonable to me.

Out of interest, just how “integrated” is this with the code? If someone
wanted to create an external project on GitHub or some place like this,
would it be feasible?

I guess I’m trying to understand how much of core it touches… to
an ActiveX control outside of the main tree, would a developer need to
LibreOffice entirely, or could they maintain their codebranch entirely
seperately and update the control if necessary after we do our changes to
the main codebase?

I’m definitely for removing all vestiges of ActiveX from LO, but the
more I
think about it the more I can see that some corporation somewhere might
affected, far more so than the remove of NPAPI… giving them the option
of a
control that can be maintained outside of the main project would be nice


On 12 Jan 2016, at 9:37 AM, Ashod Nakashian <> wrote:

On Mon, Jan 11, 2016 at 2:32 PM, Bryan Quigley <> wrote:

Anywhere else we should post this?

Ideally the note would show up unintrusively upon loading/using the
itself. Unfortunately we can't show a message box or some such UI, in
the ActiveX is used non-interactively (in which case it'd block forever,
becoming unusable).

So the next best thing to do is include the note in the installation,
should be hard to miss if made prominent (unless automated in silent

This would get the attention of possibly the users, if not the developers
(who might not even test out new versions as they come out, and expect
things to work as before). Users can contact developers, I expect, or at
least plan accordingly. Regardless, all we want is to give advance
before the day someone installs a newer version and be met with the
of missing ActiveX altogether.

The installation and release notes seem to be the most reasonable
places, if
not upon using the ActiveX itself. Unless others have better ideas.

LibreOffice mailing list

LibreOffice mailing list

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.