Signal of UI wording not clearly defined, making it difficult to understand relationship and interaction between Signals, UI and Reactive Programming.
Revised first paragraph to outline meaning and relationships
Changedfrom : Reactive programming is a style of event-driven programming with signals of data
to : Reactive programming is a style of event-driven programming based on signals.
Changedfrom: A signal is a value that can change over time.
to : A signal is a change/update in a data value which can also be linked/associated with a UI object/widget to form a UI Signal which is triggered by event and/or change in state of a UI. A UI is not required to use the Signal Communication paradigm. A UI Signal is a specific case of Signaling communication, it is a Signal which is associated with a UI Object/Widget.
Changedfrom : Creating a signal of UI using these signals
to : Creating a UI Signal(s) by associating a UI object/widget (asset) with a signal(s)
Signal of UI wording not clearly defined, making it difficult to understand relationship and interaction between Signals, UI and Reactive Programming.
Revised first paragraph to outline meaning and relationships
Changed from : Reactive programming is a style of event-driven programming with signals of data to : Reactive programming is a style of event-driven programming based on signals.
Changed from: A signal is a value that can change over time.
to : A signal is a change/update in a data value which can also be linked/associated with a UI object/widget to form a UI Signal which is triggered by event and/or change in state of a UI. A UI is not required to use the Signal Communication paradigm. A UI Signal is a specific case of Signaling communication, it is a Signal which is associated with a UI Object/Widget.
Changed from : Creating a signal of UI using these signals to : Creating a UI Signal(s) by associating a UI object/widget (asset) with a signal(s)