Just started looking at AppRun last night, and really like the design/concept! Very elegant π
I noticed in the documentation that stateful components are "work in progress" - I was wondering if you can elaborate a little bit?
I'm trying to figure out if this feature (or a planned future feature) satisfies my use-case.
As far as my understanding, components in AppRun are very different from components in, say, React - I think the best way I can explain my understanding of the conceptual difference is, AppRun components are "components of the application", while React components are "components of the UI".
While components in AppRun provide a useful abstraction of a self-contained section of the UI state and view, presumably stateful components will provide an abstraction of UI "controls", e.g. components that have an internal state?
I recently explained it to someone like this:
There is application state, and there is control state.
Control state really pertains only to a control while it exists, and becomes completely irrelevant the moment the control disappears from the user's view: whether a date-picker or drop-down was open, where the cursor was located in an input, and so on - no longer relevant once the control is gone.
We don't need or expect or want such state to persist in the model - most of the time, we don't even care that it exists, for example, we don't typically care if a drop-down is open, we just want a notification when a selection is made.
Am I right to think this is the purpose of stateful components in AppRun?
Will we be able to instanciate these components via JSX, similarly to how all components are instanciated in for example React?
Or where do you see this feature heading?
Thanks :-)