Functional Reactive Properties for observing changes and retaining values

reactify is published to Sonatype OSS and Maven Central currently supporting Scala and Scala.js on 2.11 and 2.12.

Configuring the dependency in SBT simply requires:

libraryDependencies += "com.outr" %% "reactify" % "2.0.0"

or for Scala.js or cross-building:

libraryDependencies += "com.outr" %%% "reactify" % "2.0.0"

This framework is intentionally meant to be a simplistic take on properties and functional reactive concepts. There are only four specific classes that really need be understood to take advantage of the framework:

• Observable - As the name suggests it is a simple trait that fires values and may be observed by listeners.
• Channel - The most simplistic representation of an Observable, simply provides a public := to fire events. No state is maintained.
• Val - Exactly as it is in Scala, this is a final variable. What is defined at construction is immutable. However, the contents of the value, if they are Observable may change the ultimate value of this, so it is is Observable itself and holds state.
• Var - Similar to Val except it is mutable as it mixes in Channel to allow setting of the current value.

Val and Var may hold formulas with Observables. These Observables are listened to when assigned so the wrapping Val or Var will also fire an appropriate event. This allows complex values to be built off of other variables.

Props is a very simple framework and though you'll likely want access to some of the implicit conversions made available in the package, everything can be had with a single import:

import reactify._

As discussed in the concepts there are only four major classes in Props (Observable, Channel, Val, and Var). Of those classes, unless you are creating a custom Observable you will probably only deal with the latter three.

Creating instances is incredibly simple:

val myChannel = Channel[String]           // Creates a Channel that receives Strings
val myVar = Var[Int](5)                   // Creates a Var containing the explicit value `5`
val myVal = Val[Int](myVar + 5)           // Create a Val containing the sum of `myVar` + `5`

This would all be pretty pointless if we didn't have the capacity to listen to changes on the values. Here we're going to listen to myVal and println the new value when it changes:

myVal.attach { newValue =>
  println(s"myVal = $newValue")
}

Since myVal is a Val it is immutable itself, but its value is derived from the formula myVar + 5. This means that a change to myVar will cause the value of myVal to change as a result:

myVar := 10

The above code modifies myVar to have the new value of 10. This will also cause myVal to re-evaluate and have the new value of 15 (myVar + 5). As a result, the listener we attached above will output:

myVal = 15

You can do clever things like define a value that is derived from other values:

val a = Var("One")
val b = Var("Two")
val c = Var("Three")

val list = Val(List(a, b, c))
list()      // Outputs List("One", "Two", "Three")

a := "Uno"
b := "Dos"
c := "Tres"

list()      // Outputs List("Uno", "Dos", "Tres")

This is all pretty neat, but it's the more complex scenarios that show the power of what you can do with Reactify:

val v1 = Var(10)
val v2 = Var("Yes")
val v3 = Var("No")
val complex = Val[String] {
    if (v1 > 10) {
      v2
    } else {
      v3
    }
}

Any changes to v1, v2, or v3 will fire a change on complex and the entire inlined function will be re-evaluated.

A much more advanced scenario is when you have a Var that contains a class that has a Var and you want to keep track of the resulting value no matter what the first Var's instance is currently set to.

Consider the following two classes:

class Foo {
  val active: Var[Boolean] = Var(false)
}
class Bar {
  val foo: Var[Option[Foo]] = Var[Option[Foo]](None)
}

A Bar has a Var foo that holds an Option[Foo]. Now, say I have a Var[Option[Bar]]:

val bar: Var[Option[Bar]] = Var[Option[Bar]](None)

If we want to determine active on Foo we have several layers of mutability between the optional bar Var, the optional foo Var, and then the ultimate active Var in Foo. For a one-off we could do something like:

val active: Boolean = bar().flatMap(_.foo().map(_.active())).getOrElse(false)

This would give us true only if there is a Bar, Bar has a Foo, and active is true. But, if we want to listen for when that changes at any level (Bar, Foo, and active) it should be just as easy. Fortunately with Reactify it is:

