Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Orion/Plan/0.4
Contents
Introduction
This document is a place to brainstorm about what we want to do in 0.4.
Themes
Most of the work in Orion should fall under some agreed upon themes for the release. This is a working list of ideas. If some themes can be coalesced into others that is fine. To start this is a fairly large list which needs to be prioritized.
Language Tooling
- Need a parser that can handle errors
- Investigate CodeMirror modes support for language highlighting within the editor
- CSSLint a regular part of Orion
- Syntax highlighting needs to be based on our parsing vs. regular expressions
- Validators for CSS, html, JavaScript
- Initial Browser debug communication and injection to handle console commands from Orion
Platform
- Update our 3rd party libraries including DoJo, RequireJS JSDoc
- Closer alignment with OSGi services
- Authentication integration with service registry
- Examine use of require.js and module granularity
- Localization support
- Long running tasks bug 344148 bug 344012
- Search and replace improvements bug 359739 bug 344200 bug 334709
- User access to preferences
- There is also the Editor items under consideration here Editor Items for 0.4
User Experience
- Improve Mobile UI experience
- Support patch workflow and improve branch management in Git bug 361425 bug 361909 bug 360472 bug 345397 bug 359273 (blocked by bug 309355 in JGit)
- Investigate approaches for deeper cross-site integration (delegated UI / bookmarklets)
- Identifying common tasks and providing better access to contextual movement bug 361003 bug 361425 bug 361425 bug 347066 bug 357787
- Semantic URLs with relavant contexual information for the task bug 358769
Infrastructure
- Improve build capabilities to remove reliance on shell access bug 348575
- Improve the test coverage and capabilities