diff options
Diffstat (limited to 'documentation/3.0/manual.md')
| -rw-r--r-- | documentation/3.0/manual.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/documentation/3.0/manual.md b/documentation/3.0/manual.md index f6fb6ff..3cc5545 100644 --- a/documentation/3.0/manual.md +++ b/documentation/3.0/manual.md @@ -10,7 +10,7 @@ title: User Guide Flow uses sbt as build system. To get started, include a dependency to flow in your project: ~~~scala -libraryDependencies += "ch.jodersky" %% "flow-core" % "3.0.2" +libraryDependencies += "ch.jodersky" %% "flow-core" % "3.0.4" ~~~ Next, you need to include flow's native library that supports communication for serial devices. @@ -28,7 +28,7 @@ It is recommended that you use the first option for testing purposes or end-user In case your kernel/architecture combination is present in the "supported platforms" table in the [downloads section]({{site.url}}/downloads/), add a second dependency to your project: ~~~scala -libraryDependencies += "ch.jodersky" % "flow-native" % "3.0.2" % "runtime" +libraryDependencies += "ch.jodersky" % "flow-native" % "3.0.4" % "runtime" ~~~ This will add a jar to your classpath containing native libraries for various platforms. At run-time, the correct library for the current platform is selected, extracted and loaded. This solution enables running applications seamlessly, as if they were pure JVM applications. @@ -49,7 +49,7 @@ Then, for every end-user application that relies on flow, manually add the nativ --- # Communication Protocol -The following is a general guide on the usage of flow. If you prefer a complete example, check out the code contained in the [flow-samples](https://github.com/jodersky/flow/tree/v3.0.2/flow-samples) directory. +The following is a general guide on the usage of flow. If you prefer a complete example, check out the code contained in the [flow-samples](https://github.com/jodersky/flow/tree/v3.0.4/flow-samples) directory. Flow's API follows that of an actor based system, where each actor is assigned specific functions involved in serial communication. The two main actor types are: @@ -186,7 +186,7 @@ Note that the manager has a deathwatch on every subscribed client. Hence, should Flow provides support for Akka streams and thus can be interfaced with reactive-streams. Support is implemented in a separate module, which needs to be added as a library dependency: ~~~scala -libraryDependencies += "ch.jodersky" %% "flow-stream" % "3.0.2" +libraryDependencies += "ch.jodersky" %% "flow-stream" % "3.0.4" ~~~ The main entry point for serial streaming is `ch.jodersky.flow.stream.Serial`. It's API is also well documented and should serve as the starting point when searching documentation on serial streaming. |