SoylentNews is people
SoylentNews
The Wine team has announced that version 2.0 of the Windows compatibility layer has been released.
The main highlights are the support for Microsoft Office 2013, and the 64-bit support on macOS.
[...] This is the first release made on the new time-based, annual release schedule. This implies that some features that are being worked on but couldn't be finished in time have been deferred to the next development cycle. This includes in particular the Direct3D command stream, the full HID support, the Android graphics driver, and message-mode pipes.
Do any soylentils still rely on Wine for that one irreplaceable application?
This discussion has been archived.
No new comments can be posted.
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
TOO BAD YOU CAN'T BUY a voodoo globe so that you could make the earth spin
real fast and freak everybody out.
-- Jack Handey, The New Mexican, 1988.
(Score: 0) by Anonymous Coward on Thursday January 26 2017, @12:06AM
Large corporations that are switching to Linux desktops have always some cruft left that is just impossible to get working on alternatives and they are switching from Windows for a reason so they absolutely don't want to keep maintaining (and paying licenses) for Windows which are running on VMs.
I have personally witnessed the horror of trying to export/recode Excel macros to Open Office. They ended up installing CodeWeavers CrossOver Office (commercially supported WINE MS Office set up) for everyone that needed those macros.
(Score: 0) by Anonymous Coward on Thursday January 26 2017, @02:33AM
The guys in Munich hit this problem early on and developed (GPL'd) WollMux. [google.com]
Have you heard of that?
Did you give it a try?
...and OxygenOffice (a fork of OO.o, affiliated with SuSE) had decent M$Orifice macro compatibility for the most-commonly-used VBA stuff a bunch of years back.
The OO.o guys were resistant to incorporating that stuff, but the LibreOffice guys jumped on that like a duck on a june bug.
It seems clear that your efforts were before that fork.
-- OriginalOwner_ [soylentnews.org]
(Score: 0) by Anonymous Coward on Thursday January 26 2017, @06:33PM
No, those macros were doing some internal business logic and had to import data from external databases and after doing their stuff export some to some other systems etc.
Maybe that OxygenOffice could have worked but I doubt, they went with RHEL anyway so no hope for even trying it.