I definitely like the idea of rviz-like functionality in a browser, where it is accessible from essentially any device. One of the big use-cases though is Point Cloud data, which is already very high bandwidth, even in binary format. If we sent that data in JSON format, it would expand about 4 times in size. If there were support for binary data sent via websockets, rosbridge, etc, I would be thinking more seriously about it. Dave On Mon, Apr 23, 2012 at 11:55 AM, Jeff Rousseau < jrousseau@aptima.com> wrote: > Dariush, > > I think it really depends on what you want in your "android rviz" > > We (at Aptima) have built some nice HTML5 UIs that wrap nicely into > Android and iOS devices for controlling multiple robots. So if you're > looking for a replacement for something like the old nav_view > functionality, we've found that HTML5 gives you some nice > portability/code-reuse benefits. > > http://www.youtube.com/watch?v=JcATNhoJ3gg > > I think of rviz as a "visual debugger" as well as an extremely basic > navigation interface. We cared more about building a UI for controlling > the nav stack (queing waypoints, etc) so our use case might not be exactly > the same. > > Jeff > > > -----Original Message----- > > From: ros-users-bounces@code.ros.org [mailto:ros-users- > > bounces@code.ros.org] On Behalf Of Dariush Forouher > > Sent: Monday, April 23, 2012 9:50 AM > > To: User discussions > > Subject: Re: [ros-users] RFC: rviz on Android > > > > Interesting, thanks for the many answers. > > > > I agree, building ROS apps for the browser is generally preferable for > > portability reasons. I don't know whether a fullfledged rviz is doable > inside > > the browser, however. wviz looks nice, though. > > > > @Dave: Working together on this sounds like a great idea. I was thinking > of > > handing this out as a student project as well. Once I've found someone > Ill > > contact you to see where we can contribute. > > > > cheers > > Dariush > > > > Am 21.04.2012 04:06, schrieb Michael Carroll: > > > I would certainly be interested in helping out. I did a somewhat-iOS > > > capable ROS bridge based on a 3rd party app for the iPhone and iPad, > > > but I don't know that it's really a suitable long term solution. > > > > > > I, too, was considering something along the lines of rosbridge for a > > > more fully-featured cross platform "app" (which could support any web > > > enabled device). > > > > > > I think that if a "mobile ROS" is done, it should be with the goal to > > > be as cross platform as possible. I understand this becomes > > > cumbersome when it comes to Rviz, but for most of the other > > > interesting day-to-day information, widgets and text should cover it. > > > > > > ~mc > > > > > > On Fri, Apr 20, 2012 at 13:00, Dave Hershberger > > > > wrote: > > > > > > er, I meant he's starting in May and I hope that in *June* we'll be > > > ready to farm out the Display subclass work. > > > > > > Dave > > > > > > > > > On Fri, Apr 20, 2012 at 10:59 AM, Dave Hershberger > > > > wrote: > > > > > > That's great, thanks. The project is supposed to start > sometime > > > in May when my intern arrives. Hopefully sometime in April > > > we'll be ready to start writing Display classes, which is the > > > place that looks easiest (to me) to farm out different pieces > of > > > work. All Displays are subclasses of the Display class and > they > > > all use the same APIs do their various work, and there are > about > > > 20 of them. > > > > > > It will also be great to have people testing and reporting bugs > > > in different use cases we might not see in-house. > > > > > > Dave > > > > -- > > Institut für Technische Informatik / Universität zu Lübeck > http://www.iti.uni- > > luebeck.de/mitarbeiter/dariush-forouher-m-sc.html > > > The information transmitted is intended only for the person or entity to > which it is addressed and may contain confidential and/or privileged > material. Any review, retransmission, dissemination or other use of, or > taking of any action in reliance upon this information by persons or > entities other than the intended recipient is prohibited. If you received > this in error, please contact the sender and delete the material from any > computer. > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users >