You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As the previous section showed, it's recommended to avoid creating widgets which never end, to allow arbitrary composition. However, at this point it must be pointed out that Concur does allow you to compose never-ending widgets in meaningful ways, as long as you remember that a never ending-widget will only be a Consumer, and not a Producer of meaningful data. (PS: There are ways to get data out of a never ending widget as well. See remoteWidget for an example).
could we add this ways to get data out of a never ending widget as well as an example?
I dont understand how remoteWidget / forkAction / forkActionWithState functions work
The text was updated successfully, but these errors were encountered:
srghma
changed the title
add an example with removeWidget / how to "get data out of a never ending widget" ?
add an example with remoteWidget / how to "get data out of a never ending widget" ?
Jan 30, 2021
A remote widget essentially splits a widget into two parts, a consumer of user events (m void) and a producer of UI updates (m a) that stay remotely connected. You would use it to keep the listeners alive while being able to remove the widget from the UI or returning a result from the widget.
I need to write more documentation on these, but the function is short enough for the source to be read. The reason I haven't spent a lot of time writing more documentation for them is that they never felt very satisfactory to me, and I have been looking for better solutions.
in documentation
https://ajnsit.github.io/concur-documentation/ch03-03-composing-never-ending-widgets.html
could we add this
ways to get data out of a never ending widget as well
as an example?I dont understand how
remoteWidget
/forkAction
/forkActionWithState
functions workrelated to #55
The text was updated successfully, but these errors were encountered: