What I meant was that the fact that the Search File Contents *can* be used for searching by file name at all is a happy, unintended consequence of putting in a null content string. It wasn't *intended* to be a filename search feature, and the fact that it can be used as one is strictly happenstance... and shouldn't be really used as such, probably.
Which means that there isn't really *any* proper file/folder/package name positive-filtering feature in the Package Explorer, only subtractive filtering. Beezarre.
Optimally, I'd like to see the filtering setup dialog allow for a simple exclude/include toggle. There's really not enough room in the PE pane title (or toolbar) from how I've seen most people have it set up to add a ready text field for positive name filtering, unfortunately. (Think iTunes search field. Type a sub-string, instant results. Clear to resume full view.) In any case, the point is to get the view culled down to just those elements of interest, *with* the folders leading down to them. The results returned by Search, for instance, are alphabetized by filename, not sorted by path - that surprised me. If I'm going code diving, I'm probably *much* more interested in how the pieces hang together semantically in the packaging structure than I am by what the file is named. The file name is the lowest level of organizational detail prior to hitting the code, but the packaging gives me the conceptual placement in the project. At the very least, I would have left-aligned the paths with padding after the filenames for easy visual comparison, or added a 'sort by path' option.
![[personal profile]](https://www.dreamwidth.org/img/silk/identity/user.png){kind=small}
(no subject)
Date: 2006-12-16 04:19 am (UTC)Which means that there isn't really *any* proper file/folder/package name positive-filtering feature in the Package Explorer, only subtractive filtering. Beezarre.
Optimally, I'd like to see the filtering setup dialog allow for a simple exclude/include toggle. There's really not enough room in the PE pane title (or toolbar) from how I've seen most people have it set up to add a ready text field for positive name filtering, unfortunately. (Think iTunes search field. Type a sub-string, instant results. Clear to resume full view.) In any case, the point is to get the view culled down to just those elements of interest, *with* the folders leading down to them. The results returned by Search, for instance, are alphabetized by filename, not sorted by path - that surprised me. If I'm going code diving, I'm probably *much* more interested in how the pieces hang together semantically in the packaging structure than I am by what the file is named. The file name is the lowest level of organizational detail prior to hitting the code, but the packaging gives me the conceptual placement in the project. At the very least, I would have left-aligned the paths with padding after the filenames for easy visual comparison, or added a 'sort by path' option.