DXR Roadmap: Difference between revisions

Jump to navigation Jump to search
271 bytes removed ,  19 June 2014
Docs are largely done: http://dxr.readthedocs.org/
(→‎Search: Add multi-tree search.)
(Docs are largely done: http://dxr.readthedocs.org/)
Line 3: Line 3:
Here's the next round of improvements we'll do, not necessarily in order. These either make [[DXR]] a lot better for some or a little better for all and are biased toward our goal of being able to retire MXR. These items turn into filed bugs (not necessarily with a 1-to-1 correspondence), and then we do the bugs. When this list gets short, we pull more up from below.
Here's the next round of improvements we'll do, not necessarily in order. These either make [[DXR]] a lot better for some or a little better for all and are biased toward our goal of being able to retire MXR. These items turn into filed bugs (not necessarily with a 1-to-1 correspondence), and then we do the bugs. When this list gets short, we pull more up from below.


* Better docs for the whole system, from configuration to use. Get them to the point where they're true and comprehensive, and then keep them that way in every new commit. This will help attract new contributors (accelerating feature and bug work) and save ops mistakes. Also, find a place to put release notes, preferably accessible from in-product.
* Indexing and search improvements
* Indexing and search improvements
** (1) Move to a line-based search, as proposed in https://github.com/mozilla/dxr/pull/161#issuecomment-25201532.
** (1) Move to a line-based search, as proposed in https://github.com/mozilla/dxr/pull/161#issuecomment-25201532.
Line 84: Line 83:
* (4) Show context around results (with a clickable control? by saying "context:3[lines]" in the query? show the entire statement?)
* (4) Show context around results (with a clickable control? by saying "context:3[lines]" in the query? show the entire statement?)
* (4) Currently, you always get the context menu. But I (erikrose) suspect there is a by-far-most-common case: jumping to a symbol's definition. If we were to map that to a normal click and save the context menu for context-clicks (right-clicks, etc.), it would let people bounce around the codebase faster. It would be great to back up my supposition with some measurements. Risk: This makes the existence of the context menu (and thus a lot of DXR's capabilities) non-obvious.
* (4) Currently, you always get the context menu. But I (erikrose) suspect there is a by-far-most-common case: jumping to a symbol's definition. If we were to map that to a normal click and save the context menu for context-clicks (right-clicks, etc.), it would let people bounce around the codebase faster. It would be great to back up my supposition with some measurements. Risk: This makes the existence of the context menu (and thus a lot of DXR's capabilities) non-obvious.
* (4) Find a place to put release notes, preferably accessible from in-product.


=== Just Bugs ===
=== Just Bugs ===
Confirmed users
574

edits

Navigation menu