Add a show_widgets option

[digitaltopo]

• Add a show_widgets option so users can choose to suppress the output of the paramnb widgets.
• Add documentation in example notebook

Related to #23, which is stale now.

[jbednar]

Thanks! Here show_widgets is a boolean, but for the purposes of #23, should it be something like "display_type", with values "widgets", "table", "text", or None? Here it seems like you'd need None, but for #23 it would be "table" or "text", I think, with some way to display the values even if they aren't widgets.

[digitaltopo]

@jbednar what would we include inside of the text and table representations? Or are we looking to just output current values?

It may be a bit difficult to output available "options" for each param. For example, a range param, or colorpicker. What would the options be?

If it's just current values then that should be simple. Please confirm, thanks!

[jbednar]

Just current values. Widgets serve two purposes in many cases: allowing selection of a value, and declaring what the selected value is. Even if they fail to allow selection, they can at least declare which value is currently associated with the plot shown. I suppose that they actually serve three cases, in that widgets let you see what values are allowed, but I think that third case is less crucial and as you say, difficult to convey without the widget, so I'm ok with failing to cover that third usage.

[digitaltopo]

@jbednar Added table and text outputs, please take a look.

They still use ipywidgets to output html, but I wanted to avoid bringing in an addition deps like tabulate for the table display.

[philippjfr]

Oh wow, thanks @digitaltopo. Not sure @jbednar was necessarily suggesting you implement these options but it's definitely very welcome.

[digitaltopo]

• Add a show_widgets option so users can choose to suppress the output of the paramnb widgets.
• Add documentation in example notebook

Related to #23, which is stale now.

[jbednar]

Thanks! Here show_widgets is a boolean, but for the purposes of #23, should it be something like "display_type", with values "widgets", "table", "text", or None? Here it seems like you'd need None, but for #23 it would be "table" or "text", I think, with some way to display the values even if they aren't widgets.

[digitaltopo]

@jbednar what would we include inside of the text and table representations? Or are we looking to just output current values?

It may be a bit difficult to output available "options" for each param. For example, a range param, or colorpicker. What would the options be?

If it's just current values then that should be simple. Please confirm, thanks!

[jbednar]

Just current values. Widgets serve two purposes in many cases: allowing selection of a value, and declaring what the selected value is. Even if they fail to allow selection, they can at least declare which value is currently associated with the plot shown. I suppose that they actually serve three cases, in that widgets let you see what values are allowed, but I think that third case is less crucial and as you say, difficult to convey without the widget, so I'm ok with failing to cover that third usage.

[digitaltopo]

@jbednar Added table and text outputs, please take a look.

They still use ipywidgets to output html, but I wanted to avoid bringing in an addition deps like tabulate for the table display.

[philippjfr]

Oh wow, thanks @digitaltopo. Not sure @jbednar was necessarily suggesting you implement these options but it's definitely very welcome.

[digitaltopo]

• Add a show_widgets option so users can choose to suppress the output of the paramnb widgets.
• Add documentation in example notebook

Related to #23, which is stale now.

[jbednar]

Thanks! Here show_widgets is a boolean, but for the purposes of #23, should it be something like "display_type", with values "widgets", "table", "text", or None? Here it seems like you'd need None, but for #23 it would be "table" or "text", I think, with some way to display the values even if they aren't widgets.

[digitaltopo]

@jbednar what would we include inside of the text and table representations? Or are we looking to just output current values?

It may be a bit difficult to output available "options" for each param. For example, a range param, or colorpicker. What would the options be?

If it's just current values then that should be simple. Please confirm, thanks!

[jbednar]

Just current values. Widgets serve two purposes in many cases: allowing selection of a value, and declaring what the selected value is. Even if they fail to allow selection, they can at least declare which value is currently associated with the plot shown. I suppose that they actually serve three cases, in that widgets let you see what values are allowed, but I think that third case is less crucial and as you say, difficult to convey without the widget, so I'm ok with failing to cover that third usage.

[digitaltopo]

@jbednar Added table and text outputs, please take a look.

They still use ipywidgets to output html, but I wanted to avoid bringing in an addition deps like tabulate for the table display.

[philippjfr]

Oh wow, thanks @digitaltopo. Not sure @jbednar was necessarily suggesting you implement these options but it's definitely very welcome.

[digitaltopo]

• Add a show_widgets option so users can choose to suppress the output of the paramnb widgets.
• Add documentation in example notebook

Related to #23, which is stale now.

[jbednar]

Thanks! Here show_widgets is a boolean, but for the purposes of #23, should it be something like "display_type", with values "widgets", "table", "text", or None? Here it seems like you'd need None, but for #23 it would be "table" or "text", I think, with some way to display the values even if they aren't widgets.

[digitaltopo]

@jbednar what would we include inside of the text and table representations? Or are we looking to just output current values?

It may be a bit difficult to output available "options" for each param. For example, a range param, or colorpicker. What would the options be?

If it's just current values then that should be simple. Please confirm, thanks!

[jbednar]

Just current values. Widgets serve two purposes in many cases: allowing selection of a value, and declaring what the selected value is. Even if they fail to allow selection, they can at least declare which value is currently associated with the plot shown. I suppose that they actually serve three cases, in that widgets let you see what values are allowed, but I think that third case is less crucial and as you say, difficult to convey without the widget, so I'm ok with failing to cover that third usage.

[digitaltopo]

@jbednar Added table and text outputs, please take a look.

They still use ipywidgets to output html, but I wanted to avoid bringing in an addition deps like tabulate for the table display.

[philippjfr]

Oh wow, thanks @digitaltopo. Not sure @jbednar was necessarily suggesting you implement these options but it's definitely very welcome.

