On 02/10/13 21:33 , Erik Rose wrote:
What features do you most use in MXR and DXR?
Over in the recently renamed Web Engineering group, we're working hard to
retire MXR. It hasn't been maintained for a long time, and there's a lot of
duplication between it and DXR, which rests upon a more modern foundation and
has been developing like crazy. However, there are some holes we need to fill
before we can expect you to make a Big Switch. An obvious one is indexing more
trees: comm-central, aurora, etc. And we certainly have some bothersome UI bugs
to squash. But I'd like to hear from you, the actual users, so it's not just me
and Taras guessing at priorities.
What keeps you off DXR? (What are the MXR things you use constantly? Or the
things which are seldom-used but vital?)
If you're already using DXR as part of your workflow, what could it do to make
your work more fun?
Feel free to reply here, or attach a comment to this blog post, which talks
about some of the things we've done recently and are considering for the future:
https://blog.mozilla.org/webdev/2013/09/30/dxr-gets-faster-hardware-vcs-integration-and-snazzier-indexing/
We'll use your input to build our priorities for Q4, so wish away!
Cheers,
Erik
Something that's been bothering me about MXR for many years: When I
search for any file of which there is only one copy, like any of the
interface definition files, or the singleton implementations thereof, it
should just open the file. The extra click on the unique search result
is just wasted time.
~ Gijs
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
