threerings / react Goto Github PK

A signals/slots plus FRP-like library for Java and Objective-C

License: Other

Scala 0.39% Java 99.61%

react's Introduction

React

React is a low-level library that provides signal/slot and functional reactive programming-like primitives. It can serve as the basis for a user interface toolkit, or any other library that has a model on which clients will listen and to which they will react.

API docs are available.

Building (Java)

The library is built using SBT or Maven.

Invoke sbt publish-local to build and install the library to your local Ivy repository (i.e. ~/.ivy2/local).

Invoke mvn install to build and install the library to your local Maven repository (i.e. ~/.m2/repository).

Building (Objective-C)

The Objective-C library is distributed as an Xcode project with no external dependencies. Add react.xcodeproj to your project, add /path/to/react/src/main/objc to your user header search paths, and add #import "React.h" to your project's pre-compiled header.

Artifacts

To add a React dependency to a Maven project, add the following to your pom.xml:

<dependencies>
  <dependency>
    <groupId>com.threerings</groupId>
    <artifactId>react</artifactId>
    <version>1.5.1</version>
  </dependency>
</dependencies>

To add it to an Ivy, SBT, or other Maven-repository-using build configuration, simply remove the vast majority of the boilerplate above.

If you prefer to download a pre-built binary, that can be found here:

react-1.5.1.jar

GWT

React is also usable from GWT. Add the jar to your project per the above instructions and add the following to your .gwt.xml file:

<inherits name="react"/>

Distribution

React is released under the New BSD License. The most recent version of the library is available at http://github.com/threerings/react

Contact

Questions, comments, and other communications should be directed to the Three Rings Libraries Google Group.

react's People

Contributors

Stargazers

Watchers

Forkers

aidanns groves carrot-garden sangohan kleopatra999 tomfisher karthiknaidu81

react's Issues

StackOverflowError on old android devices

Code like

ValueView<SomeObj> view;
...
void crashReact() {
for (int i = 0; i < 500; i++) {
ValueView.Listener<SomeObj> omg = this::handleSomeObjChange;
view.connectNotify(omg);
}
}

will crash react compiled into android project, if was launched on android 4.4 for example:

03-12 19:58:05.371 3470-3470/my.pid E/AndroidRuntime: FATAL EXCEPTION: main
Process: my.pid, PID: 3470
java.lang.StackOverflowError
at react.Cons.insert(Cons.java:106)
at react.Cons.insert(Cons.java:106)
at react.Cons.insert(Cons.java:106)
at react.Cons.insert(Cons.java:106)
at react.Cons.insert(Cons.java:106)

This is due to recursion in Cons.insert(), Cons.remove() e t.c.

I'll place pull-request today

RFuture.sequence returns a RFuture that never completes when called for an empty collection

Currently when calling react.RFuture#sequence for an empty collection, it returns a RFuture that never completes. I think it makes sense to return a completed RFuture here.

My use-case is that I build the collection programmatically and it being empty basically means "Nothing to do, so I am done".

Same goes for react.RFuture#collect.

RFuture.sequence misnamed?

sequence, in the context of code that's waiting on a bunch of async operations, reads to me like those ops are going to be performed in sequence, which is of course not the case. What about something like join instead?

Priority confusion

I recently needed priority in the AS version of react (which is a direct port of Java react by Tim), and was very surprised to see that my int.MIN_VALUE priority connection executed before my priority 0 connection:

https://github.com/threerings/react/blob/master/src/main/java/react/Cons.java#L93

Since that behavior was simply copied from here, I'm wondering if that was intentional, or an oversight? (although Tim points out that oversight seems unlikely since there is a unit test specifying that behavior).