CodeWarrior uses two major kinds of files: program or source files contain Java program code, while project files contain additional information CodeWarrior needs to run the program. Each program has one project file and one or more source files.
By convention, CodeWarrior names of project files end in ``.mcp'' (standing for Metrowerks CodeWarrior Project). Names of Java source files must end in ``.java''.
IMPORTANT: CodeWarrior can get confused (e.g. be unable to find a file) if filenames contain spaces or any punctuation other than underlines, dashes, and periods.
Remember to save your work frequently, not just when you are done for the day. You should also keep a second disk as a backup in case your first disk becomes corrupted or unreadable. You should copy your main floppy disk to the backup regularly.
IMPORTANT: You must keep your files on your own disks. User files are removed from the public machines regularly.
CodeWarrior does take a few simple precautions to protect your work. Before CodeWarrior runs your program, it saves all your files (unless you turned off this option). And when you are done working and leave the CodeWarrior environment by selecting File|Exit, if there are any open files that you haven't saved yet, you will be asked if you want to save them now. Click Save or Don't Save.
A lot of the space used on your disk isn't needed after you've finished a CodeWarrior project. From within CodeWarrior, with the project open, you may select Project|Remove Object Code to delete compiled Java machine code. At the desktop, inside the folder containing your project, you may delete file JavaClasses.zip, which also contains compiled Java machine code, as well as the folder that has the same name as the project file followed by Data, which contains information used by CodeWarrior to run the project. These items (object code, zip file, Data folder) can easily be recreated by running the program again.