Skip to content
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

Support vertical layout of widgets #805

Closed
philippjfr opened this issue Jul 29, 2016 · 11 comments
Closed

Support vertical layout of widgets #805

philippjfr opened this issue Jul 29, 2016 · 11 comments
Milestone

Comments

@philippjfr
Copy link
Member

philippjfr commented Jul 29, 2016

This has been a recurring feature request. Rather than laying out the widgets next to the plot it should be possible to place the widgets below the actual plot instead. This arrangement is a lot more suitable for pages that have very little space and it should not be hard to do with a small amount of css. The main question is how the user can choose between the vertical and horizontal widget arrangement.

@jbednar
Copy link
Member

jbednar commented Jul 29, 2016

I would vote for allowing all the location options (N,S,E,W) for the widget box -- all of those are valid arrangements, and each is useful sometimes.

There's also the issue of how the widgets are laid out in the box -- for E and W locations, laying them out in a column is probably the only reasonable choice. But for boxes in the N or S locations, 2-3 sliders lay out well horizontally, while any more than that has to be vertical, and in some cases people will want them all just to be in a single vertical column as for paramnb's Widgets() class. So I would think there are two parameters that would be needed:

widget_location: N,S,E,W (or left, right, above, below, or whatever you want to call them) (default E)

widget_layout: row, column (default column)

widget_cols: 1, 2, or 3 (default 1)

@jlstevens
Copy link
Contributor

jlstevens commented Jul 29, 2016

Sounds like options for the output magic. I would vote to tab-complete 'left', 'right', 'top' and 'bottom'.

In addition, I think widget_cols might be sufficient (default 1) where you could just set a very high number if you always want a row layout.

@jbednar
Copy link
Member

jbednar commented Jul 29, 2016

Sounds good. Top vs above is a subtle distinction, about whether it is higher or highest, but that is up to you.

@jordansamuels
Copy link
Contributor

+1 ability to move widgets to top or bottom of HoloMap.

Also remember some gitter discussion:

Wojciech Jaśkowski @wjaskowski Jul 04 08:52
How to change the position of HoloMap widgets? (Normally they are rendered on the right but somehow I accidentally changed them to be at the bottom once)

Philipp Rudiger @philippjfr Jul 04 08:52
They are on the bottom when the CSS is not applied (e.g. if you delete the output of the cell where hv.extension is loaded)
Currently the position isn't easily configurable, although there are workarounds with some CSS.

I'd love to have official support; if difficult, I'd like to see the CSS workaround.

@wjaskowski
Copy link

wjaskowski commented Jul 11, 2017 via email

@jvivian
Copy link

jvivian commented Jan 15, 2018

+1 — I've been wanting to build static pages that use Holomaps.

image

@philippjfr
Copy link
Member Author

Minor update, for dynamic content this is now all possible using http://panel.pyviz.org/. And we have plans to add support for exporting HoloMaps to panel in the near future.

@philippjfr
Copy link
Member Author

This is now supported on master.

@philippjfr philippjfr added this to the v1.13.0 milestone Sep 22, 2019
@basnijholt
Copy link
Contributor

Where can I find documentation on how to do this in v1.13?

@philippjfr
Copy link
Member Author

At some point along the way we lost the renderer/output docs. The easiest way of setting this is:

hv.output(widget_location=['left', 'bottom', 'right', 'top', 'top_left', 'top_right', 'bottom_left',, 'bottom_right', 'left_top', 'left_bottom', 'right_top', 'right_bottom'])

Copy link

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Oct 23, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants