What programming tool does your team use?
 

Just curious...

Re: What programming tool does your team use?
 

I checked WPILib and Other because our robot was programmed using WPILib in Eclipse instead of in MPLab last year. Everything works the same code and compile wise, just with a different IDE.

Re: What programming tool does your team use?
 

So does that mean Kevin Watson's code is kind of like WPILib? They both are used in MPLab, but both are different default code bases? Or am I wrong? (my team only uses Kevin Watson's code with MPLab)

Re: What programming tool does your team use?
 

WPIlib is a framework written by Brad Miller at WPI to greatly simplify robot programming. Here's some more info:

http://users.wpi.edu/~bamiller/WPILib/

Team 228 wrote our robot code last year in WPIlib, so we can work with it in MPLAB and EasyC PRO. And since WPIlib takes care of so much 'back-end stuff' for you, our team was able to concentrate on more important programming tasks, like our drive-by autonomous mode. ;)

Re: What programming tool does your team use?
 

In that case, I might want to consider the ability for my emulator to work with WPILib after making it work with Kevin Watson's MPLab code if it is popular enough...

Re: What programming tool does your team use?
 

This was my first year as a programmer and we used the EasyC program. It was really easy to learn and a great teaching tool for anyone who wants to learn programming.

Re: What programming tool does your team use?
 

code::blocks

Re: What programming tool does your team use?
 

Does anyone know if the source to WPILib is available? We use MPLab now because we can't figure out how to teach device driver development using WPILib or EasyC. To us the beauty of KW's software is you can pretty much just use it if you need a quick solution but because you have the source you can also learn how the microcontroller works and develop your own device driver and interrupt code. The FRC robotics program is usually the first opportunity our software developers have to really understand something about embedded development and understanding something about how to read a data sheet and configure the mc registers. This gives them the confidence to develop additional functionality on the FRC controller as well as use other co-processors such as the nice Atmel microcontrollers.

Re: What programming tool does your team use?
 

WPIlib source isn't available.

Re: What programming tool does your team use?
 

Are you serious? How? I used that as my primary programming tool before I got Visual C++ :)

Re: What programming tool does your team use?
 

http://www.chiefdelphi.com/forums/sh...37;3A%3Ablocks

lol there you go..

Re: What programming tool does your team use?
 

We've used MPLab in the past, but I'm thinking we'll give WPILib a good look this year. It seems like an incredibly simple and powerful tool.

Re: What programming tool does your team use?
 

Cool, thanks. I'll have to check that out...

Re: What programming tool does your team use?
 

I checked Other because we run the compiler on Linux (using wine) and use Makefiles and vim (a text editor) instead of MPLAB.

Re: What programming tool does your team use?
 

Eclipse all the way!
To be honest, I'm surprised at the number of people who are still using the MPLAB IDE, given the number of "real-world" options like Eclipse. I guess it's primarily because MPLAB can be installed by default from the CD.

Re: What programming tool does your team use?
 

I definitely think EasyC is great for small teams like us, 1341. I don't really think that MPLAB gives other teams so huge of an advantage. The same goals can be accomplished in all of these programming tools.