Support resizable elements within dashboard cells about dashboards HOT 3 CLOSED

@dalogsdon says:

We could just look at each direct-child of the output_area and widget-area in the cells, and see if they implement notifyResize(). This would cut down on the number of elements we'd have to search for.

from dashboards.

Searching is probably not a viable solution.
In looking at the iron-resizable-behavior code, the best thing would be to attach a listener for 'iron-request-resize-notification' to each output area or other higher up element. That is the way that resizable elements let the world know about them. Then keep a running list.

An easier approach would be to have control of the created Dom and insert resizable aware elements, but this would mean a deeper tie into polymer.

Gino B.

On Sep 28, 2015, at 10:34 PM, Peter Parente [email protected] wrote:

@dalogsdon says:

We could just look at each direct-child of the output_area and widget-area in the cells, and see if they implement notifyResize(). This would cut down on the number of elements we'd have to search for.

—
Reply to this email directly or view it on GitHub.

from dashboards.

Attached a pull request which updates the Dashboard code based on Gino's comment above. We tested with the following notebook: https://gist.github.com/jhpedemonte/d07b269b3f9b6dc8f8b3. Switching between Notebook and Dashboard views should notify the element to resize, as well as resizing the window or the cell (when in dashboard view).

In order to work with this code, Polymer elements will need to mixin iron-resizable-behavior and listen for the iron-resize event.

A note on sizing relative to the notebook/dashboard cell:
A dashboard cell has an exact width and height specified by the user. However, because a notebook cell's height is determined by its children's height (widget-area and output_area), an element cannot set its height relative to the notebook cell.

from dashboards.