-
Notifications
You must be signed in to change notification settings - Fork 11
Vidal Meeting Notes
Team did not add beta features as I requested below.
There is no need to use pull requests since you are all on the same repo. It is easier to just "merge into master" from Android Studio.
For next meeting:
- Start reading about Android testing
- Add features to Issues, associate with Beta milestone.
- demo
Andrew, Zipporah did not attend.
Final demo done: android app moves simulated robot and shows camera input.
One remaining person: git push.
Demo: Android app talks to ROS simulator on laptop, can show camera from laptop and laser sensor map.
Good progress, on track. Keep working.
Maybe, for demo have a nicer GUI.
For December demo:
- An app running a tablet.
- Joystick controls robot.
- Get some input from robot to app: photos? GPS location? laser map?
For next meeting:
- Everyone commit and push to github.
- Start coding towards December demo, start using issues.
- From now on, demo at meetings.
https://cse.sc.edu/~jokane/agitr/
Rosjava docs: http://docs.rosjava.googlecode.com/hg/android_core/html/javadoc/org/ros/android/view/package-summary.html
Have a repo that can build an Android app that talks to to ros simulator and implements a Joystick view.
For next meeting:
- Source control milestone: Add android .gitignore, and remove (git rm) files from repo that should not be there. Everyone can clone/build/commit/push.
- functional requirements:
Have rough designs.
Install ROS java libraries for Android.
For next meeting:
- Everyone do Android ros tutorial http://wiki.ros.org/ApplicationsPlatform/Clients/Android/Tutorials/Getting%20Started
- Build Android app that talks to ROS
- Detailed design: do wireframes
Met with client.
Android app. Using Android ROS library
Robots has camera and a laser scanner and GPS.
For next meeting:
- Learn android. main site, online class videos
- Rough Design, "easy" navigation, provide all required views (camera, laser).