Open
Description
This is a meta issue to keep track of the things needed to integrate Flexx in JupyterLab, eventually to allow users to create JLab plugins using Flexx. Related discussion in #253.
PR's that are merged:
Export our JS using AMD-compatible modules #225Export our JS using AMD-compatible modules (2) #271 started a major refactoring of the asset system, due to the profound changes, but it being unfinished, many of the PR's below were/will merged into it. Originally, this PR:- Make Flexx export its JS using AMD modules
- Implements its own AMD loaded at
window.flexx.define. - Many subsequent improvements (see the PR for details)
- Automatic assets - js modules match py modules (2) #266 is another significant refactoring of the asset system that automates a lot of things, making the user's life a lot easier.
- More modular CSS (aka JLab integration part 1) #254 Makes Flexx' CSS more modular, avoid conflicts with existing Phosphor CSS on the page, and make it possible to disable all its own phosphor CSS by disabling one
<style>. - Making it possible to run Flexx via a 3d party Tornado app (aka JLab integration part 2) #264 Makes it possible to run Flexx as part of another (i.e. JLab's) Tornado app.
- Add RawJS construct for embedding raw JS and define global instances #290 Makes it easier for Flexx' JS modules to load/define module globals.
- Allow running Phosphor provided by Jupyter #291 Use Phosphor from JLab
- Perhaps we need more changes to make the intended user experience of using Flexx in JLab work. Though we still need to figure out what we want it to look like.