cmsc 466 / 666

Download CMSC 466 / 666

Post on 25-Feb-2016




1 download

Embed Size (px)


CMSC 466 / 666. Yong Rao Feb. 11, 2004 Revised Mar. 15, 2004. TOPICS. Project Requirement Introduction to Eclipse. Project Requirement. Please send an email to about your 1. group members 2. company name and a brief introduction . - PowerPoint PPT Presentation


  • CMSC 466 / 666Yong Rao Feb. 11, 2004Revised Mar. 15, 2004


    Project Requirement

    Introduction to Eclipse

  • Project RequirementPlease send an email to about your

    1. group members 2. company name and a brief introduction

  • Expected ProjectAn fully functional on-line site for your proposed company

  • Project RequirementClient Presentation logic : JSP, ASP, PHP etc.Business Logic: Java Beans, Java Servlets or other applications etc. Database server : Oracle, MySql, MS SQL server etc.

    Choose the one that best matches your business

  • Presentation SchedulesPlease turn in the following things at least 1 day before your presentation 1. Final Project report modeled by standards of scientific publication. 2. Group member contribution log. 3. Source codes (optional )

    Please make a demo on the day right before or after your class presentation

  • Beyond theseBusiness Setup Why do you want to setup this companyWhere will you register and host your siteWhat functionalities you will provideand more ...Business Model SelectionWhy you select a certain modelSupporting Technology selectionWhy you choose certain technologies Detailed implementation

    Show your work

  • Introduction to Eclipsehttp://www.eclipse.org

  • Eclipse OriginsEclipse created by OTI and IBM teams responsible for IDE productsIBM VisualAge/Smalltalk (Smalltalk IDE) IBM VisualAge/Java (Java IDE)IBM VisualAge/Micro Edition (Java IDE)Initially staffed with 40 full-time developersGeographically dispersed development teamsOTI Ottawa, OTI Minneapolis, OTI Zurich, IBM Toronto, OTI Raleigh, IBM RTP, IBM St. Nazaire (France)Effort transitioned into open source projectIBM donated initial Eclipse code basePlatform, JDT, PDE

  • Brief History of Eclipse1999April- Work begins on Eclipse inside OTI/IBM2000June - Eclipse Tech Preview ships2001March- opensJune- Eclipse 0.9 ships October- Eclipse 1.0 shipsNovember- IBM donates Eclipse source base - board announced - opens2002June- Eclipse 2.0 ships September- Eclipse 2.0.1 ships November- Eclipse 2.0.2 ships2003 March- Eclipse 2.1 ships

  • Introduction to EclipseEclipse is a universal platform for integrating development toolsOpen, extensible architecture based on plug-ins

  • Eclipse Plug-in ArchitecturePlug-in ADeclares extension point PDeclares interface I to go with PPlug-in BImplements interface I with its own class CContributes class C to extension point PPlug-in A instantiates C and calls its I methods

    plug-in Aplug-in Bclass Cinterface Iextension point Pextensioncontributescreates, callsimplements

  • Eclipse Plug-in Architecture

  • Plug-in Architecture - SummaryAll functionality provided by plug-insIncludes all aspects of Eclipse Platform itself

    Communication via extension pointsContributing does not require plug-in activation

    Packaged into separately installable featuresDownloadable

  • Plug-in Development EnvironmentPDE = Plug-in development environmentSpecialized tools for developing Eclipse plug-ins

    Built atop Eclipse Platform and JDTImplemented as Eclipse plug-insUsing Eclipse Platform and JDT APIs and extension points

    Included in Eclipse Project releasesSeparately installable featurePart of Eclipse SDK drops

  • PDE templates for creating simple plug-in projects

  • PDE editor for plug-in manifest files

  • PDE - SummaryPDE makes it easier to develop Eclipse plug-ins

    PDE also generates Ant build scriptsCompile and create deployed form of plug-in

  • Java Development ToolsJDT = Java development toolsState of the art Java development environment

    Built atop Eclipse PlatformImplemented as Eclipse plug-insUsing Eclipse Platform APIs and extension points

    Included in Eclipse Project releasesAvailable as separately installable featurePart of Eclipse SDK drops

  • Java-centric view of files in Java projects

  • Eclipse JDT - SummaryJDT is a state of the art Java IDEJava views, editor, refactoringHelps programmer write and maintain Java codeJava compilerTakes care of translating Java sources to binariesJava debuggerAllows programmer to get inside the running program

  • Eclipse PlatformEclipse Platform is the common baseConsists of several key componentsWorkspaceWorkbenchSWTJFaceTeamHelpDebugAnt

  • Workspace ComponentWorkspace holds 1 or more top-level projectsTree of folders and files

  • Workbench ComponentSWT generic low-level graphics and widget setJFace UI frameworks for common UI tasksWorkbench UI personality of Eclipse PlatformWorkbenchSWTJFace

  • SWTSWT = Standard Widget ToolkitGeneric graphics and GUI widget setbuttons, lists, text, menus, trees, styled text...

    SimpleSmallFastOS-independent APIUses native widgets where availableEmulates widgets where unavailable

  • SWT : Authentic native windows look and feel

  • JFaceJFace is set of UI frameworks for common UI tasksDesigned to be used in conjunction with SWTClasses for handling common UI tasksAPI and implementation are window-system independent

  • JFace APIsImage and font registriesDialog, preference, and wizard frameworksStructured viewersModel-aware adapters for SWT tree, table, list widgetsText infrastructureDocument model for SWT styled text widgetColoring, formatting, partitioning, completionActionsLocation-independent user commandsContribute action to menu, tool bar, or button

  • Workbench ComponentWorkbench is UI personality of Eclipse Platform

    UI paradigm centered aroundEditorsViewsPerspectives

  • Team ComponentVersion and configuration management (VCM)Share resources with team via a repositoryRepository associated at project levelExtension point for new types of repositoriesRepository provider API and frameworkEclipse Platform includes CVS repository providerAvailable repository providers*ChangeMan (Serena)- AllFusion Harvest (CA)ClearCase (Rational)- PerforceCM Synergy (Telelogic)- Source Integrity (MKS)PVCS (Merant)- TeamCode (Interwoven)Microsoft Visual Source Safe

  • Debug Component

  • Ant ComponentEclipse incorporates Apache AntAnt is Java-based build toolKind of like Makewithout Make's wrinklesXML-based build files instead of makefilesAvailable from workbench External Tools menuRun Ant targets in build files inside or outside workspacePDE uses Ant for building deployed form of plug-in

  • Help Component

  • Eclipse Platform - SummaryEclipse Platform is the nucleus of IDE productsPlug-ins, extension points, extensionsOpen, extensible architectureWorkspace, projects, files, foldersCommon place to organize & store development artifactsWorkbench, editors, views, perspectivesCommon user presentation and UI paradigmKey building blocks and facilitiesHelp, team support, internationalization,

  • Thank you.

    Tier 1: the client contains the presentation logic, including simple control and user input validation. This application is also known as a thin client. Tier 2: the middle tier is also known as the application server, which provides the business processes logic and the data access. Tier 3: the data server provides the business data. Object Technology International