-
Notifications
You must be signed in to change notification settings - Fork 0
New jack branch #39
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.
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
base: master
Are you sure you want to change the base?
New jack branch #39
Conversation
# Conflicts: # src/org/montclairrobotics/sprocket/control/ArcadeDriveInput.java # src/org/montclairrobotics/sprocket/drive/DriveModule.java # src/org/montclairrobotics/sprocket/drive/DriveTrainBuilder.java # src/org/montclairrobotics/sprocket/geometry/Polar.java # src/org/montclairrobotics/sprocket/geometry/Vector.java # src/org/montclairrobotics/sprocket/geometry/XY.java # src/org/montclairrobotics/sprocket/httpserver/Http.java
rafibaum
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What's your rationale for getting rid of mappers and how do you plan on replacing their functionality? Also we do have to do code style now so once you're done I'm going to do a style check.
|
1. Because there is a general solution which I think I have, and the
machinery to do it another way is as complicated as the rest of the
drivetrain. Maybe they have to stay, but I am at least going to try and
improve it.
2. I would agree to a code style, but I want to have input on writing it.
…On Wednesday, January 11, 2017, Rafi Baum ***@***.***> wrote:
***@***.**** requested changes on this pull request.
What's your rationale for getting rid of mappers and how do you plan on
replacing their functionality? Also we do have to do code style now so once
you're done I'm going to do a style check.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#39 (review)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/APpUfWZm-GBTFOBqoG5892D0kL3g2b3dks5rRVtBgaJpZM4LhGzc>
.
|
|
If you're able to write the generic drive mapper and it works as well as any specific solution would then you're welcome to remove that functionality. Otherwise keep mappers in since we need to allow developers to express how they want to process joystick inputs into motor powers since that is a process that can differ wildly depending on a variety of factors. |
No description provided.