![]() ![]() So basically use Pages, Numbers etc but go in with a fresh and clear mind of what to expect and learn to use them. The killer is that the iOS Numbers app is as powerful as the desktop one so I will sit there with my morning coffee on my iPad and consolidate my banking spreadsheet quite happily. I’ve got to the point I run my entire life off native apple apps only now. As long as you don’t waltz in and use them and expect them to be the same as office was then they work really well. All I do is run some finance spreadsheets and write up the odd letter so I switched to using Numbers and Pages. So a couple of years back I was fed up of salting my eyeballs and said **** it. I’ve spent many an hour on their bugzilla arguing with weird things like it taking 5 minutes to open a document if your printer is offline. ![]() However there’s a severe impedance mismatch between it and every platform it runs on, it’s slow, cranky and quite frankly painful to use. But when they went O365 I decided I didn’t want to pay subscription fees going on and didn’t want to pay up front anymore so I jumped on the LibreOffice bandwagon.įundamentally it’s like using office 2000 with some added niceties. I ran Macs at home during that time and used office for Mac. I used office professionally for nigh on 30 years including developing extensive extensions for it with VSTO on w*****s. This is an ongoing unpredictable part of our work: adapting 8 million lines of code to the latest updated rules, keeping our builds compiling and signing with the latest tool chains.I’ve spent some time on this one. Adaptation to whatever new checks are added for universal apps in the App Store.one where binaries are “fat,” consisting of separate parts for each architecture) Scripts to combine builds for arm64 and x86_64 into one universal app (i.e.Enabling bits we didn’t compile in yet: Firebird, Java (when there is a JDK).The new C++/UNO ABI bridge requires more testing, to ensure the UNO scripting support works smoothly.Post-launch, if you can get an M1 Mac, then help is always most welcome! We have several missing pieces that will require further work, with some unusual low-level bits. Update: as of 2021-02 we have working native M1 binaries in the Apple app-store for users. The more exciting, complex features are not yet tested. We still have some failing unit tests, that need investigation, as well as some other bits, described below.Īll of this means that LibreOffice should start and work on M1! So far it has had only very basic Writer & Calc testing.This allows UNO scripting to work (in theory). Then there is a first attempt at a new C++/UNO ABI bridge – we need to match Apple’s ABI by tweaking Linux’s ARM64 support to match.Patching and fixing of lots of bundled libraries to make them build cleanly.It should now possible to configure and build a native LibreOffice on a Apple Silicon, as well as cross-compiling to x86_64. The status of the workĪll of these changes are in master, or in the gerrit queue getting past our CI automation: Thank you! And thanks too to Tor Lillqvist for his patience and hard work here. This effort is made possible by the kind support of those who buy LibreOffice Vanilla in the Mac app store. As such Collabora joined the Universal App Quickstart Programme back in July and has been doing work on enabling LibreOffice for M1 since then. Nevertheless, given the code size of LibreOffice, for the best performance it makes most sense to have a pre-optimized native binary. Apple ensures this by a translation layer, so that software for Intel Macs can be used, using Rosetta translation. With the launch of the new Apple devices nearing, it is important that suitable software arrives around the same time as new hardware. Here we update you on the status of the work, and what needs to be done. The code needs to be prepared for M1, step by step. This of course means work for Collabora’s LibreOffice team too. It is always an exciting time to see freshly minted ARM based silicon arriving in the form of Apple’s massive shift to the ARM based M1. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |