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
(Demonstrate site-crossing workflows)
m (Demonstrate site-crossing workflows)
Line 13: Line 13:
 
== Demonstrate site-crossing workflows ==
 
== 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:
 
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
+
* clone a repo from bugzilla / github
 
* use w3c validators for html in orion
 
* use w3c validators for html in orion
  

Revision as of 05:42, 21 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.

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

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

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

New function

New function that is important (maybe a more specific theme should be identified here...)

  • CSS tooling (CSS3 aware) - outliner, content assist, etc

Platform issues

  • dojo 1.7(.1?)

Back to the top