-
Notifications
You must be signed in to change notification settings - Fork 51
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
Context Buttons for Selection and Hover of EditParts #261
Comments
👍 |
Sorry for not responding earlier. I agree that this would be a nice feature, as long as it is optional and doesn't affect existing API. But then I know you know that anyway ;-) |
The current status can be seen in the video. Demo_ContextButton.mp4 |
This issue is stale because it has been open for 90 days with no activity. |
This issue is stale because it has been open for 90 days with no activity. |
This issue is stale because it has been open for 90 days with no activity. |
This issue was closed because it has been inactive for 180 days since being marked as stale. |
@sebHollersbacher and I are currently working on a prototype for a context button infrastructure for the graphical editors of 4diac IDE. This is inspired by the the ContextButtons in Graphiti but we hope to get a bit simpler API.
Based on the Eclipse Platform's Command Infrastructure our first prototype can show buttons on all 4 sides of a Figure. When the user moves mouse to 1 side, it hides all the other sides.
In our work we tried to keep the whole infrastructure as generic as possible. Therefore we think we could upstream it to GEF Classic.
Our approach would be to integrate it in the NonResizableEditPolicy in such a way that it will not affect any existing code. But users who would like to have it would just need to implement a dedicated response in the getAdapter method.
The first version of our prototype can be found in the 4diac IDE Gerrit.
What do you think is this something we should move to GEF Classic or keep it in 4diac IDE.
\cc @pcdavid @Phillipus @ptziegler
The text was updated successfully, but these errors were encountered: