-
Notifications
You must be signed in to change notification settings - Fork 0
Feature proposals
Currently, each filter syntax will be re-evaluated each time new data comes along. Different possibilites includes:
- Memoization
- Accept compiled syntax enabling pre-compilation
- Modify version of bind filter to get pre-compiling type of filters.
3 looks like the way to go as bound filters can also make the adaptation and distribution declaration more readable.
Currently there is a mismatch between the initialization (isConnected=false
because the connection has not been established yet) where the application receives a default context and data value, and the disconnected state where it receives nothing but isConnected
.
Ability to specify target context property in the Reacolo grammar itself, allowing OR cases with context property
E.g. roles:(phone & watch) | activity:walking
E.g., Panelrama’s optimization with Reacolo.
I.e. Context
that does not need to be contained in a Filter
.
- Reacolo alone should be easy (just need to connect
Filter
) - Creation of a Middleware for the synchronization?
- Implements a Cordova plugin for easy creation of native application using Reacology
- It is possible to use a Cordova plugin with react native (may be the way to go)
- But it looks a bit troublesome
- Reacolo is not good at cross-device interaction because it is not easy to create state mutation from sources coming from different devices.
- One idea would be to use reducers, running on only one of the devices (and only able to access the state) to merge the data. Of course, it implies that this reducer is able to ‘listen’ to events.
- RxJs?
Currently the ecology bridge only support data sync but not events.
Enable to setup non graphical UI IoT node (e.g. lightbulb) inside the reacolo syntax. The goal is to be able to integrate these components as UI component themselves.