Confirmed users
210
edits
DXR UI Refresh: Difference between revisions
Jump to navigation
Jump to search
m
→Please help refactor these.
(comments from smaug) |
Espressive (talk | contribs) |
||
| Line 103: | Line 103: | ||
* "cycleCollection" on the right side may or may not do something useful. In most cases it just ignores all the stuff, so it might be better to not have it at all. | * "cycleCollection" on the right side may or may not do something useful. In most cases it just ignores all the stuff, so it might be better to not have it at all. | ||
* How to mark certain range of code on particular revision? | * How to mark certain range of code on particular revision? | ||
==WIP== | |||
Search | |||
------- | |||
* Let us structurally query stuff that gets #ifdef'd out on x86, like ARM stuff. | |||
* Limiting searches to a particular file type. (eg, "image" in CSS files) | |||
* 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. | |||
* 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. | |||
IU/UX | |||
------ | |||
* More obviously indicate that the search results are out of date. Dim them? | |||
* Show context around results (after a click? by saying "context:3[lines]" in the query?) | |||
* Be able to refer to specific revisions of code somehow, so links don't rot. | |||
* Count of search results, so we can use DXR to gather continuous metrics | |||
* 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?) | |||
* 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? | |||
Results | |||
-------- | |||
* Better ranking: if you type an exact identifier name, put the definition at the top. | |||
Blame | |||
------ | |||
* Be able to navigate blame history better, stepping back and back in time until we find the change we were looking for. | |||
== Drill-Down Advanced Search: A Dead End? == | == Drill-Down Advanced Search: A Dead End? == | ||