Eclipse Orion 5.0.0

The main deliverables for the Orion 5.0 release are a multi-user server based on a Java runtime and a single-user server based on a Node.js runtime.

With each of these two runtimes, the client code representing the features of Orion will be served to a supported browser and allow additional functionality to be installed client side through a plug-in framework.

Primary support is for scripting languages however any file type can be edited.

The multi-user Java Server provides enhancements not found in the Node.js server including Git support, long running tasks, authentication, and an indexed search service.

Features - There will be an investigation by some of the Orion team into new features.

• Container Support for generic tooling on Project Workspace (Docker.io)
• Push to CloudFoundry capabilities from a Project Page
• User Assistants for Application Development (features, libraries)
• Additional Getting started features and landing elements
• Migration of Orion documentation to MarkDown from Wiki pages

Infrastructure - Changes to Build, deploy, test, hosting

• Migrate fully to Hudson build, test, deploy to orion.eclipse.org
• Deployment of the Orion MarketPlace
• Investigate Selenium Test framework for UI
• Clear and utlize the Mocha test framework as a replacement for JSTestDriver
• Optimize the user meta-data inquiries when using the new server layout

Core - Changes or enhancements to core framework and APIs

• Client side and server side work on user prefs and meta-data
• Font based icons (better for hi-rez, theming colour changes)
• Login Page increase in information (what is Orion)
• Landing experience (getting started, wizards as per new features above)
• Separate Syntax Highlighting framework into APIs and Implementation (carving out JS, CSS, HTML formatting and writing new implementations for other languages)
• Search - investigate options for either replacement or altering to better support Coding based queries
• Contributed Editors - Allow support for plugins to provide editor replacements (example, Markdown editor/viewer)
• Widget Work - Eliminate code duplication, consolidate tooltips and menus, deliver a solution for the context menu issue users have complained about
• Offline - continue to investigate
• JS Content Assist - JSDoc (or new spec based), provide dynamic index file loading, generate additional index files for common libraries
• ESLint - look at implementing the top linting features and/or obtaining clearance for existing rules.  The framework is already cleared for use.
• Plugin Trust model
• Persistent Sessions for less login prompts
• Implementing new Deferred

Community Involvement - would like participation from the community on investigating these areas

• JSFiddle capabilites on an Orion page
• Psudo anonymous multi-user editing of content similar to Etherpad