Update README.md

This patch updates:

- Add the release info for v0.10.3.
- Remove the deprecated actionlib information.

Fix #None

Author: Minggang Wang

README.md

@@ -11,7 +11,7 @@ If you want to select a stable release of ROS 2.0 as your platform, please check
 
 |                                             ROS 2.0 release                                             |                                                             NPM version                                                             |
 | :-----------------------------------------------------------------------------------------------------: | :---------------------------------------------------------------------------------------------------------------------------------: |
-| Eloquent Elusor Patch Release [1](https://github.com/ros2/ros2/releases/tag/release-eloquent-20200124)  | [0.12.0](https://github.com/RobotWebTools/rclnodejs/tree/0.12.0) ([doc](http://robotwebtools.org/rclnodejs/docs/0.12.0/index.html)) |
+| Eloquent Elusor Patch Release [1](https://github.com/ros2/ros2/releases/tag/release-eloquent-20200124)  | [0.13.0](https://github.com/RobotWebTools/rclnodejs/tree/0.13.0) ([doc](http://robotwebtools.org/rclnodejs/docs/0.13.0/index.html)) |
 |         [Eloquent Elusor](https://github.com/ros2/ros2/releases/tag/release-eloquent-20191122)          |                              [0.11.1](https://github.com/RobotWebTools/rclnodejs/releases/tag/0.11.1)                               |
 | Dashing Diademata Patch Release [4](https://github.com/ros2/ros2/releases/tag/release-dashing-20191018) |                              [0.10.3](https://github.com/RobotWebTools/rclnodejs/releases/tag/0.10.3)                               |
 | Dashing Diademata Patch Release [3](https://github.com/ros2/ros2/releases/tag/release-dashing-20190910) |                              [0.10.2](https://github.com/RobotWebTools/rclnodejs/releases/tag/0.10.2)                               |
@@ -176,10 +176,6 @@ The benefits of using TypeScript become evident when working with more complex m
 
 Smart TypeScript tools such as Visual Studio Code and the CodeMix plugin for Eclipse will help you learn the rclnodejs api and identify issues while coding rather than at runtime.
 
-## Experimental - Deprecated
-
-- [actionlib](https://github.com/RobotWebTools/rclnodejs/blob/develop/tutorials/actionlib.md) - as the [rcl](https://github.com/ros2/rcl) library has implemented the action related functions, we are going to drop this one and we don't guarantee the current actionlib can work with [rclcpp](https://github.com/ros2/rclcpp).
-
 ## Troubleshooting
 
 ### Maximum call stack size exceeded error when running in Jest

tutorials/actionlib.md

@@ -1,10 +1,13 @@
-# Introduction
+# Introduction - Deprecated, please reference examples under /example for the usage based on the latest implementation.
+
 Actionlib tutorial based on `rclnodejs`.
 
 ## Actionlib background
+
 To continue the tutorial, you should have some basic understanding of the `action` term in ROS. If you're not familar with it, please refer to the [description](http://wiki.ros.org/actionlib/DetailedDescription).
 
 ## Precondition
+
 You should prepare an action text file. The content is like this:
 
 ```
@@ -23,41 +26,50 @@ sensor_msgs/Image image
 Fortunately, there is a `dodishes.action` file that is already available in the `test/ros1_actions` directory.
 
 ## Basic steps of processing action files for rclnodejs
+
 For `rclnodejs`, the basic steps of process an action file is separated into 2 steps:
-* Generate several msg files and the js message package from the action file.
-* Build the shared library from the msg files that will be used in running actionlib-feature-related code.
+
+- Generate several msg files and the js message package from the action file.
+- Build the shared library from the msg files that will be used in running actionlib-feature-related code.
 
 ### Generate msg files from the action file
+
 The `generated` directory contains the generated js message package for `rclnodejs`. If you have run `npm install`, then it should
 exist after `npm install` was done. However, since your `AMENT_PREFIX_PATH` may not include the directory path of the action file, the `ros1_actions` package may not be generated. So you need remove the whole `generated` directory and regenerate them.
+
 ```
 $ rm -fr generated
 $ export AMENT_PREFIX_PATH=$AMENT_PREFIX_PATH:$(pwd)/test/ros1_actions
 $ node scripts/generate_messages.js
 ```
 
 ### Build the shared library from the msg files
+
 ```
 $ cd test/ros1_actions
 $ colcon build
 ```
 
 ## Run the action example
+
 After the build, you can run the action example. The action example contains two parts, one is the [action server](./example/action-server-example.js), another is the [action client](./example/action-client-example.js). When running the example, you should launch the server first, and then launch the client.
 
-* Launch a terminal session, load ROS2 environment and go to `rclnodejs` directory.
+- Launch a terminal session, load ROS2 environment and go to `rclnodejs` directory.
+
 ```
 $ source test/ros1_actions/install/local_setup.bash
 $ node example/action-server-example.js
 ```
 
-* Launch another terminal session, load ROS2 environment and go to `rclnodejs` directory.
+- Launch another terminal session, load ROS2 environment and go to `rclnodejs` directory.
+
 ```
 $ source test/ros1_actions/install/local_setup.bash
 $ node example/action-client-example.js
 ```
 
 Here is the action client output:
+
 ```
 The goal was sent, the goal id is 7c28f24a-5ce8-4b13-a2aa-7aa62128fd03
 70% of the task has been completed.
@@ -67,13 +79,16 @@ The goal, whose id is 7c28f24a-5ce8-4b13-a2aa-7aa62128fd03, has been executed su
 ```
 
 And here is the action server output:
+
 ```
 A goal, whose id is 7c28f24a-5ce8-4b13-a2aa-7aa62128fd03, was received.
 ```
 
 ## Explaination of the action example:
+
 1. Action server
-For the action server, the skeleton code is like this:
+   For the action server, the skeleton code is like this:
+
 ```
 rclnodejs.init().then(() => {
   const as = new rclnodejs.ActionLib.ActionServer({
@@ -103,13 +118,15 @@ rclnodejs.init().then(() => {
 First, you should new an `ActionServer` with the `type` and the `actionServer`. The `type` is the action package name and the `actionServer` is the name of the action server, which should be the same as the action client request to in future.
 
 The `ActionServer` can emit 2 type events: `goal` and `cancel` events.
-* `goal` event: triggered when an action client sends an goal to the action server by calling its `sendGoal()` method. In the handler of the this event, you can accept the goal by calling `goal.setAccepted()`. During executing the goal, you can send a feedback to the action client by calling `goal.publishFeedback()`. Once the goal is completed, you should set the goal status by calling `goal.setSucceeded()`, which will trigger the `result` event for the action client.
-* `cancel` event: triggered when an action client cancels the the goal after a goal was sent to the action server but not completed yet.
+
+- `goal` event: triggered when an action client sends an goal to the action server by calling its `sendGoal()` method. In the handler of the this event, you can accept the goal by calling `goal.setAccepted()`. During executing the goal, you can send a feedback to the action client by calling `goal.publishFeedback()`. Once the goal is completed, you should set the goal status by calling `goal.setSucceeded()`, which will trigger the `result` event for the action client.
+- `cancel` event: triggered when an action client cancels the the goal after a goal was sent to the action server but not completed yet.
 
 The `start()` method must be called to start the action server.
 
 2. Action client
-For the action client, the skeleton code is like this:
+   For the action client, the skeleton code is like this:
+
 ```
 rclnodejs.init().then(() => {
   const GoalStatus = rclnodejs.require('actionlib_msgs/msg/GoalStatus');
@@ -144,8 +161,9 @@ rclnodejs.init().then(() => {
 ```
 
 To construct an action client, use `new rclnodejs.ActionClientInterface()`. The action client can emit 3 type events:
-* `status` event: tirggered when the action server sends messages to the action client during the goal is executing.
-* `feedback` event: triggered after the action server called `publishFeedback`.
-* `result` event: triggered after the action server called `setSucceeded`.
+
+- `status` event: tirggered when the action server sends messages to the action client during the goal is executing.
+- `feedback` event: triggered after the action server called `publishFeedback`.
+- `result` event: triggered after the action server called `setSucceeded`.
 
 **Notice**, the action state transitions must obey some specific order, for more details please refer to [this articile](http://wiki.ros.org/actionlib/DetailedDescription)