Development enviroments orther than MPLAB

[CrashZero]

I used the MPLAB IDE with windows cuz I was way to lazy to use anything else, I mean most of my code is just the default; My team was kinda picky about having it working b4 we shipped;

[Astronouth7303]

The bot barely worked when we shipped. And the code was screwed up so badly that the controller gave us a red-green. (RGOD!) Or an infinate loop.

[CrashZero]

Thats nothing all our robot did when we shipped it was spin in a circle. cuz the stupid build team put one of the fricking moters in backwards. I think that when we get there i can download a code that works but we will literally be testing it on our bot for the first time then. If anything goes wrong i am sure that all you programers out there know that it is me who will be blamed for screwing it up, even though if the builders whould have put it in right it would not have been a problem.

[fred]

Our situation is sort of weird. I definitely like where we went with the robot and if it turns out correctly, look out for Miss Daisy. We didn't make too many modications to the code, not enough to warrant switching from Windows or anything. The problem is that our code hadn't been tested with the robot at all before we shipped. But we have some good programmers and I think that we will definitely turn out okay. See ya at Chesapeake.

[Ryan M.]

Wow, I didn't realize how many teams actually had code that didn't work at ship. This is my first year competing.

Surprisingly, even though we are rookies, we still got all our OI code tested and our main automous mode.

[Venkatesh]

Vim? Fwah.

I used vi (not vim) and make. Not GNU make either. Microsoft NMAKE.

If I had access to a Mac, I would use Subethaedit, but I don't. If somebody were to port Subethaedit to Windows, I would regard them in the ranks of Cerf.

[Astronouth7303]

I voted for MPLAB, but I just did MSC++ .NET, and I'm really happy. Now that's an IDE.

[Ryan M.]

Originally Posted by Venkatesh

Vim? Fwah.

I used vi (not vim) and make. Not GNU make either. Microsoft NMAKE.

If I had access to a Mac, I would use Subethaedit, but I don't. If somebody were to port Subethaedit to Windows, I would regard them in the ranks of Cerf.

Microsoft?!?!?

As my old signature used to say, "I'm not anti-Microsoft, I'm just pro-quality."

Yeah, MSC++ .NET is great (surprisingly, a good Microsoft product). The only reason I didn't use it is MPLAB allowed quick access to the compiler, while MSC++ .NET isn't custimizable for that sort of thing. Next year I'm going to find something better for our controls team to use.

[jhnphm]

GVim/Vim + Cygwin + IDE for compilation. Don't have access to a linux computer other than at home for programming, and too lazy to figure out how to use MCC's command line.

[Astronouth7303]

Compared with the general rabble, Microsoft almost caters to developers.

[Kevin Karan]

Its too bad that only 3 voted for linux...Most of my team is affraid of it, including the other programmer, so im stuck using windows at the competitions...

[phrontist]

Originally Posted by Astronouth7303

Compared with the general rabble, Microsoft almost caters to developers.

What the [expletives that would've made Nixon blush deleted]

What do you mean by "the general rabble"?! I sincerely hope you don't mean linux!

Please report to the nearest Microsoft Deprogramming Center:

ESR's Propaganda Post
Slashdot: News for Linux Zealots
The GNU Website: 'Nuff said

[Neal Probert]

I use ActiveState's Komodo a lot, otherwise Eclipse is worth a good look. Both are available under Linux or Windows. KDevelop under Linux is also worth a good look.

A lot of bots didn't work right off the bat at the early competitions, because people didn't follow the latest IFI/FIRST news about software updates and weird initial states upon RC startup.

As for NMAKE, it's piece of $@#$@#$@#$@#. Gnu MAKE is available for Windows as well. Though I think it's high time that somebody come out with a better MAKE one of these days.

[Mike Soukup]

We decided early on to scrap the MPLAB IDE and use cygwin & make instead. After a month or so I finally convinced the other mentors to use VIM. Now we're actually teaching the students how to use it.

An invaluable development tool I found a few years ago is cscope (http://cscope.sourceforge.net/). It parses all the source & header files in your build and creates a 'database' that allows you to quickly jump to a function definition, find all calls of a function, find all references to a symbol, etc. Even better you can integrate it with VIM so all you have to do is put your curser on a function call, hit <ctl>] and you're now at the function definition; hit g<ctl>\ and you have a list of all occurrances of the symbol under the cursor. I'd probably be half as productive at work if I didn't have VIM & cscope. Give it a try. If you need help send me a PM or start a new thread.

[Astronouth7303]

Cool! I like that. MS has been doing it for awhile, but it's nice to now someone else is.