Skip to content

Conversation

@jackhymowitz
Copy link
Collaborator

No description provided.

jackhymowitz and others added 7 commits December 27, 2016 13:15
# 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
Copy link
Contributor

@rafibaum rafibaum left a 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.

@jackhymowitz
Copy link
Collaborator Author

jackhymowitz commented Jan 11, 2017 via email

@rafibaum
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants