purescript-flame VS purescript-concur-core

There's Purescript with two libraries implementing the Elm architecture, flame and elmish (on React). Purescript only targets JS, but that can be embedded in mobile and desktop apps.

I will also add that Flame is a great way to get Elm Architecture goodness in PureScript.

Flame: A PureScript front-end framework inspired by the Elm architecture\ (30 comments)

Im having a good time using https://flamepurs.org/.

Halogen is definitely the most widely-used library (and someone has already posted links for that), but I just wanted to mention Flame, which has some pretty decent getting started documentation.

Thanks u/suntzusartofarse. There is a upcoming version in the works, with new features https://github.com/easafe/purescript-flame/pull/36

1. Application wide state is easy since you can always access state from parent components in child components. The problem occurs when you want to update parent state from child components.

Fortunately, you can make your own abstractions in Concur. For example, you can use a "Wire" - which lets multiple child components share and update parts of the parent's state (https://github.com/purescript-concur/purescript-concur-core/...). Note how this abstraction just uses the high level Concur API, and doesn't depend on the UI backend. With a wire the code might look something like this -

  -- A wire into parent's state, accessible using `with`, and updateable using `wire.send`

Have you looked at signals? AFAICT they are exactly what you are looking for. A signal is just Cofree widget (https://github.com/purescript-concur/purescript-concur-core/blob/master/src/Concur/Core/FRP.purs#L26).