-
Notifications
You must be signed in to change notification settings - Fork 35
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
Provide Context Menus #508
Comments
easiest and most generic solution is using a contextmenu listener on the root element and check which element was pressed. |
@thinkh any thoughts on whether that would be compatible with our needs? |
Yes, that would work. The question whether or not we want a context menu for a single cell. In case we want to reduce/remove the toolbar from the column header and move some parts into the context menu, the context menu should be already part of the LineUp library. |
I'd advocate for removing the tool bar from the column header. It results in a lot of buttons and clutters the view. |
What would we have to do to move this forward? |
Are there any updates on this? We'd like to implement context menus for our apps and it would be great if lineup would also support that. Is there anything you need from our side @sgratzl? |
Can we be specific on how this would be implemented? @thinkh could you come up with a proposal please? |
We'd like the ability to use context menus going forward. To do that, we need to develop a way for lineup to trigger context menus, but let an external party (like datavisyn) style and customize them (e.g., remove individual entries, or add new ones based on hooks).
It would also be good if LineUp and datavisyn used the same library to do context menus; I think lineup is using popper.js for menus, and datavisyn wants to use popper.js for tool tips, but might be using bootstrap for menus?
The text was updated successfully, but these errors were encountered: