Michael didn't mention it, but there is an android version that currently doesn't support custom layouts, you guys should email hexler: http://hexler.net and tell him to get on that so you can use this stuff on android too! Additionally, this isn't just for touchosc (the iOS and android app that sends/recieves osc messages), but anything that sends and receives osc messages like sound equipment, other mobile osc apps, and sound mixing software via the more basic rososc_bridge. -- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ William Woodall Graduate Software Engineering Auburn University w@auburn.edu wjwwood@gmail.com williamjwoodall.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ On Wed, Dec 21, 2011 at 1:27 PM, Michael Carroll wrote: > There isn't really a greater context at the moment. It basically started > as a side project when I found the TouchOSC app in the App Store one day. > > William and I started driving the autonomous lawnmower with the iPhone > about a year ago, and it sort of developed from that. I started with just > basic communication with TouchOSC (controls, tabpage switching, > accelerometer, and vibrate motor) at first. Then I moved on to reverse > engineering the layout files and the layout transfer system (all available > in pytouchosc). > > I then figured out that it would be more useful to have a more modular > system that allowed for tabpages to be added like plugins, so that you as a > user could create a layout from say Teleop, Diagnostics, and AppManager > (still in development). That's the direction that it's headed right now, > but I wanted to get it out there and shake some bugs out and get some new > ideas for the future. > > Basically, I got tired of playing Angry Birds, and thought that we should > do more with iPads. > > Glad you like it, > > ~mc > > On Wed, Dec 21, 2011 at 14:19, Trevor Jay wrote: > >> I graduated from UA, so if I have a bias I'm sure it swings the other >> way and I think this is absolutely fantastic! Having a helper node for >> loading the layouts is just a beautiful extra touch. >> >> Is there a greater context for this or are you just interested in RAD >> development for ROS? >> >> _Trevor >> >> On Wed, Dec 21, 2011 at 2:13 PM, William Woodall >> wrote: >> > +1 Awesome. >> > >> > I might be biased, but it is still awesome! >> > >> > Thanks for this, >> > >> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> > William Woodall >> > Graduate Software Engineering >> > Auburn University >> > w@auburn.edu >> > wjwwood@gmail.com >> > williamjwoodall.com >> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ >> > >> > >> > >> > On Wed, Dec 21, 2011 at 12:56 PM, Michael Carroll >> > wrote: >> >> >> >> Greetings ROS Users, >> >> >> >> I am please to announce a new stack that I've been working on: ROSOSC. >> >> Code and documentation for my "beta" release are available >> immediately on >> >> the ROS.org wiki: http://www.ros.org/wiki/rososc >> >> >> >> ROSOSC is a set of utilities and nodes for interacting with Open Sound >> >> Control hardware and software devices. >> >> >> >> One of the main features is the ability to interact with TouchOSC >> (created >> >> by hexler: http://hexler.net), the iOS application, to create dynamic, >> >> touch-interactive, control surfaces that can be used with ROS. These >> >> control surfaces can be composed of several different types of >> controls, >> >> such as push buttons, toggle buttons, faders, rotary knobs, labels and >> LEDs. >> >> Most of the controls support two-way communication with ROS, which >> allows >> >> users to change color, position, size, and visibility of all of the >> controls >> >> on the page via ROS topics. >> >> >> >> There are two main ways of interacting with TouchOSC with ROS: >> >> >> >> Using a "default handler" - Simply create a layout file in the freely >> >> available TouchOSC editor, and then launch the ROS touchosc_bridge >> node. >> >> All of the controls on the page will show up as topics that can be >> >> published to/subscribed to using ROS. >> >> Using a "tabpage handler" - Users can also create a python module that >> can >> >> directly interface with OSC clients. There are many features >> available to >> >> developers, including multiple client support, client join/quit >> callbacks, >> >> and client tabpage switching callbacks. More can be found out on the >> wiki >> >> and API documents. >> >> >> >> API Docs are available on the ROS wiki >> >> Two tabpage handlers are included out of the box: >> >> >> >> Diagnostics_handler - a tabpage for viewing diagnostics and aggregate >> >> diagnostics data >> >> teleop_handler - a tabpage for broadcasting command velocity messages >> to >> >> holonomic and differential drive robots. >> >> >> >> I hope that you find this useful in your robotics projects, and I'm >> >> excited to see some of the future uses of the TouchOSC and Open Sound >> >> Control interfaces. >> >> >> >> To get an idea of the basic features, I have made some YouTube videos: >> >> >> >> Loading Layouts using ROSOSC: http://youtu.be/ZHHp1WSbQQU >> >> Using the Diagnostics Tabpage: http://youtu.be/xgOYBcAzLBM >> >> Using the Teleop Tabpage: http://youtu.be/iPB_6XdgOwA >> >> >> >> Thanks, >> >> >> >> ~mc >> >> >> >> (Ken, I have already added this to the indexer) >> >> -- >> >> Michael Carroll >> >> http://mjcarroll.net >> >> Electrical Engineering Graduate Student >> >> Auburn University >> >> >> > >> > >> > _______________________________________________ >> > ros-users mailing list >> > ros-users@code.ros.org >> > https://code.ros.org/mailman/listinfo/ros-users >> > >> _______________________________________________ >> ros-users mailing list >> ros-users@code.ros.org >> https://code.ros.org/mailman/listinfo/ros-users >> > > > _______________________________________________ > ros-users mailing list > ros-users@code.ros.org > https://code.ros.org/mailman/listinfo/ros-users > >