11
edits
Labs/Ubiquity/0.2 Roadmap Proposals: Difference between revisions
Labs/Ubiquity/0.2 Roadmap Proposals (view source)
Revision as of 23:05, 12 November 2008
, 12 November 2008→Linguistics
| (3 intermediate revisions by 3 users not shown) | |||
| Line 14: | Line 14: | ||
* Creating a set of command-naming guidelines, and implementing them consistently in first-party commands, to encourage consistency across all commands, which will make the system as a whole easier to learn and use. | * Creating a set of command-naming guidelines, and implementing them consistently in first-party commands, to encourage consistency across all commands, which will make the system as a whole easier to learn and use. | ||
* Standing on the shoulders of giants, third-party frameworks? Evaluation of these tools? | |||
== User Interface == | == User Interface == | ||
| Line 34: | Line 36: | ||
* Making Ubiquity's UI not only pluggable but streamable too, allowing new usability features to be streamed in rather than manually updated. | * Making Ubiquity's UI not only pluggable but streamable too, allowing new usability features to be streamed in rather than manually updated. | ||
:* Note that adding streaming built-in command feed functionality in 0.1.2 took quite a bit longer than we thought; there's a decent chance that this could be nontrivial to implement too. | :* Note that adding streaming built-in command feed functionality in 0.1.2 took quite a bit longer than we thought; there's a decent chance that this could be nontrivial to implement too. | ||
* Statistical data gathering | |||
:* Combined with the streaming UI this allows us to quickly and cheaply test changes on large samples of users as pioneered most powerfully by Netflix but embraced by every major web company. | |||
:* Understand feature usage, errors, and stickiness | |||
:* Triage context menu versus command line priority | |||
== Community == | == Community == | ||
| Line 71: | Line 77: | ||
* Due to the security dangers of giving chrome privileges to arbitrary javascript, the functionality that gets into Firefox 3.2 should '''not''' include subscription to third-party commands. | * Due to the security dangers of giving chrome privileges to arbitrary javascript, the functionality that gets into Firefox 3.2 should '''not''' include subscription to third-party commands. | ||
== Inter-process Sandboxed Security == | |||
::'''Motivation:''' Exploring the execution of end-user code in a separate process using a technology like the recently open-sourced [http://en.wikipedia.org/wiki/GreenBorder GreenBorder] can help protect end-user machines and also serve as a useful "guinea pig" for applying a similar kind of mechanism to Firefox. | |||
* GreenBorder's source code appears to be [http://src.chromium.org/viewvc/chrome/trunk/src/sandbox/src/pe_image.h?revision=1287&view=markup here]. Understandably, it seems to be tightly coupled to the Windows operating system. | |||
* Using a separate process means we'd probably have to implement some kind of robust, cross-platform IPC mechanism; there may already exist code in Chromium to help us do this. Dan Mosedale also knows of some work that was done a few years ago to help Thunderbird and Firefox exchange information better; the code never ended up being used, but it's still in the trunk. | |||
== Stabilization of Current Feature Set == | == Stabilization of Current Feature Set == | ||
| Line 81: | Line 95: | ||
* Making debugging easier | * Making debugging easier | ||
* Getting Ubiquity to the point that it's secure and stable enough to be featured on AMO | * Getting Ubiquity to the point that it's secure and stable enough to be featured on AMO | ||
== Group Documentation == | |||
* Adoption (goals) | |||