DXR UI Refresh: Difference between revisions

Jump to navigation Jump to search

DXR UI Refresh (view source)

Revision as of 22:11, 5 October 2013

1,544 bytes removed ,  5 October 2013
m
→‎Please help refactor these.
(→‎Please help refactor these.: Land Erik's chunk)
Line 66: Line 66:
* "One of the neat things with mxr and multiple trees is that when viewing a file on say mozilla-central I can easily switch to the mozilla-aurora version to see how it looks there, this is really useful for figuring out how a bug affects different branches. Bonus points might include a file diff between the trees
* "One of the neat things with mxr and multiple trees is that when viewing a file on say mozilla-central I can easily switch to the mozilla-aurora version to see how it looks there, this is really useful for figuring out how a bug affects different branches. Bonus points might include a file diff between the trees
* In the new UI, keep a text-only representation or some other way to be usable from custom search plugins or URL-bar keywords.
* In the new UI, keep a text-only representation or some other way to be usable from custom search plugins or URL-bar keywords.
* Let us structurally query stuff that gets #ifdef'd out on x86, like ARM stuff.
* Direct results: some love them, some hate them (because they just want to see the file pathname (don't we show that with the file? Is it bothersome because it's slow to load?)
* Search for substrings or patterns of file paths. Even just typing a filename (or path segment?) without a file: specifier should find files by name or path.
* Just plain old bugs:
** I find the call graph information to be wrong some of the time, I have never been able to tell why.  See this query for example: <http://dxr.mozilla.org/mozilla-central/search?q=%2Bcallers%3A%22mozilla%3A%3AAudioNodeStream%3A%3ASetDoubleParameter%28uint32_t%2C+double%29%22>.  Do you have any idea what the source of these problems is, and if yes, is that on track to get fixed?
* Count of search results, so we can use DXR to gather continuous metrics
* Stop differentiating between macros, functions, consts, etc.: just find me an *anything* called "fred". People coming up the booth were confused that they had to know the kind of the target.
* Show context around results (after a click? by saying "context:3[lines]" in the query?)
* More obviously indicate that the search results are out of date. Dim them?
* Be able to refer to specific revisions of code somehow, so links don't rot.
* Be able to navigate blame history better, stepping back and back in time until we find the change we were looking for.
* Better ranking: if you type an exact identifier name, put the definition at the top.
* Limiting searches to a particular file type. (eg, "image" in CSS files)
* Limiting searches to a particular file type. (eg, "image" in CSS files)
* As a jump point when I know a filename (eg, "nsILogin", click search, click the particular IDL I wanted).
* As a jump point when I know a filename (eg, "nsILogin", click search, click the particular IDL I wanted).
Espressive
Confirmed users
210

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/722833"

Navigation menu