Move PR's and improvements to Robot Code 2015

[mananshah99]

We really shouldn't be working on improving this code (aside from potentially CalGames) but should move working code and set up a base for 2015. IMO, this could save us a LOT of time in training season.

[mananshah99]

So for example, @Arcterus' revised drive straight code should go in RobotCode-2015, so we have a stable version here and a "dev" version for 2015 in that repo. We should also generate javadocs there, but after more code is pushed.

[Andrew-Tierno]

@mananshah99 My only problem with that is that the framework for RobotCode-2015 isn't set up yet (i.e. we don't know which parts are going to be used for the drivetrain). Therefore, any files we wrote would be laden with errors.

[Arcterus]

@Andrew-Tierno I think it's still better to have some sort of a base to work with. By taking advantage of the development this year, we will drastically shrink the amount of work we actually need to do next year. Plus, we can always revise the code when we learn what parts are going to be used in the robot.

[Andrew-Tierno]

@Arcterus Currently setting up some framework for RobotCode2015 with a few assumptions :P

On Sun, May 25, 2014 at 11:38 AM, Arcterus notifications@github.com wrote:

@Andrew-Tierno https://github.com/Andrew-Tierno I think it's still better to have some sort of a base to work with. By taking advantage of the development this year, we will drastically shrink the amount of work we actually need to do next year. Plus, we can always revise the code when we learn what parts are going to be used in the robot.

— Reply to this email directly or view it on GitHubhttps://github.com/HarkerRobo/RobotCode-2014/issues/2#issuecomment-44142097 .

Cheers, Andrew Tierno

[Arcterus]

@Andrew-Tierno Whoops, I didn't notice that… :smile:

[mananshah99]

@Arcterus feel free to push your drive straight code to RobotCode-2015 when it's set up. We can test from there.

[Arcterus]

@mananshah99 sounds good.