-
 

visualization_rwt repository

Repository Summary

Checkout URI https://github.com/tork-a/visualization_rwt.git
VCS Type git
VCS Version kinetic-devel
Last Updated 2023-06-01
Dev Status UNMAINTAINED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

README

visualization_rwt Build Status CLA assistant

visualization packages based on RobotWebTools

INSTALL

apt-get install ros-$ROS_DISTRO-visualization-rwt

Source Install

Following is an example with ROS Indigo.

  1. Create a catkin workspace and navigate to its source directory (e.g. ~/catkin_ws/src).

  2. In your Catkin workspace, download source and build with the following commands.

cd ~/catkin_ws
wstool init src
cd src/
wstool set visualization_rwt --git https://github.com/tork-a/visualization_rwt/
wstool update
rosdep install --from-paths src --ignore-src --rosdistro ${ROS_DISTRO} -r -y
cd ~/catkin_ws 
catkin_make                (or any build commands available in ROS, e.g. `catkin build`)
source devel/setup.bash

PROJECTS

CONTRIBUTING

How to become a contributor and submit your own code

Contributor License Agreements

We’d love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.

Please fill out either the individual or corporate Contributor License Agreement (CLA).

  • If you are an individual writing original source code and you’re sure you own the intellectual property, then you’ll need to sign an individual CLA.
  • If you work for a company that wants to allow you to contribute your work, then you’ll need to sign a corporate CLA.

Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we’ll be able to accept your pull requests.

Contributing A Patch

  1. Submit an issue describing your proposed change to the repo in question.
  2. The repo owner will respond to your issue promptly.
  3. If your proposed change is accepted, and you haven’t already done so, sign a Contributor License Agreement (see details above).
  4. Fork the desired repo, develop and test your code changes.
  5. Submit a pull request.

Repository Summary

Checkout URI https://github.com/tork-a/visualization_rwt.git
VCS Type git
VCS Version kinetic-devel
Last Updated 2023-06-01
Dev Status UNMAINTAINED
CI status No Continuous Integration
Released RELEASED
Tags No category tags.
Contributing Help Wanted (0)
Good First Issues (0)
Pull Requests to Review (0)

Packages

README

visualization_rwt Build Status CLA assistant

visualization packages based on RobotWebTools

INSTALL

apt-get install ros-$ROS_DISTRO-visualization-rwt

Source Install

Following is an example with ROS Indigo.

  1. Create a catkin workspace and navigate to its source directory (e.g. ~/catkin_ws/src).

  2. In your Catkin workspace, download source and build with the following commands.

cd ~/catkin_ws
wstool init src
cd src/
wstool set visualization_rwt --git https://github.com/tork-a/visualization_rwt/
wstool update
rosdep install --from-paths src --ignore-src --rosdistro ${ROS_DISTRO} -r -y
cd ~/catkin_ws 
catkin_make                (or any build commands available in ROS, e.g. `catkin build`)
source devel/setup.bash

PROJECTS

CONTRIBUTING

How to become a contributor and submit your own code

Contributor License Agreements

We’d love to accept your patches! Before we can take them, we have to jump a couple of legal hurdles.

Please fill out either the individual or corporate Contributor License Agreement (CLA).

  • If you are an individual writing original source code and you’re sure you own the intellectual property, then you’ll need to sign an individual CLA.
  • If you work for a company that wants to allow you to contribute your work, then you’ll need to sign a corporate CLA.

Follow either of the two links above to access the appropriate CLA and instructions for how to sign and return it. Once we receive it, we’ll be able to accept your pull requests.

Contributing A Patch

  1. Submit an issue describing your proposed change to the repo in question.
  2. The repo owner will respond to your issue promptly.
  3. If your proposed change is accepted, and you haven’t already done so, sign a Contributor License Agreement (see details above).
  4. Fork the desired repo, develop and test your code changes.
  5. Submit a pull request.