glung / redux-java

The java version of Redux : a predictable state container for apps.

// This project is unmaintained //

▲▲▲ Redux-java ▲▲▲

A java implementation of jvm-redux-api

Integration

Gradle

allprojects {
  repositories {
    ...
    maven { url 'https://jitpack.io' }
  }
}

dependencies {
  compile 'com.github.glung:redux-java:1.0'
}

Maven

<repositories>
  <repository>
      <id>jitpack.io</id>
      <url>https://jitpack.io</url>
  </repository>
</repositories>

<dependency>
  <groupId>com.github.glung</groupId>
  <artifactId>redux-java</artifactId>
  <version>1.0</version>
</dependency>

redux-java's Issues

change notifyStateChanged call order

if a subscriber unregister itself while onStateChanged, some subscribers can't get notified

private void notifyStateChanged() {
    for (int i = 0, size = subscribers.size(); i < size; i++) {
        subscribers.get(i).onStateChanged();
    }
}

should be

private void notifyStateChanged() {
    for (int i = subscribers.size()-1; i >=0; i--) {
        subscribers.get(i).onStateChanged();
    }
}

Deploy to a maven repo

Animating removal/addition of todos in the example apps

In the TODO list example, you have to set the items in the adapter and call the notifyDataSetChanged method instead of one of the more specific methods (e.g. notifyItemRemoved). Note that when calling the more specific methods, it allows RecyclerView to actually perform the removal/addition/change/etc animations.

With all these unidirectional data-flow architectures, it seems they build the UI as a function of the state. I think that's a really enticing concept, but I can't see how something as simple as the issue mentioned above is supposed to work. Is there a way to fix this or is it just a limitation of the architecture?

Write the example todolist-kotlin

Write a version of the todolist app with reducers written in Kotlin. Eventually, use https://github.com/andrewoma/dexx for persistant data structures.

Update README

• Gist
• Add a README per module / example

Motivation

What would be a motivation for such project? Which usecase would it address for someone? At the moment I can only think of Android clients that could potentially use this.

Would be nice to see such a motivation statement in readme file with explanation.

Thanks for awesome work.

Fix the dev-tools-ui for Android style.

Some ui bugs on Lollipop. It needs its own style.

Add a CI build system.

Example without dagger

You have done a great job, I think if you provide examples without dagger this repo will fly

Dagger will just add complexity to people how don't know about it.

Remove the GSON dependency on the dev-tools

Ideally the redux should not have any dependency. GSON have been used for convenience in the dev-tools during the early development phase but could be easily removed.