Author Topic: Developer tools (coders only)  (Read 1348 times)

0 Members and 1 Guest are viewing this topic.

Offline RandomTiger

  • Senior Member
  • 211
Developer tools (coders only)
How about we share some info about tools. Could lead to more progress if some people are missing out.

Windiff:

Comes with VC6 I think. Great tool that visually shows you code changes in colour. It can get a bit confused if there are a lot of changes but its the best for finding small changes that you've lost.
It can be used to compare two files or two entire directories.

I use it when I get in  a mess about what I have changed. I dig up an old version of the code and do a directory compare. Its already helped me in this project loads of times.

Cmdedit (http://www.geocities.com/jadoxa/cmdedit/):

Dos is very powerful and can save you a lot of time if you use it well. Here is a tool to make dos really work for you. It allows you to recall previous commands you have issued and if you press tab it will complete file and directory names for you. Great for getting around your harddisc fast.

I used this to get around fast in my freespace data dir when all pcx files had been converted into TGA's and the number of files in the dir was so high explorer couldnt handle it.

Great for using with cvs as well.

----
Comeon coders, share your knowledge!

 

Offline Inquisitor

Developer tools (coders only)
There are also some pretty extensive file comparison tools in CVS, WinCVS (see other post) brings them way into ease of use.

Lessee, apart from Visual Studio itself, I use WinCVS, something called tree dif to manage builds of things that have lots of script files so I can update stuff (alot like windiff, I just got into the habit of using it), and i think that covers my daily life.
No signature.

 

Offline penguin

  • Eudyptes codus
  • 28
  • Still alive.
Developer tools (coders only)
Bah.  Everything you've both mentioned is built into most Linux distros.  ;)

It could use a decent debugger, though.
your source code slave

 

Offline EdrickV

  • Valued
  • 29
    • http://members.aol.com/HunterComputers
Developer tools (coders only)
Cygwin (for those of us without VC6) also features a command history, filename completion, and a command line diff. It also can use gdb, but I'm not sure how good gdb is in debugging.

PS DOSKey can do command history for DOS but doesn't have filename completion. On the other hand, on Win98 or better Windows Explorer (and thus many other Windows components, like the run box) features AutoComplete, which is filename completion by another name.
Ground - "Let me help you out, you're clear to taxi any way you can, to any runway you see."

Mesh Gallery/Downloads:
http://members.aol.com/ArisKalzar/Gallery.html
Turreting 101:
http://members.aol.com/EdrickV/FS2/Turreting.html

http://members.aol.com/HunterComputers