Microsoft office linux github
WinApps for Linux
Run Windows apps such as Microsoft Office/Adobe in Linux (Ubuntu/Fedora) and GNOME/KDE as if they were a part of the native OS, including Nautilus integration for right clicking on files of specific mime types to open them.
Proud to have made the top spot on r/linux on launch day.
WinApps was created as an easy, one command way to include apps running inside a VM (or on any RDP server) directly into GNOME as if they were native applications. WinApps works by:
- Running a Windows RDP server in a background VM container
- Checking the RDP server for installed applications such as Microsoft Office
- If those programs are installed, it creates shortcuts leveraging FreeRDP for both the CLI and the GNOME tray
- Files in your home directory are accessible via the \\tsclient\home mount inside the VM
- You can right click on any files in your home directory to open with an application, too
Currently supported applications
WinApps supports ANY installed application on your system.
It does this by:
- Scanning your system for offically configured applications (below)
- Scanning your system for any other EXE files with install records in the Windows Registry
Any officially configured applications will have support for high-resolution icons and mime types for automatically detecting what files can be opened by each application. Any other detected executable files will leverage the icons pulled from the EXE.
Note: The officially configured application list below is fueled by the community, and therefore some apps may be untested by the WinApps team.
 | Adobe Acrobat Pro (X) | | Adobe Acrobat Reader (DC) |
