Indeed we didn't share ideais about visualizing the robot data, but that is because i needed to get the libs working in the first place.
I will try to respond to Jordi, Mirko Bordignon and Toby Collett.
Jordi: The modifications to the new api are mostly on the support for multiple player clients. It is better explained in the iros 2006 article or even better by trying it out yourself, but here is a sample of how it works.
Suppose we have a stage simulation / world with 3 robots + lasers and we want to view the lasers in a OpenGL window. The xml configuration file would go like this:
<!-- the handlers section is something like a "for each",
i.e. for each client it finds with the following sensors the following plugin will be launched for that sensor.-->
<playerClient host="localhost" port="6665">
<playerClient host="localhost" port="6666">
<playerClient host="localhost" port="6667">
<!-- here we proceed to filter the interfaces we want by name, indexNumber and/or driverName-->
<!-- the plugin(s) that are going to be launched if the interface is found -->
it is just this simple.
Mirko: First of all thanks for your comments on Player Viewer 3D. The provided software is nice as seen in the article, but it really starts to shine by the ease to fast prototype new stuff.
I coded it from the requirements i got when doing my final project and decided to go all the way with the viewer, i.e. providing a complete framework to interact with the world and visualize sensors.
How it copes with Toby Collett Ardev will be discussed next.