Development enviroments orther than MPLAB
 

It took me all of five minutes to decide that there is no way I would use the MPLAB IDE to program the robot this year. Every part of it made me angry (especialy the ultra-long load times on my crappy old notebook), so I started using gVim + cygwin + make.
What are other people using to program it?

Re: Development enviroments orther than MPLAB
 

wine+mcc18+makefile+ifi_picloader

works way better than MPLAB since I can use vim or kate or whatever else I want, and the cli bootloader feels less clumsy than ifi's loader.

Re: Development enviroments orther than MPLAB
 

i would do something else, but im too lazy

Re: Development enviroments orther than MPLAB
 

horray for vim, the true "programmer's text editor"

Re: Development enviroments orther than MPLAB
 

*cheers* Yup! Nothing like it.
(you know youve been coding with vim too long when you start hitting j and k when your on the web... Thank heaven FireFox knows to start searching when you hit /)

Re: Development enviroments orther than MPLAB
 

no, you know you've been using vim to long when you start typing :w for no reason at all into your word documents at school.... ;)

Re: Development enviroments orther than MPLAB
 

Actually, I find vim scary. ;)

My team used MPLAB + Windows since I was the only one with Linux on their machine. Plus, I didn't find out until later that others got the IFI_Loader to work with WINE with no major problems.

Re: Development enviroments orther than MPLAB
 

afaik, the ifi loader still doesn't work through wine. A new one was coded from scratch to do the job.

Re: Development enviroments orther than MPLAB
 

Same thing. ;)

Re: Development enviroments orther than MPLAB
 

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;

Re: Development enviroments orther than MPLAB
 

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.

Re: Development enviroments orther than MPLAB
 

:ahh: 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. :ahh:

Re: Development enviroments orther than MPLAB
 

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.

Re: Development enviroments orther than MPLAB
 

Wow, I didn't realize how many teams actually had code that didn't work at ship. :ahh: 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. :p

Re: Development enviroments orther than MPLAB
 

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.