Notice: This Wiki is now read only and edits are no longer 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.
Simplify existing workflows
Mostly this is reducing the number of links/pages to get where you need to go. Identifying common tasks and providing better access to contextual movement through Orion.
- git branch management
- commands available in more places, esp editor bug 361003
- Support patch workflow in Git bug 361425
Demonstrate site-crossing workflows
This is identifying and implementing workflows that let you cross sites seamlessly while working with Orion. We need some workflow definitions for these, but ideas kicked around include:
- clone a repo from bugzilla / github
- use w3c validators for html in orion
- allow to edit images with online editors like Pixlr or Picnik bug 362067
Mobile friendly UI
This includes both mobile-specific layouts and techniques as well as general simplification/usability improvements that help on both the desktop and in mobile
- get rid of unnecessary side panes (favorites, etc.)
- device specific styling (fonts, text vs. icons, sizes, etc.)
- address current command hover behavior
- touch screens
Debug
- What work could begin on a Debug platform or a DOM inspector
New function
New function that is important (maybe a more specific theme should be identified here...)
- CSS tooling (CSS3 aware) - outliner, content assist, etc
- support querying for running progress tasks bug 344148
- Git submodule support bug 361909
- Creating a patch
- Accepting a text patch into your Workspace
- TextEditor - Selecting the display size for tabs and using tab key to enter, for example, 4 spaces
- Plugin's page to turn into a preferences page
- Long running task (long running
- Support for multiple tasks
- Wildcard search
- Global search and replace
Language Tooling
- JavaScript Tooling
- Enablement for other languages
- Need a parser that can handle errors
- Error reporting
- Incremental problems vs. failing on first
- refactoring (extract function, inline variable?)
- quickfixes (example is javascript)
- CSSLint thing a regular part of Orion
- Data URIs for images and data into CSS file
- Follow links within Javascript files. At the moment now they're just a highlight.
Platform issues
- dojo 1.7(.1?)
- Require JS 1.0
- JSDoc 3.0?
- API into the service registry needs to be improved
- Login starting plugins, too asyncronous, hard to use
- How we bootstrap
- Authentication issues
- blocking ability to cache successfully
- impacting the site crossing issues
- Ensuring our architecture is not reaching and components can be consumed without referencing too much
- Need to have a better solution to consuming RESTful services
- Pair down Orion Core - a lot of specifics to the server have slipped in (navigator, editor, preferences)
- Improve the way we're using require.js - package and a bunch of types in it - there's some thinking that we need to go to the type level. This has changed with the current version
Build
- Need better build capabilities including Hudson launches for build and deploy
Evangelization
- significant amount of time should be a requirement on team members ==
- Working on more integration with other projects
- Getting integrations going without necessary buy-in up front
- Example of a real multi-server application. An example with non-static content. Server to server site crossing
- Describe the problems we are having and look for feedback
- New landing page
- Revamping the OrionHub experience
- Additional file systems such as S3 or Dropbox
Localization
- Need to validate what components need to be localized
- What are the available techniques and patterns we can use
Test Infrastructure
- Test automation and coverage. (JSCoverage to analyze?)
- Increased test cases across the board