Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

The DroneService doesn't need to know nothing about the input and outputs #3

Open
rocboronat opened this issue May 13, 2015 · 1 comment
Open

The DroneService doesn't need to know nothing about the input and outputs #3

rocboronat opened this issue May 13, 2015 · 1 comment
Labels
enhancement

Comments

@rocboronat
Copy link
Member

Right now, DroneService is working with the input: the phone sensors. The idea is to dettatch that kind of business of the Service itself. It will be getter if the DroneService gets from the input and throws to the output, and nothing else.
@rocboronat rocboronat changed the title The DroneService don't need to know nothing about the input and outputs The DroneService doesn't need to know nothing about the input and outputs Jun 26, 2015
@rocboronat
Copy link
Member Author

First point accomplished: now (6d8fe54) the DroneService don't calculate the desired yaw. Instead of it, there's another class who process it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@rocboronat