PROSA - Eclipse Is Just What?
•Download as KEY, PDF•
1 like•567 views
The document introduces Eclipse, an open source development environment originally created for Java programming. It announces a talk by Tonny Madsen from RCP Company to provide an overview of the Eclipse platform, including its technical aspects, projects, organization, capabilities, and future. The talk aims to explain what Eclipse is, demonstrate its use, and answer questions.
Recommended
Recommended
More Related Content
What's hot
What's hot (17)
Similar to PROSA - Eclipse Is Just What?
Similar to PROSA - Eclipse Is Just What? (20)
More from Tonny Madsen
More from Tonny Madsen (20)
Recently uploaded
Recently uploaded (20)
PROSA - Eclipse Is Just What?
- 1. Eclipse Is Just What? “Onsdag 26.1. Introduktion til Eclipse Eclipse er et fremstormende open source-udviklingsmiljø (Eclipse IDE), der oprindeligt er udviklet med henblik på Java. Kom og mød Tonny Madsen, formand for Eclipse Danmark, foreningen for både professionelle, virksomheder og brugere. Tonny er til daglig direktør i RCP Company, der har specialiseret sig i udvikling, uddannelse og konsulentydelser inden for Eclipse. Han vil give jer et overblik over platformen, både teknisk, projektmæssigt, organisering, muligheder, fremtiden etc.” -- Bjarke Redistribution and other use of this material requires written permission from The RCP Company. PR0036
- 2. Agenda Eclipse is… what exactly? The Eclipse Architecture Demo Time Q&A 2 L0001 - 2010-11-27
- 3. Eclipse is… what exactly? 3 L0001 - 2010-11-27
- 4. Eclipse – The Sweets 4 L0001 - 2010-11-27
- 5. ECLIPSE – The Mitsubishi Car 5 L0001 - 2010-11-27
- 6. Eclipse – The Java IDE 6 L0001 - 2010-11-27
- 7. Eclipse – The Tools Platform 7 L0001 - 2010-11-27
- 8. Eclipse – The Application Platform 8 L0001 - 2010-11-27
- 9. Eclipse – The Application Platform 9 L0001 - 2010-11-27
- 10. IBM Lotus Notes Version 8 10 L0001 - 2010-11-27
- 11. 11 JDT Team PDE Resources CVS Workspace Eclipse RCP Git Help Eclipse Platform Update CDT Apache SWT WTP JFace File System DataTools Workbench Web Server BIRT Text Editor OSGi/Run-time A Little About SOA Intro PDP Preferences Navigator The Eclipse Architecture EMP Jobs Search ICU Commands Mylyn Registry L0001 - 2010-11-27
- 12. The Eclipse Story 1994: IBM develops VisualAge for Smalltalk – programmed in Smalltalk 1995: Java is released to a select group 1996: IBM develops VisualAge for Java – still programmed in Smalltalk November 1998: OTI (Object Technology International – part of IBM) is commissioned to develop new development platform for Java First known as VisualAge Micro Edition (VAME) and later Eclipse 7. November 2001: Eclipse 2.0 made Open Source 25. June 2004: Eclipse 3.0 released introducing Eclipse RCP Framework make-over introducing OSGi 12 xx
- 13. The Eclipse Story 2009: Eclipse 3.5 released – known as Galileo 27. June 2010: Eclipse 3.6 will be released Also known as Helios End of July, 2010: Eclipse SDK 4.0 Early Adopter Release First release of e4 technology June 2011: Eclipse 3.7 will be released June 2012: Eclipse 4.x will be released 13 xx
- 14. Basically… We need an architecture that supports distributed development over a large number of autonomous development groups We need a component concept where components are loosely coupled and can be started (and stopped) independently We need a way to describe external interfaces of components and dependencies between components We need a way to only start the components when they are needed, and not before – also known as late activation We need all this to work over multiple generations of components 14 L0001 - 2010-11-27
- 15. 15 JDT Team PDE Resources CVS Eclipse RCP Workspace Git Eclipse Platform Help Update CDT Apache SWT WTP JFace Eclipse Architectural Components File System Workbench DataTools Web Server BIRT Text Editor OSGi/Run-time SOA Intro PDP Preferences Navigator EMP Jobs Search ICU Commands Mylyn Registry L0001 - 2010-11-27
- 16. 16 Base Authentication Data Model Communication Data Model Eclipse RCP Logging Base Logic Eclipse Platform Audit Your Typical RCP Application Add-on SWT Add-on JFace Workbench Add-on Add-on OSGi/Run-time Add-on Help Add-on Preferences Intro Add-on Jobs Update ICU Apache Commands Debug Tools Registry L0001 - 2010-11-27
- 17. Organizing the Platform An Eclipse system is based on a number of basic concepts Plug-ins – a plug-in is the basic unit of software Fragments – a fragment is an add-on to an existing plug-in with additional functionality Features – a feature is a number of plug-ins that are distributed and updated as a whole Applications – an application is a Java class that implements a specific interface and is declared as such in the plug-in Products – a product is a set of features or plug-ins along with the appropriate branding 17 xx
- 18. Eclipse.dk – The Danish Eclipse Society Eclipse.dk was created in Marts 2007 as a meeting place for everyone interested in the Eclipse (www.eclipse.org) platform. The purpose of Eclipse.dk is as follows: To promote the knowledge of Eclipse in Denmark. To create networks amongst danish Eclipse-users and developers. To build knowledge on Eclipse in Denmark, especially In danish institutes of higher education. Between danish companies developing applications based on Eclipse. Create and maintain a web site on Eclipse for danish users – eclipse.dk. Strengthen the relations between danish and international Eclipse-users and organizations. The eclipse.dk society has members representing not only vendors of Eclipse-based products and services, but also users of the platform and representatives from institutions of higher education. 18 xx
- 19. Q&A 19 L0001 - 2010-11-27
- 20. About Me Tonny Madsen, Founder and Owner of The RCP Company 20 years of experience in system development in major companies 9 years experience as the Systems Architect of an 20+ MLoC project 9 years of experience with Eclipse and Eclipse RCP Eclipse Foundation Member Chairman of Eclipse.dk Extern Lecturer at IT-University on Model Driven Development and Domain Specific Languages Regular speaker at EclipseCon, Eclipse Summit, etc 20 L0001 - 2010-11-27
- 21. More Information The foundation: http://eclipse.org The Danish User Group: http://eclipse.dk The training: http://www.eclipse.org/community/training/classes.php Resources on Eclipse: http://www.eclipse.org/resources/ Consolidated Blog: http://planeteclipse.org/ 21 L0001 - 2010-11-27
Editor's Notes
- \n
- \n
- \n
- \n
- \n
- Just to make everybody aware that they actually know about Eclipse already. It is known technology – not new technology. ESB, web services and BPM are all considered new technology…\n
- The current view of Eclipse according to the Eclipse Foundation. Really, the same view as when Eclipse was first conceived.\n
- \n
- This is the prototype of the banking desktop. It looks and feels like an Eclipse application. Just see the L&F. No serious presentation branding has been performed… yet…\n\nOne area where e4 would have helped – the look could be Nordea look instead of Eclipse look.\n
- Is this Eclipse RCP?\nThe perspective switcher is different!\nViews in the “same position” of the perspective – a so-called folder – are shown differently.\nThe “Launch” button\nBased on Eclipse RCP!\nEarly demo based on Eclipse RCP 3.1\nLook of some native widgets has been changed!\nUI is a mix of SWT and Native Notes® windows\nThe workbench is recognizable yet different\n\nDomino, IBM, Lotus, Notes and Workplace Client Technology are trademarks or registered trademark of International Business Machines Corp. in the United States, other countries, or both.\n\nIBM Lotus Notes look&feel was designed by Mary Beth Raven.\n\nWould have been easier with e4, as this would have eased the structural changes as well.\n
- \n
- \nAlso an outline of the history of Eclipse\nSee http://www.ibm.com/developerworks/rational/library/nov05/cernosek/index.html \n
- \nAlso an outline of the history of Eclipse\nSee http://www.ibm.com/developerworks/rational/library/nov05/cernosek/index.html \n
- What are the main drivers for the Eclipse architecture?\n
- Eclipse products are built in layers.\nAt the bottom there are Eclipse RCP with the bare necessities. The RCP subsystems typically add visible features to the platform and provide APIs for extending their functionality. Some of these components supply additional class libraries that do not directly relate to an extension point, but can be used to implement extensions. For example, the workbench UI supplies the JFace UI framework and the SWT widget toolkit. \nThe platform layer adds the generic features needed for an Integrated Development Environment (IDE).\nThe different language support sits on top of the platform. The basic IDE features (known under the misleading name Eclipse SDK) includes two major tools that are useful for plug-in development. The Java development tooling (JDT) implements a full featured Java development environment. The Plug-in Developer Environment (PDE) adds specialized tools that streamline the development of plug-ins and extensions.\nLikewise for the many features of Calisto, Europa and now Ganymede. They are also layered to provide a set of basic features that are used by other features to provide better and more specialized tools.\nThe Resources, Workspace and Update components shown above is not really part of the very basic RCP component set. They are used very often in RCP applications.\n
- Using Eclipse RCP in an application is typically done the very same way as when used in Eclipse IDE.\nAt the bottom there are Eclipse RCP with the bare necessities.\nThe platform layer adds the generic features needed for any application in the specific environment.\nThe application itself is then placed at the top.\n
- The terms listed above are central to an Eclipse system and it is rather important to understand them in order to implement a big Eclipse application.\n
- \n
- \n
- \n
- \n