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
(New function)
Line 6: Line 6:
 
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.
+
* git branch management
+
* commands available in more places, esp editor [https://bugs.eclipse.org/bugs/show_bug.cgi?id=361003 bug 361003]
+
* Support patch workflow in Git {{bug|361425}}
+
* Better usability on 403 pages {{bug|337038}}
+
 
+
== 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.
+
* semantic URLs that open UIs in some chosen state {{bug|358769}}
+
 
+
== 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}}
+
* Make Git Log more general to show changes between two any refs (e.g. two local branches before merging them)
+
* Add Git Commit page showing commit details {{bug|360472}}
+
* Accepting a text patch into your Workspace {{bug|361425}}
+
* Show graph for Git log {{bug|345397}}
+
* Support for Git Stash {{bug|359273}}, blocked by {{bug|309355}} in JGit
+
* "Forgot password" or "Reset password" + communication with users via mails {{bug|347066}} {{bug|357787}}
+
* 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 {{bug|359739}}
+
* Global search and replace {{bug|344200}}
+
* Scoped search (both global and local) {{bug|334709}}
+
* Support for comparing any two files (client side unified diff)
+
* [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
+
 
+
== Debug Framework ==
+
* Investigate framework and tooling required to provide close integration with browser debugging
+
* Look at remote console
+
 
+
== Language Tooling ==
+
* JavaScript Tooling
+
* Enablement for other languages
+
 
* Need a parser that can handle errors
 
* Need a parser that can handle errors
** Error reporting
+
* Investigate CodeMirror modes support for language highlighting within the editor
** Incremental problems vs. failing on first
+
* CSSLint a regular part of Orion
* refactoring (extract function, inline variable?)
+
* Syntax highlighting needs to be based on our parsing vs. regular expressions
* quickfixes (example is javascript)
+
* Validators for CSS, html, JavaScript
* CSSLint thing a regular part of Orion
+
* Initial Browser debug communication and injection to handle console commands from 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
* Working on more integration with other projects
+
* Closer alignment with OSGi services
* Getting integrations going without necessary buy-in up front
+
* Authentication integration with service registry
* 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
* Describe the problems we are having and look for feedback
+
* Localization support
* New landing page
+
* Long running tasks {{bug|344148}}  {{bug|344012}}
* Revamping the OrionHub experience
+
* Search and replace improvements  {{bug|359739}} {{bug|344200}} {{bug|334709}}
* Additional file systems such as S3 or Dropbox
+
* User access to preferences
  
== Localization ==
+
== User Experience ==
* Need to validate what components need to be localized
+
* Improve Mobile UI experience
* What are the available techniques and patterns we can use
+
* 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}}
  
== 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}}
* 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
* Increased test cases across the board
+

Revision as of 10:27, 31 October 2011

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

User Experience

Infrastructure

  • Improve build capabilities to remove reliance on shell access bug 348575
  • Improve the test coverage and capabilities

Back to the top