a00efb28f3
Rewrites node input component. Now the input is composed of multiple widget components arranged in a tree of views with automatic layout. That allows creating complex UI elements on top of the node itself, and further widget positions will be automatically adapted to that. The tree roughly follow the span tree, as it is built by consuming its nodes and eagerly creating widgets from them. The tree is rebuilt every time the expression changes, but that rebuild process reuses as much previously created widgets as possible, and only updates their configuration as needed. Each widget type can have its own configuration options that can be passed to it from the parent, or assigned based on configuration received from the language server. <img width="773" alt="image" src="https://user-images.githubusercontent.com/919491/233439310-9c39ea88-19bc-43da-9baf-1bb176e2724e.png"> # Important Notes For now, all span-tree updates are sent over to the shared Frp endpoint of the whole tree, so there is no mechanism for intercepting them by the parent widgets. One idea would be to use existing bubbling/capturing events on widget display objects for that purpose, but I think existing implementation is simpler and more convenient, and we can always easily change that if we have a use for it. There are some issues with performance due to much more display objects being created on the graph. Expect it to be a little worse, especially at initialization time. |
||
|---|---|---|
| .. | ||
| base | ||
| build | ||
| ci_utils | ||
| ci-gen | ||
| cli | ||
| deprecated | ||
| enso-formatter | ||
| intellij-run-config-gen | ||
| macros | ||
| prettier | ||
| shader-tools | ||
| .gitignore | ||
| README.md | ||
[WIP] Enso CI Build Scripts
The code under this directory is under ongoing intensive development. As such it has not been reviewed or cleaned up yet.
General principles
- Written in Rust.
- Portable. Works on any platform that Enso targets.
- Do not duplicate functionality that is already available in tools being part of our tech stack.
- Supports both developers and CI use-cases (and environments). Developers can call it locally to do anything that CI does.
- Does not require much setup work. Where feasible sets things up for the user.
Concepts
Target
- Can be built locally from sources. Building yields artifacts.
- Artifacts are self-contained to a single filesystem directory.
- Artifacts can be downloaded from a remote location rather than built with the same effect.
- Can contain other targets.
- Artifacts can be platform-specific.
- Artifacts must be releasable as CI run artifacts or release assets.
Usage
While the script is invoked using cargo run, the convenience run script is
provided in the repository root.
The general usage form is:
./run <command> [options]
The command itself is usually a combination of target name and subcommand, like
ide build or backend test.
At every layer, the --help command can be used to get more information. Note
that the information depends on the command, so running ./run --help will not
give you the same information as ./run ide --help nor
./run ide build --help.
Targets
IDE
IDE is the top level target for our project. It consists of GUI and Backend
targets.
Sources consist mostly of TS code for the Electron client and packaging.
Artifacts are platform specific and consist of the single image file.
GUI
GUI is the front-end part of the project. It consists of WASM target.
Sources consist mostly of TS code for the web page that embeds the WASM
binaries.
Artifacts are portable across the platforms and consist of the web page that can be served either using Electron client (as IDE does) or using a web server (like the Cloud version of Enso).
WASM
This is the core of GUI, written in Rust. It has no external dependencies.
Artifacts are portable across the platforms and consist of the single WASM binary accompanied by the JS snippets and glue.
Backend
Backend is the back-end part of the project, as seen from the IDE perspective. It contains a Project Manager bundle that includes:
- Project Manager native image;
- Enso Engine distribution (with the Standard Library);
- GraalVM distribution.
These components are not represented as "Targets" (in terms of build script) but could be and likely will be in the future.