To test most* of what I proposed to remove: During Install disable the
ActiveX control. (Ideally with a fresh install)
AFAICT OLE is actually also separate (but if it's not we don't want to
break that). It works fine on Linux (and I don't have a copy of MS
Office to test with on Windows).
ActiveX is more likely a marketing buzzword used for many aspects of the
COM technology.
Yes, I've found that a lot. Not a clear line in the sand for what it is.
Thanks both if you can test!
Bryan
*We'd still want to confirm with an actual build to be sure.
On Fri, Jan 27, 2017 at 6:24 PM, <libroffice.dev@artavi.de> wrote:
Hi,
Am 27.01.2017 um 18:03 schrieb Bryan Quigley:
Looking back over my previous attempt, I think you might not be
affected. (In any case COM/ATL support would not be dropped)
The other problem was not having good test cases for making changes to
the code. I do note in my original release notes "We specifically
want feedback if you use ActiveX to embed LibreOffice components into
your application." Our original intention was to remove the plugin
that allows you to embed LibreOffice inside other applications (like
IE) using ActiveX. Without test cases that worked, we weren't able to
ensure we wouldn't break something.
Ah, maybe we were talking about different things.
Do you mean the ability i.e. to put an LO calc document as object into a
MS
word document, and when activating the object the LO menu appears and
take
over control? I was talking about the pure automation through COM,
remotely
working on LO documents or gathering information.
ActiveX is more likely a marketing buzzword used for many aspects of the
COM
technology.
So, no, we don't use that OLE stuff. I can remember from the early days
of
OLE it was slow and had poor stability, so I never used that.
Best regards
Jörgen