Add visualization plugin support

[osrf-migration]

Original report (archived issue) by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

First step is to support a generic Scene plugin that lets user modify the existing scene.

Need to look into ign-common's plugin framework

[osrf-migration]

Original comment by Ian Chen (Bitbucket: Ian Chen, GitHub: iche033).

---

• changed title from "Add plugin support" to "Add visualization plugin support"

[osrf-migration]

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

---

• Edited issue description* set assignee to "carromj (Bitbucket: carromj, GitHub: mjcarroll)"
• set assignee_account_id to "557058:65740f22-cc56-4418-9608-7e17d0ed47b7"

[osrf-migration]

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

---

➤ Nathan Koenig commented:

Add support for visualzation plugins. Use cases include visualization of sensor data, visualization markers, and other custom plugins that may be project specific.

Create a demo plugin that renders something (like a sphere, or points) into a scene. Write a tutorial on how to create a custom plugin.

[osrf-migration]

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

---

➤ Nathan Koenig commented:

This task is operating on the assumption that plugins to ign-rendering is the best approach to achieve sensor data visualization, visualization markers, etc.

There could be another approach that doesn't require plugins. For example, ign-rendering could offer interfaces to render and manage objects. A sensor, in ign-sensors, could then directly call into ign-rendering instead of using a plugin to render sensor data.

So, Michael Carroll and Ian Chen, can you discuss approaches and come up with a good strategy?

[osrf-migration]

Original comment by Nate Koenig (Bitbucket: Nathan Koenig).

---

➤ Nathan Koenig commented:

I removed a due date for this so that you can focus on Ogre2.1 integration work with Ian and Javier.