Blocks-Backend-Events

[omerXfaruq]

All events are implemented except Tabs. Tabs is not a component in backend.

Closes #723

[pngwn]

@farukozderim I think Tabs should be the same as everything else. It isn't any different functionally from rows, columns or carousel. Grid will probably fall under a similar category.

[abidlabs]

I agree with @pngwn, tab change could be a useful event to track. @farukozderim since Tab is a BlockContext which is a Block, it should also support the set_event_trigger() already, right?

My only additional suggestion here is to have more descriptive docstrings for the event triggers of. Instead :

"""
Parameters:
    fn: function name
    inputs: List of inputs
    outputs: List of outputs
Returns: None
"""

"""
Creates a trigger to call a function when this component is clicked
Parameters:
    fn: the function to call
    inputs: the input components whose values should be used as the inputs to the function
    outputs: the output components whose values should be updated based on the function return values
Returns: None
"""

Otherwise, LGTM.

[abidlabs]

Type of fn should be Callable (here and below)

[omerXfaruq]

updated

[omerXfaruq]

I wanted to clarify meaning of tabs event below, but now it is clarified!
#723 (comment)

[abidlabs]

I wanted to clarify meaning of tabs event below, but now it is clarified!
#723 (comment)

Small clarification, this event is supposed to be triggered when the TabItem is selected from the menu of tabs, right? In that case, should the TabItem event be called click() not change()?

If the idea is that this trigger should be called any time that the selected tab changes, then Tab should have the change() event.

[omerXfaruq]

Ready to merge!