{"id":3700,"date":"2014-02-07T11:32:33","date_gmt":"2014-02-07T19:32:33","guid":{"rendered":"http:\/\/blog.mozilla.org\/webdev\/?p=3700"},"modified":"2014-02-07T23:06:11","modified_gmt":"2014-02-08T07:06:11","slug":"dxr-gets-a-huge-ui-refresh","status":"publish","type":"post","link":"https:\/\/blog.mozilla.org\/webdev\/2014\/02\/07\/dxr-gets-a-huge-ui-refresh\/","title":{"rendered":"DXR Gets A Huge UI Refresh"},"content":{"rendered":"

After months of hard work by talented Mozillians, both paid and volunteer, DXR’s UI overhaul branch has hit production<\/a>! With more efficient workflows, support for multiple trees, and improvements in discoverability, it makes searching Mozilla’s codebases more fun and takes a big step toward the retirement of legacy tools.<\/p>\n

What’s new?<\/h3>\n

Improved flow.<\/strong> The old design forced you into a choice upfront about whether you’d be browsing or searching. That splash screen is gone, replaced with useful information: the top level of the source tree.<\/p>\n

\"The<\/a><\/p>\n

If you want to browse, browse; search, search. In addition, multi-tree support is polished and proven, and new trees are coming soon. Finally, breadcrumbs are integrated more smoothly into the workflow; it will soon be a one-click matter to limit search to the folder you’re browsing.<\/p>\n

Filters upfront.<\/strong> We now expose and document all 27 search filters in a ubiquitous drop-down menu.<\/p>\n

\"DXR's<\/a><\/p>\n

Previously, we showed only about 6, and even those were available only via the Advanced Search panel, which didn’t appear until you had already entered a search and hit Return\u2014search-as-you-type didn’t cut it. Take a look: DXR knows some tricks you weren’t aware of.<\/p>\n

Real parsing.<\/strong> There’s an honest-to-goodness query parser now! You can express quotation marks without doing backflips, and the quoting behavior of regexes is unified with that of the other filters. Any filter’s argument can be quoted with ether single and double quotes, and, in case you need both at once, they can be backslash-escaped. For example…<\/p>\n