| Adobe After Effects (CC) | | Adobe Audition (CC) |
| Adobe Bridge (CS6, CC) | | Adobe Creative Cloud (CC) |
| Adobe Illustrator (CC) | | Adobe InDesign (CC) |
| Adobe Lightroom (CC) | | Adobe Photoshop (CS6, CC) |
| Adobe Premiere Pro (CC) | | Command Prompt (cmd.exe) |
| Explorer (File Manager) | | Internet Explorer (11) |
| Microsoft Access (2016, 2019, o365) | | Microsoft Excel (2016, 2019, o365) |
| Microsoft Word (2016, 2019, o365) | | Microsoft OneNote (2016, 2019, o365) |
| Microsoft Outlook (2016, 2019, o365) | | Microsoft PowerPoint (2016, 2019, o365) |
| Microsoft Project (2016, 2019, o365) | | Microsoft Publisher (2016, 2019, o365) |
| Powershell (Standard, Core) | | Visual Studio (2019 — Ent|Pro|Com) |
| Windows (Full RDP session) |
Step 1: Set up a Windows Virtual Machine
The best solution for running a VM as a subsystem for WinApps would be KVM. KVM is a CPU and memory-efficient virtualization engine bundled with most major Linux distributions. To set up the VM for WinApps, follow this guide:
If you already have a Virtual Machine or server you wish to use with WinApps, you will need to merge kvm/RDPApps.reg into the VM’s Windows Registry. If this VM is in KVM and you want to use auto-IP detection, you will need to name the machine RDPWindows . Directions for both of these can be found in the guide linked above.
Step 2: Download the repo and prerequisites
To get things going, use:
Step 3: Creating your WinApps configuration file
You will need to create a
/.config/winapps/winapps.conf configuration file with the following information in it:
The username and password should be a full user account and password, such as the one created when setting up Windows or a domain user. It cannot be a user/PIN combination as those are not valid for RDP access.
- When using a pre-existing non-KVM RDP server, you can use the RDP_IP to specify it’s location
- If you are running a VM in KVM with NAT enabled, leave RDP_IP commented out and WinApps will auto-detect the right local IP
- For domain users, you can uncomment and change RDP_DOMAIN
- On high-resolution (UHD) displays, you can set RDP_SCALE to the scale you would like [100|140|160|180]
- To add flags to the FreeRDP call, such as /audio-mode:1 to pass in a mic, use the RDP_FLAGS configuration option
- For multi-monitor setups, you can try enabling MULTIMON , however if you get a black screen (FreeRDP bug) you will need to revert back
- If you enable DEBUG , a log will be created on each application start in
Step 4: Run the WinApps installer
Lastly, check that FreeRDP can connect with:
You will see output from FreeRDP, as well as potentially have to accept the initial certificate. After that, a Windows Explorer window should pop up. You can close this window and press Ctrl-C to cancel out of FreeRDP.
If this step fails, try restarting the VM, or your problem could be related to:
- You need to accept the security cert the first time you connect (with ‘check’)
- Not enabling RDP in the Windows VM
- Not being able to connect to the IP of the VM
- Incorrect user credentials in
/.config/winapps/winapps.conf
Then the final step is to run the installer which will prompt you for a system or user install:
This will take you through the following process:
Adding pre-defined applications
Adding applications with custom icons and mime types to the installer is easy. Simply copy one of the application configurations in the apps folder, and:
- Edit the variables for the application
- Replace the icon.svg with an SVG for the application (appropriately licensed)
- Re-run the installer
- Submit a Pull Request to add it to WinApps officially
When running the installer, it will check for if any configured apps are installed, and if they are it will create the appropriate shortcuts on the host OS.
Running applications manually
WinApps offers a manual mode for running applications that are not configured. This is completed with the manual flag. Executables that are in the path do not require full path definition.
Checking for new application support
The installer can be run multiple times, so simply run the below again and it will remove any current installations and update for the latest applications.
Optional installer command line arguments
The following optional commands can be used to manage your application configurations without prompts:
- Black window: This is a FreeRDP bug that sometimes comes up. Try restarting the application or rerunning the command. If that doesn’t work, ensure you have MULTIMON disabled.
- Some icons pulled from
- Fluent UI React — Icons under MIT License
- Fluent UI — Icons under MIT License with restricted use
- PKief’s VSCode Material Icon Theme — Icons under MIT License
- DiemenDesign’s LibreICONS — Icons under MIT License
About
Run Windows apps such as Microsoft Office/Adobe in Linux (Ubuntu/Fedora) and GNOME/KDE as if they were a part of the native OS, including Nautilus integration.
Источник
raelgc / Install MSOffice on Ubuntu.md
Install Microsoft Office 2010 on Ubuntu
We’ll install MSOffice using the PlayOnLinux wizard. Additionally, MSOffice requires samba and winbind to properly work.
So, if not installed, install them:
Of course, you’ll need the MSOffice installer files (either DVD/folder files), in the 32 bits version. Even if you’re under Ubuntu 64, we’ll use a 32 bits wine installation.
Then open POL (PlayOnLinux) from command line ( playonlinux & ) or using Dash.
In the POL window menu, go to Tools > Manage Wine versions and install Wine 2.13 . Versions below it will crash after click on a document hyperlink. Versions above it will not properly handle the launcher icon (due missing WM_CLASS when window is maximized).
In the POL window, click on Install at top (the one with a plus sign).
1. PlayOnLinux Install menu
At the Install window, at the bottom, select Office and make sure Commercial (at top) is marked.
Now select Microsoft Office 2010 and click on Install .
2. Welcome to PlayOnLinux Installation Wizard
Nothing to do here other then click on the Next button.
3. Please Choose an Installation Method
Now it’s up to you: select DVD or file installation according your MSOffice installation.
Then click on Next .
Browse the files or the DVD: the goal here is select the MSOffice setup.exe , from the 32 bits version.
Now, after click on Next : you’ll see a sequence of PlayOnLinux installation windows, configuring the new Windows virtual drive, installing components, etc.
4. The MSOffice Install Wizard
Automatically the MSOffice installer will be displayed.
Install the MSOffice as on Windows: agree with EULA, select install type, etc.
In the last Install window, click on Close in the MSOffice installer: you’ll see a PlayOnLinux window still running some additional configurations.
Then, a successful message: click on Next and the install window will be closed.
Now you can close PlayOnLinux.
1. Desktop Files
Current PlayOnLinux Office2010 script already creates the below shortchuts.
But in case you deleted them or want to fix something.
Let’s create some .desktop files to provide better integration into Ubuntu: you can associate typical MSOffice files, like .docx to Word; at Dash, type winword to run Word, etc.
Open a text editor (like gedit , nano or vim ) and create 3 files under
/.local/share/applications , with the following names and contents.
Please, replace /home/ (at the Icon line) by your home folder path:
After create those 4 files, open a terminal ( Ctrl+Alt+T ) and run this command to refresh the Dash entries:
One clarification: the env XMODIFIERS=» command in the Exec line is to prevent wine to change keyboard behavior (sometimes while using wine the keyboard uses a different layout, so accents will not work properly, etc).
If you have a printer properly configured under Ubuntu, probably it’ll be automatically available to MSOffice under wine.
If not, we can make it available. Basically, your printer must be installed using cups . No problem if the printer is installed using other softwares/drivers, but to get it available for wine, it must be installed under cups too.
If cups package is not installed, install it:
Then, open http://localhost:631/ and add your printer.
After configure it, print a test page using the related printer in Printers from System Settings .
Now, make sure you have this file: /etc/printcap . If it’s not present, create it this way:
Reboot wine: open PlayOnLinux, click Configure , select Office2010 , click on Wine tab and click on Windows reboot button.
3. Fix Alternate between Excel windows
When you open 2 files in Excel, and click on Excel icon in the launcher by the second time to see opened files (Expose), you’ll see a weird behavior: one window properly rendered, and the second with just a single icon.
To fix this, open Excel, then File > Options > Advanced > General and check Ignore other applications that use Dyanamic Data Exchange (DDE) .
Then, to alternate between Excel files, on Excel click on View tab and then click on Alternate Windows .
Источник
Microsoft office linux github
Hacky Electron wrapper for Microsoft Office
This is a unofficial, unsupported (really, I just hacked this in a weekend, keep your expectations very low, folks) cross platform Electron wrapper for Office 365 and Office consumer web interfaces, so you have have a consistent, fast, closer to a native-like experience across platforms, including Linux.
Most of this project is a shameless copy of the nice work that Howard (https://github.com/eNkru/freelook) started by creating an Electron wrapper for Outlook consumer and then Tom (https://github.com/tomlm/electron-outlook) extended by adding support for Outlook 365 (so you can use with your Azure AD accounts). I’m expanding it further for all of Office, so you can use Word, Excel OneNote, PowerPoint, OneDrive, Skype, etc.
Do expect (many) bugs and security issues.
(Note: If you came here looking for Microsoft Teams for Linux, please use the official client: https://aka.ms/get-teams-linux)
Latest features and notes
- The icon of the app changes according to the application you are currently using (most of the time)
- You can navigate from Word to Excel, to OneDrive, to Outlook, etc. all in the same window (use the Office menu at the top left corner)
- Disabled nodeIntegration — I believe OneDrive’s JavaScript plumbing requires this to be off
Here’s what it looks like:
Office 365 on Ubuntu:
Editing a Word doc on Ubuntu:
Switching between apps:
(yes, it does work on Windows. I haven’t tested on Mac but it should work there too, I guess?)
Why would you do such a thing? Just use the browser!
Short answer: Yes
Long answer: Tom talks about his motivation to use this as his Outlook client, on Windows, instead of the native client (https://github.com/tomlm/electron-outlook):
«I have found that the Outlook Web application a great email client for a number of reasons.
- It always is running the latest without upgrading.
- It gets new features faster (such as sweep)
- It starts fast and is really responsive.
- etc
The one thing that has prevented me from adopting it is the fact that it runs as a browser tab.
- It gets lost in the soup of other tabs
- It is harder to get to my email tab because it isn’t on my active app list
- Browser hot keys sometimes interact with the application
- It doesn’t give me notifications when the brower goes away etc.»
Besides, it does feel very nice to see that running on Linux.
How to use or contribute to this
There are two key folders here:
- Consumer: Use this if you use Office with a Microsoft Account (e.g. Hotmail, Outlook.com, etc)
- Office365: Use this if you use Office with an Active Directory account (an Office 365 subscription)
The URLs are often different, plus the credentials you will be using as well, so it makes sense to separate these, especially if you intend to save your credentials.
In each folder you will find two different Electron applications:
- Outlook: This is mostly a copy from Tom’s code, it’s the original Electron app focused on enabling Outlook
- Office: While this should also work with Outlook (it contains most of the code from the Outlook folder), it defaults to opening OneDrive where you have a menu to get you to any of Office, plus a bunch of additional code that should enable using the different Office applications on the web
Download and Install
If you just want to download the installers, go here.
May the Force be with you.
Clone the repository and run in development mode.
(Highly recommend using Visual Studio Code for both editing this code and debugging)
Build the application
This will build an AppImage in the dist folder. This file can be run in most popular linux distributions.
Hate it? Want to contribute?
There are many things I could use help with here. Such as:
- General bug fixing (I’ve never built anything in Electron before so. ¯\_(ツ)_/¯ )
- Fixing Icons (I just used screen shots for now so they aren’t great)
- For Office 365 clients, fix the auth issues for other ADFS clients and non ADFS scenarios (auth will probably fail today if you fall in that bucket)
- Better keyboard shortcuts
- Better navigation/menus
- Better testing across platforms
- More control for when to launch things directly on the browser?
- Better code reuse (so far the consumer and the Office 365 editions are almost the same code with small differences, shouldn’t need to duplicate the whole thing)
- Would be nice if it recognized file extensions, automatically opened them and uploaded them to your OneDrive, then into the online editor?
- Other ideas?
Источник
