Brandon Alexander

Good questions. My goal for the rest of v0.1.x is to improve publishing and subscribing robustness. This includes: 1. Unregistering publishers and subscribers. Right now, after closing the program, you...

@maxired - I've been considering what we discussed. I'm thinking about a slight tweak to the API. Basically, instead of ros.node() and ros.topics(), you can initialize a topic directly. The...

I updated the API to get rid of node() and topics(). You can now initialize a topic directly with var topic = new ros.topic(); The example/how_to.js has been updated with...

With the updates in Issue #28, I made registerSubscriber and registerPublisher public functions. You can now call these directly instead of passing in a mode. Or, just call publish() or...

Look at [dnode](https://github.com/substack/dnode) and [now.js](http://nowjs.com).

More work needs to go into defining the services usage, but service should resemble the topic API some. The new ros.js has some [example code](https://github.com/rosjs/rosjs/blob/master/example/example.js) using services, but it's not...

I originally wrote this issue for v0.0.1. With v0.1.0, we now can access individual topics easier. It may make more sense to shut these down individually or the node as...

I have done all of my robot testing using a TurtleBot, but I haven't namespaced my topics yet (see Issue #5). First, I have been using the cmd_vel topic and...

I reproduced your issue locally tonight. I ran `rostopic echo /topic1/command_velocity` and nothing printed out. I tried it with geometry_msgs and std_msgs and same issue. Then I wrapped `topic.publish` in...

Nodes should launch okay since they do with rosrun. However, need to make sure param setting and remapping work too (see Issue #5).