Skip to content
This repository has been archived by the owner on Sep 7, 2018. It is now read-only.

How to structure the code to allow the Symphony UI to run in ContainerJS #218

Open
ColinEberhardt opened this issue Jun 27, 2017 · 0 comments

Comments

@ColinEberhardt
Copy link
Collaborator

ColinEberhardt commented Jun 27, 2017

Via email from Leslie @ Tick42

If Symphony LLC continue with their plans to ship some kind of Electron based exe (as per the https://github.com/symphonyoss/SymphonyElectron project) to run their new UI and (I assume) host the UI on some LLC web site then how can we structure the code injection so that we could run their UI in a Container.JS implementation such as our own Electron wrapper or OpenFin ?

Currently they don't have to do anything in order to make this work. The UI code, that is deployed on some website, assumes the presence of a ssf object which exposes our APIs.

The SymphonyElectron project injects this API using a preload script.

With our electron implementation we do exactly the same thing.

With OpenFin, once this PR is merged #207 we will also be using preload scripts.

For the browser, a client-side shim is required. In this case the browser API, as implemented by this project https://github.com/symphonyoss/ContainerJS/tree/master/packages/api-browser needs to be added, This would require them to add an additional script tag to their code that is loaded before their Symphony UI code.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

2 participants