Chapter 2. The Eclipse Integrated Development Environment (IDE)

The entire user interface in Figure 2.1, “Eclipse User Interface (default)” is referred to as the Eclipse workbench. It is generally composed of a code Editor, Project Explorer window, and several views. All elements in the Eclipse workbench are configurable, and fully documented in the Workbench User Guide (Help Contents). Refer to Section 2.2, “Useful Hints” for a brief overview on customizing the user interface.

Eclipse features different perspectives. A perspective is a set of views and editors most useful to a specific type of task or project; the Eclipse workbench can contain one or more perspectives. Figure 2.1, “Eclipse User Interface (default)” features the default perspective for C/C++.

Eclipse also divides many functions into several classes, housed inside distinct menu items. For example, the Project menu houses functions relating to compiling/building a project. The Window menu contains options for creating and customizing perspectives, menu items, and other user interface elements. For a brief overview of each main menu item, refer to Reference > C/C++ Menubar in the C/C++ Development User Guide or Reference > Menus and Actions in the Java Development User Guide.

The following sections provide a high-level overview of the different elements visible in the default user interface of the Eclipse integrated development environment (IDE).

2.1. User Interface

The Eclipse workbench provides a user interface for many features and tools essential for every phase of the development process. This section provides an overview of Eclipse's primary user interface.

Figure 2.1. Eclipse User Interface (default)

Figure 2.1, “Eclipse User Interface (default)” displays the default workbench for C/C++ projects. To switch between available perspectives in a workbench, press Ctrl+F8. For some hints on perspective customization, refer to Section 2.2, “Useful Hints”. The figures that follow describe each basic element visible in the default C/C++ perspective.

Figure 2.2. Eclipse Editor

The Editor is used to write and edit source files. Eclipse can autodetect and load an appropriate language editor (e.g. C Editor for files ending in .c) for most types of source files. To configure the settings for the Editor, navigate to Window > Preferences > language (e.g. Java, C++) > Code Style.

Figure 2.3. Project Explorer

The Project Explorer View provides a hierarchial view of all project resources (binaries, source files, etc.). You can open, delete, or otherwise edit any files from this view.

The View Menu button in the Project Explorer View allows you to configure whether projects or working sets are the top-level items in the Project Explorer View. A working set is a group of projects arbitrarily classified as a single set; working sets are handy in organizing related or linked projects.

Figure 2.4. Outline Window

The Outline window provides a condensed view of the code in a source file. It details different variables, functions, libraries, and other structural elements from the selected file in the Editor, all of which are editor-specific.

Figure 2.5. Console View

Some functions and plugged-in programs in Eclipse send their output to the Console view. This view's Display Selected Console button allows you to switch between different consoles.

Figure 2.6. Tasks View

The Tasks view allows you to track specially-marked reminder comments in the code. This view shows the location of each task comment and allows you to sort them in several ways.

Figure 2.7. Sample of Tracked Comment

Most Eclipse editors track comments marked with //FIXME or //TODO tags. Tracked comments—i.e. task tags—are different for source files written in other languages. To add or configure task tags, navigate to Window > Preferences and use the keyword task tags to display the task tag configuration menus for specific editors/languages.

Figure 2.8. Task Properties

Alternatively, you can also use Edit > Add Task to open the task Properties menu (Figure 2.8, “Task Properties”). This will allow you to add a task to a specific location in a source file without using a task tag.

Figure 2.9. Problems View

The Problems view displays any errors or warnings that occurred during the execution of specific actions such as builds, cleans, or profile runs. To display a suggested "quick fix" to a specific problem, select it and press Ctrl+1.