I don't think Adobe would bother with that.
We never know. But i think in that way also. Maybe Sulake pays Adobe for a technical support. Big companies does that, IBM, Oracle, Microsoft...
---
Anyways, the biggest problem of Electron it's that uses Google Chrome containers. So if Chrome officially stop supporting Flash?
Chrome uses the PPAPI Plugins, so even if Chrome disable Flash, will be possible inject the PepperFlash Plugin?
Anyways, i'm researching about injecting NPAPI Plugins, (Chrome doesn't support they anymore). I will find to decompile the Package (in case of OS X) of an Pepper Flash Plugin, and try to inject the META Informations into a NPAPI Package (in OS X both are .plugin)
If this works, i can "officially" inject Adobe Shockwave Flash NPAPI Plugin into a PPAPI Plugin.
The poop it's that if the chrome container runs directly on Electron App, i will need pass out the "SANDBOX MODE" of Chrome Plugin Allowance.
Actually the HabClient does a request to the Engine that renders the Client. So it's hosted in a URL and not in File System. (Since Electron allows to Bind External Pages and Electron Pages (both in HTML). But the Electron Pages are loaded through File System.
Chrome as strictly and rigorous security in File System Loaded files.
But already exists tutorials to bypass they.
I will also research the possibility of using a specific version of Chrome (aka Chromium) container.
That will be hard.
But i will try do my best in this project. And obviously this time, releasing it.
This weekend i will resume the commits. And do the things that i explained in my previous post. (Or going as far i can)
Thanks for supporting and reading this project!