Confirmed users
210
edits
Webtools/DXR User Research: Difference between revisions
Jump to navigation
Jump to search
→Questions Asked
Espressive (talk | contribs) |
Espressive (talk | contribs) |
||
| Line 25: | Line 25: | ||
* Exploring code that I don't know well; finding all uses of code that I am modifying. | * Exploring code that I don't know well; finding all uses of code that I am modifying. | ||
=== Do you ever use MXR or do you exclusively use DXR? === | |||
* MXR with alarming frequency, DXR every time I hear about new features | |||
=== Which aspects of the service do you currently love and why? === | |||
* I used to love the ability to perform searches like derived:nsILoadContext, but that appears to be broken in both DAO and DMO. I love the incremental searches for DAO, the ability to limit searches based on the current results, and the speed with which results and source files appear. | |||
=== Which aspects of the service do you currently dislike and why? === | |||
* "- It's slower than MXR; enough so to be frustrating in a papercut sort of way. This seems to be partially a client-end thing - i.e. it's not necessarily the network, just that it's doing too much on my end. | |||
- The RegExp field is broken on allizom (it keeps inserting # all over the place, and... is that running client-side? because it just went slow-script-dialog on me, not to mention hanging Firefox...) | |||
- It doesn't understand XPIDL, JS, Python, Perl, ... | |||
- In fact, Python just errors out (it's probably trying to run it as CGI) | |||
- Clicking the ""search"" button near the textboxes can often complain about no tree (i.e. it doesn't pick up the tree= query string in the URL)" | |||
* The lack of MXR parity; the completely unintelligible results for any non-plaintext search on DAO; the lack of example searches on DAO; | |||
=== Is there anything in MXR that you miss in the DXR service? === | |||
* "- Tree-switching (though with the current pace there's too many trees people might be interested it, sigh) | |||
- Speed. MXR is a heck of lot faster to load (due to simpler UI). It also does well at streaming results in. | |||
- On identifier searches, it lists definitions (things in *.h) first. I probably care about uses a lot less than what's available. (It would be nice to suppress forward declarations to later, though) | |||
- It understands (somewhat) XPIDL files (*.idl) better; it actually seems to parse it somewhat. | |||
- It has a single field for identifiers, so I don't have to think about whether I'm looking for a function, a type, or a macro. (If something is all three, it's probably too complicated) | |||
- MXR does regexp for path: searches." | |||
* JS/IDL/JSM/etc. integration (linked identifiers, searches for GetFoo returning JS entries for foo, and more), case-insensitive results. | |||
=== Any additional comments? === | |||
* "I would like to see the project separated into components. | |||
Compile -> database. | |||
Comments + database -> database | |||
database -> database model | |||
template engines to do whatever you want that use the database model. | |||
database -> model <-> controller <-> view | |||
------ | |||
keys should not be integers, or based on the location in the file. | |||
If I associate links with code objects, the links will be destroyed on every compile. | |||
Database of code should be able to recreate the raw source code of definitions. minus #def out sections. | |||
If this is all done then this tool would be much more attractive than swig / doxygen" | |||
* "I think I'd actually want to get this hooked into the address bar so I can have search suggestions as I go... That would be nice, but probably outside your immediate scope ;) (So I can start typing ""dxr nsIDOMWin"" and have it display ""dxr nsIDOMWindowUtils"" as one of the suggestions, even if I've never looked at it before) Oh, did I mention speed? ;)" | |||
* The lack of JS integration severely hinders my ability to use DXR on more than a trial basis. | |||