Please read http://getfirebug.com/wiki/index.php/I_am_missing_a_feature_in_Firebug! first.
To develop an enhancement we need
* a DETAILED DESCRIPTION of how you imagine the feature * a TEST CASE (no matter how trivial)
What should be implemented/improved?
While doing development using firebug, we often have many javascript source files to search through in order to find the one or two that we'd like to inspect/debug. There is currently a basic search on filenames, but often that's not enough since we have many files with the same or similar filenames (we're using Extjs framework). What would make development significantly faster is to have some sort of fuzzy-search that could search on file names, but also file paths (e.g. if we want to find a Base.js filename, but that filename exists in many places, we could search the path as well, "OpenLayers/Base.js".) This would be similar to Textmate's Command-T, Vim's FuzzyFinder, emacs Ido, etc.
Test Case:
consider just 3 script files:
/Base.js /Ext/Base.js /OpenLayers/Base.js
- searching for Base.js returns 3 results
- searching for OpenLayers returns 1 result
- searching for OpenLayers/Base.js returns 1 result
Cheers!
Make sure you have the latest version of Firebug (http://getfirebug.com/releases/firebug/). Browser version: Operating system:
Comment #1
Posted on Aug 24, 2012 by Helpful Wombat(No comment was entered for this change.)
Comment #2
Posted on Aug 24, 2012 by Helpful WombatDone in https://github.com/firebug/firebug/commit/b518e5b4bffe2eea9786a8470299e0ecd51565f8.
Sebastian
Comment #3
Posted on Aug 24, 2012 by Happy ElephantThat was fast - thanks! One of the things I just thought of is that developers may want preference given to filenames still. So a slightly more advanced search might not just do indexOf on whole file path, but score the match based off of whether the match occurred in the last piece of the exploded path
e.g.:
consider 5 script files:
/Ext/Base.js /Ext/Foo.js /Ext/Bar.js /ExtFull.js /ExtMin.js
- someone searching for "Ext" might want to see ExtFull.js and ExtMin.js at the top of the results, above the long list of files within the Ext directory that also match the file path search
Just a thought. The simple fix will work well for us. I imagine that testing out the full path search change should highlight whether the file path search gets in the way of someone trying to do filename search.
Thanks again
Comment #4
Posted on Aug 28, 2012 by Helpful WombatGood point. Though I think that's a separate thing, so I created issue 5874 to cover that.
Sebastian
Comment #5
Posted on Aug 28, 2012 by Helpful WombatI imagine that testing out the full path search change should highlight whether the > file path search gets in the way of someone trying to do filename search. We could also allow a regexp search. Though I'd prefer if you put this into a new issue if you think it's needed.
I changed the summary of this issue to reflect the changes done.
Sebastian
Comment #6
Posted on Sep 13, 2012 by Massive WombatThis issue has been fixed in Firebug 1.11.0a3 https://getfirebug.com/releases/firebug/1.11/firebug-1.11.0a3.xpi
Please try it and let us know whether it works for you.
Thanks for the help! Honza
Comment #7
Posted on Sep 14, 2012 by Happy ElephantThis is great - thanks so much! I'll let you know if I think of anything else related to this, but for now, this is exactly what I was looking for. Thanks again for your hard work
Comment #8
Posted on Sep 14, 2012 by Helpful WombatGreat! Thanks for the verification.
Sebastian
Status: Verified
Labels:
Type-Enhancement
script
Test-case-available
FBTest-wanted
fixed-1.11-a3