- 1 Resources
- 2 Theme Categorization
- 3 Active Themes
- 3.1 Platform Support
- 3.2 Rich Client Platform (RCP)
- 3.3 Embedded Device Software
- 3.4 Ease Of Use
- 3.5 Technology Trends
- 3.6 Scaling Up
- 3.7 Enterprise Ready
- 3.8 Design for Extensibility
- 4 Persistent & Pervasive Themes
- 5 Deferred Themes
- 6 Pending Themes
Eclipse themes are described in one of four categories.
- Active themes are those that are ongoing and changing. From time to time, some Active themes will become Persistent and Pervasive.
- Persistent and Pervaisve themes are not time or release specific. Persistent and Pervasive themes are not only a signal of importance, but permanence.
- Deferred Themes are not an indication of priority, but are an indication that there are technical or resource inhibitors preventing them from becoming an Ative Theme. Deferred themes are a signal to the ecosystem that help is needed.
- Pending Themes are new and interesting themes that have not yet been properly explored and discussed to become an Active theme.
While Eclipse has been very successful with Java developers on Windows systems, we endeavour to provide platform support for additional existing and upcoming platforms.
Approximately 85% of Eclipse download requests are for the Windows OS. With the VISTA release there are a number of efforts to port Windows applications. This presents an opportunity for organizations who will take the opportunity to migrate to the more ubiquitous and portable Eclipse platform. In order to leverage the opportunity as much as possible, it is essential that relevant Eclipse projects support and leverage VISTA. For example, Avalon APIs need to be implemented in SWT.
Vista will be important as both a platform used by developers, as well as one to which the resultant applications and/or products will be deployed.
Linux continues to grow in market share as a platform for projects at all levels. We need to offer strong support for Linux on two dimensions:
- As a deployment platform for applications developed using Eclipse technology
- As a platform used by developers as their primary working environment
Mac OS X
Mac OS X is used in many development, open source and end user environments and is a very active community. Eclipse needs to provide some level of support for users of this platform.
Java SE Mustang, Dophin and Beyond
Eclipse endevours to support next generations of the Java platform in a timely manner. The first stage of support is that end users can build applications on the latest JDK versions. The next stage of support is that projects themselves are able to take advantage of the latest JDK changes.
Rich Client Platform (RCP)
RCP adoption has been strong by the ecosystem in 2006. The goal is for projects to support and use the Eclipse RCP as much as possible.
Aside from general use of RCP, there are two additional dimensions to this theme.
- Enabling broader use of RCP on smart devices such as PDAs and enhancing the abilities of RCP to work in these environments.
- Making RCP as easy as possible to use so that it's easier for application developers to adopt.
The Equinox project is an example of the focus on the OSGi component model within Eclipse. The Ecosystem requires Additional PDE enhancements to facilitate developing and deploying RCP-based applications, and for OSGi bundle manifest tooling.
Embedded Device Software
This theme describes additions to Eclipse to provide standardization and extensibility to enable embedded tools providers, real-time operating system providers, semiconductor vendors, and hardware developers to create embedded-specific capabilities on top of standard Eclipse projects such as the Platform, JDT, eRCP, CDT, and TPTP. These capabilities should include the following.
- Drive consistency in the workflow for embedded development tools and projects.
- Provide an extensible embedded debug model implementation of the new Eclipse 3.2 platform API’s. This debug model will enable integration of debug engines from multiple vendors for debugging bare metal hardware, bringing up operating systems, and developing applications on single and multi-core hardware. This implementation will also enable vendors to integrate target simulation and emulation environments with Eclipse.
- Build a remote target launching, exploring, and management framework with extensible real-time operating system visibility. This framework will provide complex launching capabilities for deploying multiple target images to multiple devices.
- Enable C++ GUI application design, build, and deployment for mobile devices running any operating system. Also enable vendors to customize run-time libraries for their operating systems.
- Provide mobile Java application development support for J2ME mobile profiles, including extensible frameworks for devices and emulators and capabilities for application build and deployment, code obfuscation, code optimization, image signing, and localization.
- Complete the 1.0 release of the embedded Rich Client Platform.
- Enable mobile Linux application development, including design, development, debug, and deployment of cross-compiled applications.
- Provide embedded testing capabilities - monitoring, profiling, and unit testing.
Ease Of Use
The Eclipse components need to not only provide features that advanced users demand, but also be something that users find simple to use. The goal of this theme is to ensure that Eclipse-based products are simple to use for users with widely-varying backgrounds and skill sets performing a variety of tasks. Examples include:
- Provide Eclipse User Experience Guidelines to ensure consistency and usability (including Accessibility) across projects. [see 121303].
- Usability reviews and updates to new and existing user interfaces to streamline common processes and clarify concepts and terminology.
- Improving support for Cheat Sheets to assist users in performing tasks. [e.g. 56234, 69735]
- User personas/roles to streamline the user interface to adapt to specific user needs. [e.g. 73941]
- More robust/tolerant Java editor: The Java editor is quite intolerant of broken code - its better than it used to be but could be better.
- Enhanced user documentation, tutorials, white papers, demonstrations.
For example, if a user interface wizard provides a short path to performing a task, make sure that usability studies have identified the most common task performed by the target users.
Existing and new Eclipse projects need to consider key technology trends in the market to ensure that the Eclipse platform continues to retain it's leadership as the framework and tool of choice for developers. Relevant trends identified are:
Extending to be Life-cycle Platform
Web 2.0 and AJAX
AJAX and other "Web 2.0" technology (see Wikipedia discussion on Web 2.0) has enabled the development of a new generation of web sites that provide a rich and user-friendly experience in a wide variety of applications. While the initial adopters of this technology have been social web sites, it's adoption is increasingly seen in business applications such as CRM systems.
As developers shift from the development of traditional web sites to Web 2.0-style sites, the role of Eclipse as a development framework for these applications must be considered. In order to retain these developers, the Eclipse platform should provide strong support for developing applications that leverage Web 2.0 technologies such as AJAX and Web Services APIs.
Due to power constraints, there is a trend towards multiple cores on a CPU instead of merely increasing the CPU frequency.
- Enable tools to build products and applications that work well with multi-core CPU hardware.
- Leverage multi-core CPU hardware in projects.
Diverse application software such as payroll, datawarehousing, and reporting now routinely manipulate large amounts of data that exceed 2GB. Using 64-bit CPUs enables these applications to manipulate large data in memory rather than having to write and read intermediate results to much slower disks.
This refers to the need for Eclipse to deal with development and deployment on a larger and more complex scale. Increasing complexities arise from:
- Large development teams distributed in different locations,
- Large source code bases, large amounts of data, multiple scripting and programming languages, complex build environments that have been developed incrementally over time the dynamic nature of new source code bases and their interaction with configuration management, and build environments involving many different tool chains and build rules.
- Large volumes of data
- Performance improvements in memory footprint, user perceived response times, and start-up times as the complexity and number of projects, files, users, and plug-ins grow (10X-100X over the next two years). This is particularly important in client/server environments where a single Solaris, AIX, Linux or HP-UX server must support dozens of concurrent Eclipse users and where Eclipse competes mostly with command line tools.
- Improve support for and performance with Motif based window managers on Solaris (drag and drop, etc)
- Improve remote X window performance
- Improve performance when creating, loading, importing and closing projects with slow file systems (networks)
- All Eclipse projects should identify common use cases and publish performance benchmarks on every milestone.
- Ability to deal with extremely large projects and workspaces where there is a large number of developers working on different, and sometimes overlapping parts of the source tree simultaneously. This may include a more efficient way to manage multiple workspaces. Examples of large projects include Mozilla and Open Office.
The Update Manager is a fantastic tool for a person updating his/her own installation. Preference Import & Export and Team Project Files further extend Eclipse in this regard. However in large organisations, for various reasons, the organisation might want to make sure that large numbers of users have and maintain similar Eclipse set-ups. This could involve various aspects of the system, eg. what Eclipse components are installed, what preferences and other values are set etc. On one level this could be a convenience thing so that this would enable central management to help developer workstations be up-to-date, on a different level some organsiations might want a policy of strict control where the maintenance of the environment is also about enforcing a development policy and toolset, this would need more work in that it would require Eclipse internal policy management.
Further Enhance Update Manager
The Eclipse Update Manager provides initial technical capabilities to enable delivering software as a service. This capability can be leveraged more to provide updated components across Eclipse projects to developer desktop in an asynchrous fashion without the developer having to do a manual dependency analysis.
- Dependency (across Update Sites?)
- Version-level Conflicts?
- Easier to access rollback?
Ease of Deployment, Servicability & Managability of Large Scale Installations
- Zero-conf discovery of Update Site & Pref/Config Repositories
- Shared Hierarchical Configuration (First-class Preferences, Perspective Configurations, Team Share Preferences, Update Site Preferences, etc.)
- Simplified Update of the Platform Bits
- Plug-in Cross-Dependency Awareness / Version Incompatibility
- Improve the Eclipse project and workspace concept to allow overlapping environments
- Ability to fit into an existing environment of source files, build artifacts and version control repositories with minimal disruption to let developers complete a full edit-compile-debug cycle in the shortest possible time. This may include better support for multiple programming languages across language toolkits for improved usability. This would also include a more flexible project model.
Features to enable a developer to get started as part of a (new or exisiting) team. This could include
- making sure that the person has the correct software set-up,
- that the software settings are appropriate for the team and then finally (which falls outside perhaps of the above management) that the projects and the project content can be easily "bootstrapped" to the new workstation.
Example Story: Here the ultimate goal could be that once a "team manager" has been told the IP address of a new member's PC, he would have 10 minutes later a fully configured Eclipse workstation with all the project's Eclipse project and all related settings on his/her machine.
Design for Extensibility
Within the Eclipse community, many development projects are defining new development platforms on top of other Eclipse projects. Concrete examples include the Business Intelligence Reporting Tools, the Data Tools, and the Device Software Development Platform projects. It is recognized, however, that some function is not strictly required by the underlying projects but are important to enable other platforms to succeed. This theme also includes effort to assure platform integrity.
Some identified key requirements for this theme are:
- Robust API documentation
- API tools to detect use of internal interfaces
- Expose meaningful building block APIs
- Open the internal JDT (UI) interfaces to enable tools to seamlessly facilitate and interact with the JDT core and UI layers. For example the parsing and AST functionality.
- Enhance the Debug API to enable seamless debugging across mixed (Java+native) languanges
- Provide a more flexible mechanism that can be used to debug non-Java programs. This is both in the debug model and presentation
- Provide for debugging a system comprised of multiple languages
- Enable task automation
- Provide access to Eclipse APIs and resources from scripting languages
- Provide the capability to record, edit, playback macros, representing a set of user interface actions.
- Provide a better experience for the co-existence of offerings from multiple vendors in a single Eclipse installation
- Permit offering brand/identity to show through (e.g. On the splash screen)
- Allow for license management of "products" (i.e. Aggregations of features)
- Integrated diagnostic capabilities - e.g. When a user encounters a problem, providing assistance on the where the problem originated, which product
- Loosen the strong file orientation by providing an abstraction layer of logical objects to allow one to extend Eclipse functionality tools working at a higher abstraction level.
- Authoring, deploying and managing components/features/etc.
- Bolster OSGi Adoption (via authoring assistance, etc.)
- Headless Execution
- Server-side Runtime Infrastructure
- Core & UI Split
Persistent & Pervasive Themes
Every project should support and make a statement on their accessibility compliance. In the U.S., this means Section 508 compliance; in the European Union, this is the Web Accessibility Initiative of the World Wide Web Consortium (W3C).
Internationalization & Localization
Every project should support both internationalization and localization:
- Internationalization (I18N)
Each project should be able to work in an international environment, including support for operating in different locales and processing/displaying international data (dates, strings, etc.).
Each project should provide an environment that supports the localization of the technology (i.e. translation). This includes, but is not limited to, ensuring that strings are externalized for easy translation.
Where possible, projects should use an open and transparent process to create, maintain and deliver language packs translated into multiple languages in a timely manner. The primary languages to consider are: English, Simplified Chinese, Traditional Chinese, Japanese, French, German, Spanish.
Upward compatibility is a critical aspect of developer satisfaction and community growth. Developers need to be able to adopt the latest release of Eclipse technology without reworking their applications. Extensive rework incurred during a migration will lead to developer frustration and the possibility that they will evaluate and adopt other tools. Smooth upward migration is therefore a core Theme that all projects must consider.
- Assuring release-to-release migration is supported (e.g., resources, workspaces, API, as appropriate).
- Assuring API compatibility release-to-release, including testing for upward compatibility
- Clear statements indicating which APIs are intended for internal use only (and are not gaurenteed to be upward compatible)
- Providing tools that automate the migration process where possible
Consistent Multi Programming Language Support
The original vision of Eclipse was to accelerate the creation of IDEs. There is a lot of work to do to make it simpler to create language-specific IDEs. Our vision is to:
- Make it easier to create language specific tools in a consistent way
- Enabling source files written in multiple languages within the same project.
Vertical market-specific initiatives
With the establishment of Eclipse as a dominant platform for building tools and applications, it is logical that Eclipse technology begin to play a major role in vertical industry initiatives. Vertical markets should not be confused with Technology Segments where Eclipse technology is generally consumed very rapidly. Examples of quick Eclipse adoption in new technology segments include Ajax and other Web2.0 tools and applications. Vertical markets are much more solutions oriented and have broad reach into a technology stack. The Eclipse projects should be aware that Eclipse is becoming a major player in the Healthcare and Automotive verticals, and there are signs of it becoming a key platform in a number of other verticals. In Automotive, for example, Eclipse based technology is used in CAD tools, workflow tools, embedded design tools, etc.