val active: Val[Boolean] = Val(bar().flatMap(_.foo().map(_.active())).getOrElse(false))

Yep, it's that easy. Now if I set bar to Some(new Bar) then foo := Some(new Foo) on that, and finally set active to true on Foo my active Val will fire that it has changed. Reactify will monitor every level of the Vars and automatically update itself and fire when the resulting value from the function above has changed.

// Monitor the value change
active.attach { b =>
  ... do something ...    
}

// Set Bar
val b = new Bar
bar := Some(b)

// Set Foo
val f = new Foo
b.foo := Some(f)

// Set active
f.active := true

With Reactify you don't have to do any magic in your code, you just write Scala code the way you always have and let Reactify handle the magic.

As we saw above, Var and Val retain the state of the value assigned to them. A Channel on the other hand is like a Var (in that you can set values to it), but no state is retained. This is useful for representing firing of events or some other action that is meant to be observed but not stored.

The core functionality is complete and useful, but we can build upon it for numeric values that are dependent on other numeric values or numeric values that may have multiple representations. For example, consider a graphical element on screen. It may have a left position for the X value originating on the left side of the element, but if we want to right-align something we have to make sure we account for the width in doing so and vice-versa for determining the right edge. We can simplify things by leveraging a Dep instance to represent it:

val width: Var[Double] = Var(0.0)

val left: Var[Double] = Var(0.0)
val center: Dep[Double, Double] = Dep(left, width / 2.0)
val right: Dep[Double, Double] = Dep(left, width)

Notice we've even added a center representation. These are dependent on left but their value is derived from a formula based on left and width. Of course, if representing the value alone were all we care about then a simple Val(left + width) could be used as our right value, but we also want to be able to modify center or right and have it properly reflect in left. Any changes made to Dep will properly update the variable it depends on left in this case. See DepsSpec for more detailed examples.

Dep also supports conversions between different types as well, but must have an implicit DepConnector available to handle the conversions.

As of 1.6 you can now do two-way binding incredibly easily:

val a = Var[String]("Hello")
val b = Var[String]("World")
val binding = a bind b

By default this will assign the value of a to b and then changes to either will propagate to the other. If you want to detach the binding:

binding.detach()

This will disconnect the two to operate independently of each other again.

You can also do different typed binding:

implicit val s2i: String => Int = (s: String) => Integer.parseInt(s)
implicit val i2s: Int => String = (i: Int) => i.toString

val a = Var[String]("5")
val b = Var[Int](10)
a bind b

We need implicits to be able to convert between the two, but now changes to one will propagate to the other.

• Complete re-write of internal and recursive state system for better modularity and stability
• Observable builder
• Observable from Future
• RecursionMode to better clarify how hierarchical recursion should work
  • Static mode for function-less properties
  • None mode for functional but non-recursive
  • RetainPreviousValue for single-level recursion (new default for performance)
  • Full for complete multi-level recursion
• Transaction system
• Val.dirty and Var.dirty for on-update re-validation of functional reactive properties for performance intensive functionality
• Better recursive integration

• Binding support
  • Different type binding

• Stop Propagation feature
• Listener
• Prioritization support
• Support for chaining Observables to a single listener

• Complete reworking of internals to support more advanced usage
• Removal of Macros as they were creating serious limitations
• Simplified package naming
• Introduced ultra light-weight Prop as a simpler bare minimum alternative to Val
• Better cleanup and re-introduction of StateChannel, State, and Channel as better interface representations.

• Utilization of Macros instead of runtime Observable detection

• Syntactic sugar for dealing with collections in a StateChannel.
• Observable.changes to conveniently see old and new values on change.
• Convenience mutation mod method in StateChannel.

• Dep for dependency representation

• Channel, Val, and Var functionality
• Observable functionality
• Convenience implicits to convert from Val and Var to the value
• Support for value-defined Observable dependencies (Observable State classes used in the makeup of variables are monitored for changes)