You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+7Lines changed: 7 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -350,6 +350,13 @@ As you can see, we can create and *Dispatch* an *Event* in a single operation. T
350
350
351
351
Now that we've walked through these basic Usage Examples, see if you can produce your own `EventReceiver` to process `TemperatureRatingEvent`s. Everything you need to achieve this has already been demonstrated in this document.
352
352
353
+
## Features Coming Soon
354
+
`EventDrivenSwift` is an evolving and ever-improving Library, so here is a list of the features you can expect in future releases:
355
+
-**Event Pools** - A superset expanding upon a given `EventReceiver` descendant type to provide pooled processing based on given scaling rules and conditions.
356
+
-**`UIEventReceiver`** - Will enable you to register Event Listener Callbacks to be executed on the UI Thread. This is required if you wish to use Event-Driven behaviour to directly update SwiftUI Views, for example.
357
+
358
+
These are the features intended for the next Release, which will either be *1.1.0* or *2.0.0* depending on whether these additions require interface-breaking changes to the interfaces in version *1.0.0*.
359
+
353
360
## License
354
361
355
362
`EventDrivenSwift` is available under the MIT license. See the [LICENSE file](./LICENSE) for more info.
0 commit comments