How does Google decision to phase out Apps affect us?

Added by Pirm Okas over 1 year ago

So, I just found out today Google is determined to kill Google Apps on all platforms except Chrome OS.

In early 2018 Chrome users on Windows, macOS or Linux will no longer be able to open apps they already have installed or install new ones

http://www.omgchrome.com/not-joke-google-killing-chrome-apps/

So, in order to have Chrome NaCl version of Movian still working post-early-2018, one should take action and backup their Movian app from existing installation. It is necessary to do since there is no official download link for it and only possible way to get the app is via Chrome Web Store.

Extracted version can then simply be loaded via "chrome://extensions/ ==> Load unpacked extension" with Developer mode checkbox being set. I'm attaching latest available version.

Tested it on Iron Portable 58 (anonymized fork of Chrome). All is good and OpenGL works.

nmgfcbigejokjgholnnnipegblickgnp.zip - Movian 5.0.488_0 - Native Client, Windows (13.4 MB)

nmgfcbigejokjgholnnnipegblickgnp.zip - Movian 5.0.488_0 - Native Client (13.4 MB)


Replies (16)

RE: How does Google decision to phase out Apps affect us? - Added by Pirm Okas over 1 year ago

And one more thing, are there any instructions on how to build NaCl version from git sources? Seems like every platform has one-liner for building except for Chrome.

EDIT: Nevermind, I figured it out.

https://movian.tv/boards/25/topics/10865

RE: How does Google decision to phase out Apps affect us? - Added by Andreas Smas over 1 year ago

Yeah I've read all of this as well. It's sad for sure but not so unexpected as they already deprecated Chrome apps.

I'm not sure it will even be possible to run (p)NaCL binaries in the future either so you probably need to keep
a copy of Chrome around as well.

RE: How does Google decision to phase out Apps affect us? - Added by Pirm Okas over 1 year ago

So I thought keeping the archive of Portable or Install version of any of Chrome forks, like Chromium or Iron should suffice. However, I just found out none of the installers actually come with pNaCL libraries. They get pulled from Google servers and saved to the profile folder on demand or when user explicitly enables it via chrome://components. I don't think this has been discussed anywhere on the web.

So for future backup purposes I made an archive of latest or quite possibly the last version of pNaCL libraries, both 32bit and 64bit versions.

Archive should be extracted into Profile's data folder. For instance:

Chromium Portable (32bit): ChromiumPortable\Data\Profiles\pnacl\
Iron Portable (64bit): IronPortable64\Profile\pnacl\

So... keeping an install/portable version of Chrome and those pNaCL libraries should make us future proof when Google Apps and support for Native Client actually gets shut down.

0.57.44.2492_32.zip - x86_32 (5.4 MB)

0.57.44.2492_64.zip - x86_64 (6.21 MB)

RE: How does Google decision to phase out Apps affect us? - Added by Pirm Okas over 1 year ago

Running pNaCL under Ubuntu flavoured distibutions is also still possible. However, Chromium that is available via official repositories comes without compiled support for Native Clients. The only easy way is to use Chrome that is supplied via Google made .deb packages.

There's also a caveat that Google Chrome doesn't support 32bit systems anymore since version 48, but that doesn't really change anything since we're only interested in making a backup for Chrome install to be able to use Movian in the future. And that old version supports it just fine. Google it if you need it. As for x86_64 systems, as of date stable version number 59 is running decent with Movian. Still a few crashes while launching or exiting, but it's rock solid while actually runnning.

So I'm attaching a few files for (my own) backup purposes. Chrome 59 (64bit). Also, reattaching (same version as above) Movian 5.0.488 and pNaCL libraries for x86_64 (again, probably the same files as above used for Windows). Always good to have some mirrors.

Path for Portable Native Client component:

~/.config/google-chrome/pnacl/0.57.44.2492/_platform_specific

Path for Movian:

~/.config/google-chrome/Default/Extensions

Have fun in the future in case anyobody in interested in maintaining ability to use Movian in Chrome under Linux once Google phases Native Clients completely out.

RE: How does Google decision to phase out Apps affect us? - Added by Zamar Ac about 1 year ago

Please update to Movian-5.0.490 the Movian plugin for Windows Chrome. We don't know if and when Google will decide to phase out Google Apps, in particular on Windows platform, so its counterproductive and grossly unfair to stop updating Movian Chrome plugin long before that presumed time, since its used by many people on Windows, which is the most popular and used OS for decades. :(

RE: How does Google decision to phase out Apps affect us? - Added by Dean Kasabow about 1 year ago

I already compiled 490 a month ago and posted the link here:

https://movian.tv/issues/3291#note-10

RE: How does Google decision to phase out Apps affect us? - Added by Zamar Ac about 1 year ago

Thanks Dean! :)

Apart from DVB subtitles, are there any other changes? Also, is it possible to fix clipboard support, so Copy - Paste would work between Windows Clipboard and Movian Search field, and text fields in Settings? Its always a problem to type lengthy links, with many errors. Or may be some plugin can fix that? This bug was reported fixed here for Mac (https://movian.tv/issues/3074), but it seems to never work in Movian for Windows Chrome.

RE: How does Google decision to phase out Apps affect us? - Added by Dean Kasabow about 1 year ago

No, the only change is to handle DVB subtitles without crashing.

You can always drag & drop a link from your browser to Movian and it will handle it properly. It is not as convenient as clipboard paste, but works.

RE: How does Google decision to phase out Apps affect us? - Added by Pirm Okas about 1 year ago

Hey Dean, could you compile latest 494 build for PNaCl? Thanks.

RE: How does Google decision to phase out Apps affect us? - Added by Zamar Ac about 1 year ago

It looks like Google indefinitely extended for now the previously announced early 2018 date of NaCl apps stop loading by Chrome.

Dec 5, 2017 ( https://blog.chromium.org/2016/08/from-chrome-apps-to-web.html ):
"The Chrome browser will continue to load packaged and hosted apps on Windows, Mac, and Linux beyond the previously announced deprecation timeline. Another update will be posted here when a new date for the Chrome Apps EOL on Windows, Mac, and Linux has been finalized."

However, they still recommend devs to migrate current apps to WebAssembly ( https://developer.chrome.com/native-client/migration ). Is it possible to migrate Movian to WebAssembly? If yes, this is the right time to start this work now. Movian is a great light weight media center many people use on Windows now instead of heavy, complex for users, and always long updating Kodi solution.

RE: How does Google decision to phase out Apps affect us? - Added by Pirm Okas 11 months ago

Hey Dean, please compile build 500 :) Thanks.

RE: How does Google decision to phase out Apps affect us? - Added by Zamar Ac 11 months ago

Pls guys when compiling new builds, always add a changelog if possible.

RE: How does Google decision to phase out Apps affect us? - Added by Andreas Smas 10 months ago

Webassembly doesn't support all the APIs that Movian requires. It doesn't even support multiple threads which Movian uses extensively.

I just read thru https://developer.chrome.com/native-client/migration and there are a lot of "Red Gaps" that Movian requires unfortunately

RE: How does Google decision to phase out Apps affect us? - Added by funny jokes 4 months ago

I want you to thank for your time of this wonderful read!!! I definately enjoy every little bit of it and I have you bookmarked to check out new stuff of your blog a must read blog!
[[http://ludokinggames.com]]

(1-16/16)