Skip to main content

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.

Jump to: navigation, search

Difference between revisions of "Orion/Plan/0.5"

< Orion‎ | Plan
(Introduction)
(Introduction)
Line 3: Line 3:
 
This document is a place to brainstorm about what we want to do in [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;field0-0-0=everconfirmed;target_milestone=0.5%20M1;target_milestone=0.5%20M2;target_milestone=0.5;product=Orion;classification=Eclipse 0.5].
 
This document is a place to brainstorm about what we want to do in [https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;field0-0-0=everconfirmed;target_milestone=0.5%20M1;target_milestone=0.5%20M2;target_milestone=0.5;product=Orion;classification=Eclipse 0.5].
  
The official plan document will be linked here when available.
+
The official plan document is [eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/orion/plans/orion-project-plan-0-5.xml here].
  
 
= Themes =
 
= Themes =

Revision as of 10:57, 12 March 2012

Introduction

This document is a place to brainstorm about what we want to do in 0.5.

The official plan document is [eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/orion/plans/orion-project-plan-0-5.xml here].

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

  • Parsers, Languages, Highlighting, Refactoring, etc.
    • +1 for Python

Platform

  • 3rd Party Libraries existing upgrades and new libraries.
    • dojo 1.7 requires testing/removing workarounds
  • Authentication
  • Localization (i18N)
  • Accessibility
  • Search
  • Compare
  • Additional File Systems
  • Plugin Model and Architecture for describing, identifying, discovering and installing
    • Support catalogs via a feed as well as page redirection
    • Internationalization strategy for plugins
  • Preferences/Settings
    • UI, how does a plugin describe the user-changeable preferences - related to bug 340469 [ Anton ]
    • General settings bug 373287 [ Anton ]
    • Editor settings improvements bug 369346 and bug 372139
    • Support settings for Editors other than JavaScript
  • Editor - bidi
  • URI Templates
  • Command line console bug 369608 [Kris]
  • Access to server logs and stacktraces bug 372034
  • Generic mechanism for cross page communication bug 372045
  • Sequenced tasks
  • Visual plugin, delegated content, and shell services (see wiki discussion) bug 372914
  • Propagating markers from an out of client build back to Orion editor

User Experience

  • Workflows, URI Template usage across sites
  • Improve workflow for accepting contributions from github bug 369591 [Szymon]
  • Integrate with GitHub and Gerrit review flow bug 372486
  • Mobile experience
  • Landing page (deferred from .4)
  • Unify look & feel of all Git pages [Szymon, Libing]
  • Unify/formalize use of section outliners, section replacement [Susan, Szymon, Anton] bug 368848
  • Improve progress reporting bug 371261
  • Improve file uploads - for single files as well as zips and native drag and drop bug 335890 [ John, Jay, Anton ]
  • Open up a group of files that you were working on bug 373290
  • Orion to restore itself to the last state you left in in when you last logged in ( files you were working on open in tabs etc )

Infrastructure

  • Improve build capabilities to remove reliance on shell access bug 348575 [John]
  • testing infrastructure
    • page level verification

Git support [Tomek]

Others?

  • Deployment Scenario - Orion living on my website ( e.g HostMonster ). bug 373374

Back to the top