Better chaining API + object for config

[yocontra]

This allows you to do drone.up(0.5).front(1).clockwise(0.2) and also adds some sugar for setting multiple config options at once

drone.config({
  "someoption":"someval",
  "otheroption":"otherval"
});

This makes it easier to have your own drone config file and load it into the drone before you fly it.

Sidenote: is there any way currently to get the config from the drone?

[felixge]

So I'm working on a new API for this whole thing, which is here: https://github.com/felixge/node-ar-drone/commits/new-api . Meanwhile I'm happy with any new patches coming in, in fact I just made you a contributor on the repo. What's your npm user name?

Anyway, returning this is problematic for users of the REPL. So you should change this patch so the REPL still stays usable and doesn't flood the screen.

Sidenote: is there any way currently to get the config from the drone?

No, not yet.

[yocontra]

@felixge -

Is there a way I can tell if the user is on the REPL to change the return values?

Do you have any docs on what you want the new API to look like so I can pitch in?

npm name is fractal

[felixge]

@contra I've added you on npm. I'm not sure about detecting if you're inside a REPL, but there is probably a way : ).

There are no docs for the new API yet, but that's the next thing I'll work on so we can discuss them!