On 11 Jan 2016, at 10:41 AM, Bryan Quigley <gquigs@gmail.com> wrote:
To look at this issue from another POV.. If someone showed up today
with an issue with a LO ActiveX control embedded in their application
that didn't work - what would our response be? It's an outdated
technology that we're not investing in.
It probably shows a lack of adoption, but it doesn’t look like anyone actually has reported issues
with it...
My position on ActiveX is to leave it (lest we break applications in the
wild,) and to *announce its deprecation* with two goals: first, solicit the
feedback of LO ActiveX consumers and, if so inclined to continue using it,
help in its support. And second, to flag a date in the future when ActiveX
will be completely removed from LO codebase, pending sufficient reason and
support by its consumers.
I'm happy with this. I'd say a quicker timeframe is fine though.
From the announce, if no one has found an application that uses
LO-embedded ActiveX remove it in a month or something. I expect that
if there are some users they might not hear until the install the
version without it regardless of what we do.
Perhaps it should be announced in the release notes, with an actual version where it will be
removed.
Chris
Context
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.