22
Page 1 Eclipse 3.1 IDE Overview

Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Embed Size (px)

Citation preview

Page 1: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 1

Eclipse 3.1 IDE Overview

Page 2: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 2

Eclipse IDE Overview

• Workspace

• Workbench

• Resources

• Perspectives

• Views

• Preferences

• Plugins

Page 3: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 3

The Workspace, the Workbench and Resources

• The “Workspace” is the directory where Eclipse will store your projects. You can have as many Workspaces as you like, although only one is active at any time. You can choose one as a default which Eclipse will automatically select each time you start it.

• The “Workbench” is the general name given to the complete window space the Eclipse IDE occupies on your screen. The Workbench will have a Menu Bar, a Tool Bar, a status area and a “Perspective” which

may contain several “Views” and “Editors

• The things that Eclipse operates on are, in general, called “Resources”. Your Workspace is a Resource, as is any Project you create, and as are all the files in your Projects.

• Eclipse makes only token efforts to operate on files which are not contained in a Project in your Workspace

Page 4: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 4

The Workspace, the Workbench and Resources

• A Workbench, showing an empty Workspace

Page 5: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 5

Tool bar

PerspectiveandFast Viewbar

ResourceNavigatorview

Stackedviews

Propertiesview

Tasksview

Outlineview

Bookmarksview

Menu bar

Messagearea

EditorStatusarea

Texteditor

Perspectives

Page 6: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 6

Editor

Package Explorer

LombozJ2EE View

Perspectives

Java Perspective

Tool Bar

Menu Bar

MessageArea

StatusArea

Page 7: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 7

Menu Bar

Navigator View

Outline View

Stacked Views Problems

View

Tool Bar

C/C++ EditorSyntax Highlighting

Content Assist

Code assist

Integrated Debugging Features

C/C++ Perspective

Page 8: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 8

Views

• Views are frames which display data in a particular way.

• For example, the “Package Explorer” view (left) arranges its display around the structure of Java packages, while the “Resource Navigator” view (right) reflects the directory structure of the project as it exists on disk.

Page 9: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 9

Views

• The “Outline View” shows the structure of the current file

Page 10: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 10

Editors

• Most perspectives will have an editor area and some views.

• Editors can be associated with specific file types, or you can manually open a file with a specific editor. If there’s a system association of a file type with an application that’s not recognized by Eclipse, that application will be automatically opened, with sometimes surprising results.

• Many editors can be open at once, but only one can be active. The menus and toolbar may change to include functions unique to the active editor.

Page 11: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 11

Editors

• The COBOL Editor

Page 12: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 12

Editors

• The Java Editor

Page 13: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 13

Editors

• A Java file opened in the Text editor

Page 14: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 14

Preferences

• The Eclipse IDE has many parameters which you can change to suit your personal preferences.

• The Preferences settings are accessed through the Window->Preferences menu selection.

• Each feature or plugin that is installed in an Eclipse instance can add its own set of preferences and can access the global preferences.

Page 15: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 15

Preferences

Page 16: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 16

Eclipse Help System

• The Eclipse IDE has a comprehensive help system which can be accessed via the Help menu.

• Many GUI items on the Workbench have context-sensitive help links which allow you to directly access the appropriate section of the Help system by pressing “F1” while the item has focus.

Page 17: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 17

Eclipse Help System

Page 18: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 18

Plugins

• Modules that provide specific functionality such as the Unisys Composite Application plugin that comprises of the following

• OS2200 plugin• Provides traditional development environment within Eclipse

• Uses file residing on 2200 as project repository (requires CIFS)

• OS2200 defined project• unique project name within Eclipse• Connection (define connection to OS2200, cifs as well as userid password

used by Telnet plugin)• Supports asm, masm, c, pls, h & cob file extensions

• Build of the project triggers a runstream defined on the 2200 (could be an SSG setup by system administrators)

Page 19: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 19

Plugins

• OS2200 plugin• Provides 'OS 2200' console to display build information (note this is a

console in Eclipse terms, not OS2200 terms)

• Telnet plugin• Provides a Telnet plugin that is used to establish terminal

connections to the OS2200

• JAI plugin• Provides a Java Application Integration plugin that simplifies the use

of the 0S2200 TIP/HVTIP Resource Adapters (note this capability requires CITA)

Page 20: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 20

OS2200 Plugins

Page 21: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 21

SUBVERSIONSource Repositories

ProjectXYZ

tags

branches

pom.xml

trunk

project folders

Importproject

filestructure

MAVENArtifact Repositories

CONTINUUMBuild System

JIRARequirements,

Issues & Tracking

.svn

pom.xml

project folders

ProjectXYZ

CheckoutCheckin

Import project pom.xml from repository

ProjectXYZ

Developer

Local MavenArtifact Repository

RepOne

Local MavenArtifact Repository

Maven

ThirdParty

Work

RepOne

RepTwo

Sandbox

repository type ’fsfs’

Dependencies

CONFLUENCEDocumentation

System

Reference System

’build’

Store build result in RepOne Respository

Returned Dependencies

Request Dependencies

Dependencies

ReturnedDependencies

RequestDependencies

’deploy’

APP Server

Deploy application from RepOne Respository

send build result emails to ’notifiers’ in project pom.xml

Nightly Testing

if nightly tests successful, componentsare released into the developers repository

developers update local repository with updated components

Typical Developer Environment

Eclipse

Eclipse, plugin for OS2200, Cobol, Plus, etc

Page 22: Page 1 Eclipse 3.1 IDE Overview. Page 2 Eclipse IDE Overview Workspace Workbench Resources Perspectives Views Preferences Plugins

Page 22

Eclipse 3.1 IDE Overview