-
Notifications
You must be signed in to change notification settings - Fork 8.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Layout Phase 2 #49122
Comments
Pinging @elastic/kibana-canvas (Team:Canvas) |
Some suggested additions:
|
Updated the issue to reflect @clintandrewhall's suggestions |
++ @ryankeairns screenshot. We could have a greyed out lock that you just click when the element is highlight, and then in an accordion view be able to select multiple elements. Also, editing a single element in a group of selected or custom elements would be possible here. |
Thanks @timductive, great collection! These, on an initial look, don't seem directly related to the layout engine, ie. fixing or providing them don't appear to need (or solvable by) an Maybe there are just varying definitions of the LE boundary, still it'd be useful to keep the placement and direct manipulation calculations (what I understand under LE - it's just calcs; no DOM involvement) separate from other UI affordances such as menus, context menus, DOM element capture, actual element insertion and update by React etc. (Having said this, it might make sense to have the concept of a "Layout UI" abstraction, because, if such drag&drop is needed elsewhere, it's nice to have a React component encapsulation for all the context menus, future layer/element manipulation side panels, keyboard shortcuts etc.- but currently, these things are not cleanly separated from unrelated menu, button etc. UI, not sure if @cqliu1 thinks it's even feasible to separate though) For clarity, I'm adding a question mark in the original post, and also for these: #23602 should be triaged as the issue isn't clear from the gif (which I filed :🦆🦆🦆:) |
Hey @monfera thanks for taking a look. I agree, what I will do is edit this issue to clearly indicate things that are the Layout Engine and things that are Layout UI and then we can discuss what the right abstractions are. I'll also take a look and re-triage the issues that you mentioned. |
Closing this for the time being as we are currently not prioritizing Canvas layout updates. |
This phase of the layout engine will add some key features and update/fix some previous issues.
Layout Engine
Layers
Next generation tools like Maps and Lens utilize the concept of layers and Canvas should as well. This will help with finding/selecting elements, grouping, manipulating, etc...
Fine-tuned controls
Canvas would benefit from more explicit and fine-tuned controls for how users can layout the page.
Layout UI
Layers
Fine-tuned controls
Right-click menu
Performance
I've taken a best-guess at performance work that is related to the layout engine.
The text was updated successfully, but these errors were encountered: