|author||elijahe <email@example.com>||Thu Jan 09 16:25:12 2014 -0500|
|committer||Mark Macdonald <firstname.lastname@example.org>||Thu Jan 09 16:51:01 2014 -0500|
Bug 425227 - Orion Editor Content Assist Improvements - Added support for HOME and END keys - Added handling for cases when first proposal in list is unselectable, e.g. a section title such as "Templates" - Removed duplication of state between the ContentAssistMode and ContentAssistWidget. "proposals" and "selectedIndex" now only exist in ContentAssistMode. - Refactored iteration through popup items and improved performance of item selection. - Added support for making a visual distinction between name of proposal and its description. - If there's only one proposal apply it immediately instead of showing popup --Signed-off-by: Elijah El-Haddad <email@example.com>
The goal of Orion is to build developer tooling that works in the browser, at web scale. The vision behind Orion is to move software development to the web as a web experience, by enabling open tool integration through HTTP and REST, JSON, OAuth, OpenID, and others. The idea is to exploit internet design principles throughout, instead of trying to bring existing desktop IDE concepts to the browser. See the Orion wiki for more information about Orion.
Orion source code is available in an Eclipse Git repository, and there is also a mirror on GitHub. For complete details on getting the source and getting setup to develop Orion, see the Orion wiki.
Bug reports and patches are welcome in bugzilla.