-
Notifications
You must be signed in to change notification settings - Fork 10
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
Allow preferred modal position to be device-specific #5
Comments
For me at least, Treeview is crucial part of making the switch to Silverbullet, so I too am interested in having this behavior. As I've only deployed Silverbullet the other day, I'm still evaluating it before making the switch. For now, I've done a quick workaround using the new space-style to get this behavior (see video below). If/once I'm committed, I'd be interested in perhaps tackling this. Just in case, do you have a syntax in mind for how the options should be arranged, considering the various dynamic/responsive behavior? treeview-style.mp4 |
I was thinking of adding a button to the treeview toolbar: either a single button that cycles through the various positions, or a button that shows a dropdown of options. We could also add functions for each position to the There could also be an "auto" mode that takes into account screen width, I guess. I think that would be possible. Either way, I think we'd need to remove the main setting entirely. I suppose it could be kept and used as the "default" option, but I think that would be too confusing. But definitely open to alternative ways to handle it! |
That's an interesting approach. So one would define when each of the positions ( If I understood this correctly, one limitation would be that you would only be able to define each position once? For example, if I've setup The other ideas that crossed my mind so far are only some conventional approaches, like setting the default behavior in |
On mobile it might make more sense to open it on the bottom or as a modal. On desktop that preference might be different.
The text was updated successfully, but these errors were encountered: