As a programmer, you are probably familiar with developing programs in a file-based environment. You write code in source files and compile and link them into executable binary files. As you build the executable code, you must manage files and file dependencies. This is an error-prone process that takes time away from your primary task of programming.
By providing a development environment without files, VisualAge for Java performs the tasks of managing and compiling code. Browsers let you view and edit classes and methods individually. VisualAge for Java compiles Java source code for you when you save it.
From within the IDE, you can import code from the file system into VisualAge for Java. You can also export code to the file system if you want to work outside VisualAge for Java.
Editing is Integrated
The Workbench and browsers reflect an object model rather than a file-based
model. The object hierarchy of program elements (projects, packages, classes, interfaces,
and methods) provides a structure for the code. The Workbench and browsers have a source
pane with full editing capabilities that let you modify and save source code.
Compilation Occurs when You Save Source Code
After you modify the source for a class or method, you save it, and VisualAge for
Java compiles the new code for you. VisualAge for Java keeps track of both the source and
its corresponding bytecodes. However, you never see .java or .class files in the IDE.
VisualAge for Java compiles source code incrementally. That is, it compiles only those parts of the source code that you change (and other code that is directly dependent on it) and therefore significantly reduces the overall compilation time.
Unresolved Problems
Projects and Other Program Elements
Incremental Compilation
Workspace
Repository
Editions and Versioning
Importing Files from the File System
Compiling Code
Saving Changes to Code
Experimenting with Code Fragments
Exporting and Publishing Code