enso-org/enso
1
1
Fork 0
mirror of https://github.com/enso-org/enso.git synced 2024-12-27 00:43:27 +03:00
Code Issues Projects Releases Wiki Activity
4cbd5f45a1
enso/lib/rust/ensogl/component/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

27 lines
940 B
TOML
Raw Normal View History

Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
[package]
name = "ensogl-component"
version = "0.1.0"
authors = ["Enso Team <contact@enso.org>"]
Switch to 2021 edition (#3173)
2021-12-01 18:06:57 +03:00
edition = "2021"
Refactored config crate + moving crates to lib/rust directory. (#3155)
2021-11-12 15:56:23 +03:00
[dependencies]
Return creating node with (+) button & fix a regression (#3338) * Creating a new node with the (+) button (#3278) [The Task](https://www.pivotaltracker.com/story/show/180887253) A new (+) button on the left-bottom corner appeared. It may be clicked to open searcher in the middle of the scene, as an alternative to tab key. https://user-images.githubusercontent.com/3919101/154514279-7972ed6a-0203-47cb-9a09-82dba948cf2f.mp4 * The window_control_buttons::common was extracted to separate crate `ensogl-component-button` almost without change. * This includes a severe refactoring of adding nodes in general in the Graph Editor. The whole responsibility of adding new nodes (and starting their editing) was moved to Graph Editor - the Project View only reacts for GE events to show searcher properly. * The status bar was moved from the bottom-left corner to the middle-top of the scene. It does not collide with (+) button, and plays "notification" role anyway. * The `interface` debug scene was buggy. The problem was with one expression's span-tree. When I replaced it, the scene works. * I've removed "new searcher" API, as it is completely outdated. * I've changed code owners of integration tests to GUI team, as it is the team writing mostly the integration tests (int rust) * Fix regression #181528359 * Add docs & remove unused function * Fix & enable native Rust tests * Fix formatting Co-authored-by: Adam Obuchowicz <adam.obuchowicz@enso.org> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
2022-03-16 21:02:47 +03:00
ensogl-button = { path = "button" }
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
ensogl-drop-down-menu = { path = "drop-down-menu" }
Grid-view based dropdown component (#3985) Implements https://www.pivotaltracker.com/n/projects/2539304/stories/184023380 Dropdown component. Planned to be used in nodes as a single and multiple selection widget, both for static and dynamically loaded values. Initial support is focused on static data, with limited support for dynamic sources. Notably, loading states are not supported yet. Full support for that is planned to be added later with widget lazy-loading. - Supports single and multiple selections. - Dedicated API for providing a static list of all entries. - Range-based query API for dynamically loading data as it is scrolled (only basic support - will need more work for proper async lazy-loading). - Internal entry cache and query batching to avoid querying data one by one (the batching for now is very basic, will have to be improved for proper lazy-loading). - Automatic dropdown width adjustment based on the entry label lengths, up to a set max allowed value. - Open and close animation. - Keyboard support for focusing and selecting entries. ![image](https://user-images.githubusercontent.com/919491/207866293-de2e3fef-c93b-48cc-8253-11c186d223fd.png) # Important Notes Implementing the dropdown on top of grid-view have uncovered some assumptions around grid-view layers. It was assumed to always be a part of the component browser. Removing that assumption required a mechanism for propagating camera update information through layer tree. This is now implemented using a `camera_parent` layer field. Ideally each layer should simply have at most a single parent, and camera inheritance would follow that. That refactor turned out to be quite involved, so right now the simpler temporary solution is introduced in order to not delay this PR further.
2022-12-22 21:19:40 +03:00
ensogl-drop-down = { path = "drop-down" }
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
ensogl-drop-manager = { path = "drop-manager" }
Precompute MSDFs (#5811) Precompute MSDFs for all ASCII glyphs; after this, we no longer spend any time on MSDF computations when loading or interacting with the example projects. Also shader precompilation (during build) is now parallel; if you have many cores and an SSD, it's now practically instant. Closes #5722. # Important Notes - The *dynamic-assets* mechanism now used for MSDF data and shaders is versatile, and could be used to pre-seed any other computation-intensive runtime caches.
2023-03-10 15:59:56 +03:00
ensogl-dynamic-assets = { path = "dynamic-assets" }
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
ensogl-file-browser = { path = "file-browser" }
Flame Graph for Profiling Data (#3297) Add an API to create a flame graph from profiling data. Also adds a demo scene showcasing the functionality that generates some profiling data by measuring dummy function calls and rendering a flame graph for the dummy data (see video for the result). Not that the functionality is not yet exposed user-facing in the GUI itself, but only as API and demo scene, therefore [ci no changelog needed] https://user-images.githubusercontent.com/1428930/155118977-ecac0628-777c-48bd-9aa7-30ee6aef1976.mp4 # Important Notes * Change from the initial design: labels are shown on the flame graph instead of as a tooltip. This is because tooltips are currently only implemented in the graph editor and would require some additional refactoring (probably taking the better part of a day). * re-instated the behaviour that logs are shown in the JS console if development mode is active.
2022-03-04 01:23:27 +03:00
ensogl-flame-graph = { path = "flame-graph" }
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
ensogl-label = { path = "label" }
Vector Editor first visual implementation (#6245)
2023-04-19 05:26:01 +03:00
ensogl-list-editor = { path = "list-editor" }
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
ensogl-list-view = { path = "list-view" }
Grid View with Scrolling (#3588) **Note**: This PR also contains content of previous Grid View PR. We decided to discard the previous, because this one did some refactoring of old one, and it's not a big addition. Added a scrollable::GridView component, which just embeds the GridView in ScrollArea. Also, re-worked the idea of text layers. https://user-images.githubusercontent.com/3919101/179020359-512ee127-c333-4f86-bff5-f1cb4154e03c.mp4
2022-07-19 11:39:23 +03:00
ensogl-grid-view = { path = "grid-view" }
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
ensogl-scroll-area = { path = "scroll-area" }
ensogl-scrollbar = { path = "scrollbar" }
ensogl-selector = { path = "selector" }
ensogl-shadow = { path = "shadow" }
ensogl-text = { path = "text" }
Implement multi-process message visualisation. (#3423) Implements a visualization that is integrated with our GUI profiling visualization for the multiprocess data implemented in #3395 https://user-images.githubusercontent.com/1428930/165915395-c850c7b2-1cc5-4eb0-8f21-37565d113b1e.mp4 The visualization shows a horizontal line for Engine, Language Server and GUI and renders arrows for each message passed between them. Information about the message is revealed on hover. # Important Notes * this PR refactors the tooltip mechanism. Note that this has not been in active use anywhere else, as tooltips for node received a custom implementation and the tooltip that was previously implemented was used nowhere else yet. [ci no changelog needed]
2022-05-03 12:40:27 +03:00
ensogl-tooltip = { path = "tooltip" }
While testing, developers should not have to wait for each crate to be re-built. (#3168) Split all the EnsoGL components, examples and debug scenes to separate crates, so the work on the single component should be quicker than before.
2021-11-30 14:27:50 +03:00
ensogl-toggle-button = { path = "toggle-button" }
Implement loading spinner for visualisations. (#6512) Fixes #5088. Adds a ensoGL spinner for visualizations waiting on data. https://user-images.githubusercontent.com/1428930/236801655-67a0ffed-da5d-4e27-8797-cd8126cb86d9.mp4 # Important Notes This spinner will not show up for the duration where visualizations are processing data on the frontend. If this is a concern, visualization need to implement heir own loading spinner, or we need to provide a unified API for them to keep the spinner visible.
2023-05-12 07:41:55 +03:00
ensogl-spinner = { path = "spinner" }
Reference in New Issue Copy Permalink