Confirmed users
574
edits
DXR Roadmap: Difference between revisions
Jump to navigation
Jump to search
m
→Top of the Heap
(→Indexing: Maybe dynamic markup generation is a priority-2 feature, since it enables permalinking. Does MXR really have that feature?) |
|||
| Line 10: | Line 10: | ||
** (3) Just typing a filename (or path segment?) without a path: specifier should find files by name or path. [[DXR Result Mixing]] should help with this. | ** (3) Just typing a filename (or path segment?) without a path: specifier should find files by name or path. [[DXR Result Mixing]] should help with this. | ||
*** [Should be solved by ^^] Trying to find files is hard. (Still haven't figured out how to get easily from the main page to Navigator.cpp on dom/base) | *** [Should be solved by ^^] Trying to find files is hard. (Still haven't figured out how to get easily from the main page to Navigator.cpp on dom/base) | ||
*** [Should be solved by ^^] A basic "file:" keyword hint with simple wildcard | *** [Should be solved by ^^] A basic "file:" keyword hint with simple wildcard globbing could do most of it well enough, I think... "file:*.css", "file:nsILogin*", "file:/test*". (We already search for "path" matches as unanchored substrings. We just need to add the globbing. Why this isn't super slow I don't know.) | ||
*** [Should be solved by ^^] As a jump point when I know a filename (eg, "nsILogin", click search, click the particular IDL I wanted). | *** [Should be solved by ^^] As a jump point when I know a filename (eg, "nsILogin", click search, click the particular IDL I wanted). | ||
*** Oddly enough, the direct result finder does search for paths ending in whatever you type, so that's an inconsistency (noticed by jmaher). | *** Oddly enough, the direct result finder does search for paths ending in whatever you type, so that's an inconsistency (noticed by jmaher). | ||