made call to compute_cartesian_path more pythonic; added links to mov…

[jwhendy]

…eit_commander API

I tweaked the tutorial intro, as MoveGroupCommander is used just a much as RobotCommander, so it seemed fair to highlight both, and I added a link to the API a well, which I found really helpful when getting my hands dirty (just nice to see all the calls one has available).

While I'm new, from what I've seen in python blogs various talks on python, using named arguments seemed more elegant/pythonic than un-named arguments with comments after them, especially since the variables were named perfectly already.

[davetcoleman]

i love this!

[davetcoleman]

i just retriggered the build

[davetcoleman]

You have a slight syntax error:

Warning, treated as error:
/home/travis/build/ros-planning/moveit_tutorials/doc/ros_visualization/visualization_tutorial.rst:100: WARNING: Bullet list ends without a blank line; unexpected unindent.

[jwhendy]

I think I've figured this all out...

• Update perception_configuration.rst #101 was causing build errors based on 404 errors for the links used
• after fixing that, it failed due to using the same hyperlink text for both pr2_moveit_config links so I fixed that as well
• I thought the issue was due to my inserted image in Tutorial fixes #91 which added an extra blank line after the bullet list, but then had a real head scratcher when I couldn't find that image anymore! Turns out that visualization tutorial is now kinetic compatible #92 removed it
• I also found that visualization tutorial is now kinetic compatible #92 replaced the entire bullet list in "Step 3: Interact with the PR2", and added two spaces before an asterisk, causing the error you see above. That said, the comment that was merged failed due to the non-existent .png file issue you referred to in fixed collision contact tutorial failing build due to image location… #94 so it couldn't continue to find this issue...

So! If you take #109, I think this will then pass as well.