Transcript Eclipse 3.1 IDE Overview Page 1

Eclipse 3.1 IDE Overview
Page 1
Eclipse IDE Overview
• Workspace
• Workbench
• Resources
• Perspectives
• Views
• Preferences
• Plugins
Page 2
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 3
The Workspace, the Workbench and Resources
• A Workbench, showing an empty Workspace
Page 4
Perspectives
Menu bar
Text
editor
Tool bar
Perspective
and
Fast View
bar
Outline
view
Resource
Navigator
view
Bookmarks
view
Properties
view
Message
area
Stacked
views
Tasks
view
Editor
Status
area
Page 5
Java Perspective
Perspectives
Menu Bar
Tool Bar
Editor
Package
Explorer
Lomboz
J2EE View
Message
Area
Status
Area
Page 6
C/C++ Perspective
Menu Bar
C/C++
Editor
Tool Bar
Syntax
Highlighting
Content
Assist
Navigator
View
Code assist
Integrated
Debugging
Features
Outline
View
Stacked
Views
Problems
View
Page 7
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 8
Views
• The “Outline View” shows the structure of the current file
Page 9
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 10
Editors
• The COBOL Editor
Page 11
Editors
• The Java Editor
Page 12
Editors
• A Java file opened in the Text editor
Page 13
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 14
Preferences
Page 15
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 16
Eclipse Help System
Page 17
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 18
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 19
OS2200 Plugins
Page 20
Typical Developer Environment
Eclipse, plugin for OS2200,
Cobol, Plus, etc
Developer
Eclipse
ProjectXYZ
.svn
project folders
pom.xml
Local Maven
Artifact Repository
Nightly Testing
developers update
local repository
with updated
components
APP Server
Dependencies
’deploy’
MAVEN
Artifact Repositories
Checkout
Checkin
Reference System
if nightly tests successful, components
are released into the developers repository
SUBVERSION
Source Repositories
Deploy application from RepOne Respository
Store build result in RepOne Respository
RepOne
Returned
Dependencies
RepOne
CONTINUUM
Build System
Maven
RepTwo
ThirdParty
Request
Dependencies
Returned Dependencies
Request Dependencies
Sandbox
Local Maven
Artifact Repository
Dependencies
ProjectXYZ
’build’
Work
repository type ’fsfs’
Import
project
file
structure
ProjectXYZ
send build result emails to
’notifiers’ in project pom.xml
tags
branches
trunk
CONFLUENCE
Documentation
System
JIRA
Requirements,
Issues & Tracking
project folders
pom.xml
Import project pom.xml from repository
Page 21
Eclipse 3.1 IDE Overview
Page 22