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.4"

< Orion‎ | Plan
(customize/macros capability)
(Introduction)
 
(31 intermediate revisions by 6 users not shown)
Line 2: Line 2:
  
 
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.4%20M1;target_milestone=0.4%20M2;target_milestone=0.4;product=Orion;classification=Eclipse 0.4].
 
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.4%20M1;target_milestone=0.4%20M2;target_milestone=0.4;product=Orion;classification=Eclipse 0.4].
 +
 +
See the official plan document [http://eclipse.org/projects/project-plan.php?planurl=http://www.eclipse.org/eclipse/orion/plans/orion-project-plan-0-4.xml here].
  
 
= Themes =
 
= 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.
 
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 ==
+
== Language Tooling ==  
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.
+
* Need a parser that can handle errors [Mark, Jay]
* git branch management
+
* Investigate CodeMirror modes support for language highlighting within the editor [Mark]
* commands available in more places, esp editor [https://bugs.eclipse.org/bugs/show_bug.cgi?id=361003 bug 361003]
+
* CSSLint a regular part of Orion [https://dev.eclipse.org/ipzilla/show_bug.cgi?id=5785 CQ 5785] [John]
* Support patch workflow in Git {{bug|361425}}
+
* Validators for CSS, HTML, JavaScript [John, Mark]
 
+
* Initial Browser debug communication and injection to handle console commands from Orion [Grant, Mike]
== 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 [http://pixlr.com/ Pixlr] or [http://www.picnik.com/ Picnik] {{bug|362067}}
+
* Non-static multi-server integration - more than one server doing long-running work. E.g., compile server separate from file server.
+
 
+
== 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
+
 
+
== New function ==
+
New function that is important (maybe a more specific theme should be identified here...)
+
* What work could begin on a Debug platform or a DOM inspector
+
* CSS tooling (CSS3 aware) -  outliner, content assist, etc
+
* support querying for running progress tasks {{bug|344148}}
+
* Git submodule support {{bug|361909}}
+
* Creating a patch {{bug|361425}}
+
* Accepting a text patch into your Workspace {{bug|361425}}
+
* 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 tasks
+
* Support for multiple tasks {{bug|344012}}
+
* Wildcard search
+
* Global search and replace
+
* [http://www.w3.org/TR/offline-webapps/ Offline support], not sure if this is something for .4
+
* customize/macros capability, make greasemonkey scripts and chrome extensions first class citizens in Orion
+
 
+
== 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
+
  
== Evangelization ==
+
== Platform ==
* significant amount of time should be a requirement on team members
+
* Update our 3rd party libraries including DoJo, RequireJS, JSDoc [Simon, John]
* Working on more integration with other projects
+
* Closer alignment with OSGi services [Simon]
* Getting integrations going without necessary buy-in up front
+
* Authentication integration with service registry [Simon, Gosia]
* Example of a real multi-server application. An example with non-static content.  Server to server site crossing
+
* Examine use of require.js and module granularity [Simon]
* Describe the problems we are having and look for feedback
+
* Investigate approaches to localization support [Simon]
* New landing page
+
* Long running tasks {{bug|344148}}  {{bug|344012}} [Susan, Gosia]
* Revamping the OrionHub experience
+
* Search and replace improvements  {{bug|359739}} {{bug|344200}} {{bug|334709}} {{bug|362827}} [Libing, John]
* Additional file systems such as S3 or Dropbox
+
* User access to preferences [Gosia]
 +
* There is also the Editor items under consideration here [http://wiki.eclipse.org/Orion/EditorWishList Editor Items for 0.4]
  
== Localization ==
+
== User Experience ==
* Need to validate what components need to be localized
+
* User interface refresh and improved initial user experience [Susan, Ken]
* What are the available techniques and patterns we can use
+
* Improve Mobile UI experience {{bug|359875}} {{bug|339427}} {{bug|340615}} {{bug|359567}} [Susan, Silenio]
 +
* Support patch workflow and improve branch management in Git {{bug|361425}}  {{bug|361909}}  {{bug|360472}}  {{bug|345397}}  {{bug|347066}} {{bug|357787}}{{bug|359273}} (blocked by {{bug|309355}} in JGit) [Tomasz]
 +
* Investigate approaches for deeper cross-site integration (delegated UI / bookmarklets) [Simon, Susan, Szymon]
 +
* Identifying common tasks and providing better access to contextual movement {{bug|361003}} {{bug|359277}}{{bug|349531}} {{bug|360986}} {{bug|360988}} [Susan, Anton, Libing]
 +
* Semantic URLs with relevant contextual information for the task {{bug|358769}} {{bug|358767}} {{bug|342739}} [Susan, Simon]
  
== Build and Test Infrastructure ==
+
== Infrastructure ==
* Need better build capabilities including Hudson launches for build and deploy {{bug|348575}}
+
* Improve build capabilities to remove reliance on shell access  {{bug|348575}} [John]
* Test automation and coverage. ([http://siliconforks.com/jscoverage/ JSCoverage] to analyze JS?, [http://www.eclemma.org/ EclEmma] for Java)
+
* Improve the test coverage and capabilities {{bug|362805}} [Simon]
* Increased test cases across the board
+

Latest revision as of 11:35, 21 November 2011

Introduction

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

See the official plan document 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

  • Need a parser that can handle errors [Mark, Jay]
  • Investigate CodeMirror modes support for language highlighting within the editor [Mark]
  • CSSLint a regular part of Orion CQ 5785 [John]
  • Validators for CSS, HTML, JavaScript [John, Mark]
  • Initial Browser debug communication and injection to handle console commands from Orion [Grant, Mike]

Platform

  • Update our 3rd party libraries including DoJo, RequireJS, JSDoc [Simon, John]
  • Closer alignment with OSGi services [Simon]
  • Authentication integration with service registry [Simon, Gosia]
  • Examine use of require.js and module granularity [Simon]
  • Investigate approaches to localization support [Simon]
  • Long running tasks bug 344148 bug 344012 [Susan, Gosia]
  • Search and replace improvements bug 359739 bug 344200 bug 334709 bug 362827 [Libing, John]
  • User access to preferences [Gosia]
  • There is also the Editor items under consideration here Editor Items for 0.4

User Experience

Infrastructure

  • Improve build capabilities to remove reliance on shell access bug 348575 [John]
  • Improve the test coverage and capabilities bug 362805 [Simon]

Back to the top