Optional widget wrapper

[YooSunYoung]

Fixes #71

I don't like how it looks but it works...

Optional

Switchable & Optional

Screen.Recording.2024-08-13.at.10.10.20.mov

[jokasimr]

I saw this before but didn't understand it. What is a switchable widget? When is it used?

[YooSunYoung]

I saw this before but didn't understand it. What is a switchable widget? When is it used?

@jokasimr
Switchable widget is when you don't want to set the parameter at all in the workflow
and
Optional widget is when you want to set it as None.
It's handled by the attributes of Parameter object, switchable and optional.

Maybe I should add this information in the developer's gui page...

[SimonHeybrock]

I saw this before but didn't understand it. What is a switchable widget? When is it used?

TL;DR: When you have a parameter param: SomeType | None (aka Optional[SomeType]).

[jokasimr]

TL;DR: When you have a parameter param: SomeType | None (aka Optional[SomeType]).

From @YooSunYoung s explanation that sounds more like an optional widget.

[YooSunYoung]

I added the explanation in the developers document

[jokasimr]

Instead of making switchable widgets, maybe we should just add a long multiple-select widget containing all domain types (parameters) in the workflow. When you select some of them, they show up in the ParameterBox widget and you can assign their values. When you select a set of outputs, the multiple select list of parameters selects the required parameters to produce the outputs.

This would help by

1. removing the need to have switchable parameters/widgets, simplifying the gui
2. make it easy to add support for changing intermediate values, the user just needs to select them manually from the parameter multiple select widget

[YooSunYoung]

@jokasimr I created a separate issue regarding your suggestion. #74

[jokasimr]

Maybe it's simpler to use a single checkbox here? That would let us remove the layout code, since we would not have to manually place the two radio elements on the same line.

[jokasimr]

I'm thinking something like:

import ipywidgets as ipw

c = ipw.Checkbox(description='')
s = ipw.Stack([ipw.Label('None'), ipw.Text()], selected_index=0)
ipw.dlink((c, 'value'), (s, 'selected_index'))
ipw.HBox([c, s])

[jokasimr]

Or, same but using .disabled like you did in this PR.

[jokasimr]

But it doesn't matter much. If you think it's better like it is just go with that.

[YooSunYoung]

Yeah I didn't want to use checkbox because we are using it for switchable. Maybe we can update it once we fix the switchable as you suggested...!

[YooSunYoung]

I made this note in the #74

[jokasimr]

see comment above about checkbox, I think that would let us remove this

[jokasimr]

Is this decorator meant to be used elsewhere? Right now it's only used in one place as far as I can tell.
Maybe we can just put the logic inside that function for now and make it a decorator later if the logic is reused elsewhere?

[YooSunYoung]

We can't put it inside because of the singledispatch decorator.
You'll have to do it in every dispatch registered functions.

[jokasimr]

Aha I see