[digitaltopo]

• Add a show_widgets option so users can choose to suppress the output of the paramnb widgets.
• Add documentation in example notebook

Related to #23, which is stale now.

[jbednar]

Thanks! Here show_widgets is a boolean, but for the purposes of #23, should it be something like "display_type", with values "widgets", "table", "text", or None? Here it seems like you'd need None, but for #23 it would be "table" or "text", I think, with some way to display the values even if they aren't widgets.

[digitaltopo]

@jbednar what would we include inside of the text and table representations? Or are we looking to just output current values?

It may be a bit difficult to output available "options" for each param. For example, a range param, or colorpicker. What would the options be?

If it's just current values then that should be simple. Please confirm, thanks!

[jbednar]

Just current values. Widgets serve two purposes in many cases: allowing selection of a value, and declaring what the selected value is. Even if they fail to allow selection, they can at least declare which value is currently associated with the plot shown. I suppose that they actually serve three cases, in that widgets let you see what values are allowed, but I think that third case is less crucial and as you say, difficult to convey without the widget, so I'm ok with failing to cover that third usage.

[digitaltopo]

@jbednar Added table and text outputs, please take a look.

They still use ipywidgets to output html, but I wanted to avoid bringing in an addition deps like tabulate for the table display.

[philippjfr]

Oh wow, thanks @digitaltopo. Not sure @jbednar was necessarily suggesting you implement these options but it's definitely very welcome.

[digitaltopo]

• Add a show_widgets option so users can choose to suppress the output of the paramnb widgets.
• Add documentation in example notebook

Related to #23, which is stale now.

[jbednar]

Thanks! Here show_widgets is a boolean, but for the purposes of #23, should it be something like "display_type", with values "widgets", "table", "text", or None? Here it seems like you'd need None, but for #23 it would be "table" or "text", I think, with some way to display the values even if they aren't widgets.

[digitaltopo]

@jbednar what would we include inside of the text and table representations? Or are we looking to just output current values?

It may be a bit difficult to output available "options" for each param. For example, a range param, or colorpicker. What would the options be?

If it's just current values then that should be simple. Please confirm, thanks!

[jbednar]

Just current values. Widgets serve two purposes in many cases: allowing selection of a value, and declaring what the selected value is. Even if they fail to allow selection, they can at least declare which value is currently associated with the plot shown. I suppose that they actually serve three cases, in that widgets let you see what values are allowed, but I think that third case is less crucial and as you say, difficult to convey without the widget, so I'm ok with failing to cover that third usage.

[digitaltopo]

@jbednar Added table and text outputs, please take a look.

They still use ipywidgets to output html, but I wanted to avoid bringing in an addition deps like tabulate for the table display.

[philippjfr]

Oh wow, thanks @digitaltopo. Not sure @jbednar was necessarily suggesting you implement these options but it's definitely very welcome.

[digitaltopo]

• Add a show_widgets option so users can choose to suppress the output of the paramnb widgets.
• Add documentation in example notebook

Related to #23, which is stale now.

[jbednar]

Thanks! Here show_widgets is a boolean, but for the purposes of #23, should it be something like "display_type", with values "widgets", "table", "text", or None? Here it seems like you'd need None, but for #23 it would be "table" or "text", I think, with some way to display the values even if they aren't widgets.

[digitaltopo]

@jbednar what would we include inside of the text and table representations? Or are we looking to just output current values?

It may be a bit difficult to output available "options" for each param. For example, a range param, or colorpicker. What would the options be?

If it's just current values then that should be simple. Please confirm, thanks!

[jbednar]

Just current values. Widgets serve two purposes in many cases: allowing selection of a value, and declaring what the selected value is. Even if they fail to allow selection, they can at least declare which value is currently associated with the plot shown. I suppose that they actually serve three cases, in that widgets let you see what values are allowed, but I think that third case is less crucial and as you say, difficult to convey without the widget, so I'm ok with failing to cover that third usage.

[digitaltopo]

@jbednar Added table and text outputs, please take a look.

They still use ipywidgets to output html, but I wanted to avoid bringing in an addition deps like tabulate for the table display.

[philippjfr]

Oh wow, thanks @digitaltopo. Not sure @jbednar was necessarily suggesting you implement these options but it's definitely very welcome.

[digitaltopo]

• Add a show_widgets option so users can choose to suppress the output of the paramnb widgets.
• Add documentation in example notebook

Related to #23, which is stale now.

[jbednar]

Thanks! Here show_widgets is a boolean, but for the purposes of #23, should it be something like "display_type", with values "widgets", "table", "text", or None? Here it seems like you'd need None, but for #23 it would be "table" or "text", I think, with some way to display the values even if they aren't widgets.

[digitaltopo]

@jbednar what would we include inside of the text and table representations? Or are we looking to just output current values?

It may be a bit difficult to output available "options" for each param. For example, a range param, or colorpicker. What would the options be?

If it's just current values then that should be simple. Please confirm, thanks!

[jbednar]

Just current values. Widgets serve two purposes in many cases: allowing selection of a value, and declaring what the selected value is. Even if they fail to allow selection, they can at least declare which value is currently associated with the plot shown. I suppose that they actually serve three cases, in that widgets let you see what values are allowed, but I think that third case is less crucial and as you say, difficult to convey without the widget, so I'm ok with failing to cover that third usage.

[digitaltopo]

@jbednar Added table and text outputs, please take a look.

They still use ipywidgets to output html, but I wanted to avoid bringing in an addition deps like tabulate for the table display.

[philippjfr]

Oh wow, thanks @digitaltopo. Not sure @jbednar was necessarily suggesting you implement these options but it's definitely very welcome.