Has potential Rated 2 out of 5 stars
I agree with gd2shoe's review.... this would be great if it could do regex search on the page, integrated into the search bar that comes up with Ctrl+F. Another cool feature might be regex syntax highlighting like http://regexpal.com/ does.This review is for a previous version of the add-on (126.96.36.199).
way chill!, but a button please? Rated 4 out of 5 stars
this is an awesome tool, wtg! &huge thnx. there's only one thing i could ask. i know i'm a ditz &space and sometimes, okay more than sometimes, i even forget its there. i live through my 'art toolbar' and a tool bar button would make this a total must have extension. it is now, with the improvements already requested. with those and i button i'd have to blog about. its this or vi's search&replace; an awesome extension all the same! a must have for any web developer!This review is for a previous version of the add-on (188.8.131.52).
Almost what I need Rated 3 out of 5 stars
Good work, this extension could blossom into something wonderful. I would love to be able to search a web page by regx. As this extension stands, I can copy the contents of the page into the tester. The problem with this is that the result box does not scroll.
If a scroll box is added there, this extension will help me tremendously. Ideally (some later version perhaps) being able to search the page itself from the search bar (ctrl+f, perhaps a check box) would be absolutely awesome.
Thanx ;) Rated 5 out of 5 stars
A regex editor that actually works! Rated 4 out of 5 stars
A very nice extension.
Only problem I can see is that there is no way to save a regex once you've built it.
1) make the 'expression' text box multi-line, so you can split complex ones down for readability
2) option to test on only a highlighted portion - i.e. if a new bit of text in the middle of the 'search text' entry makes the regex fail, being able to test the first part of the regex only by highlighting it and clicking 'test'. Otherwise you have to strip back the latter part of the regex to find where the problem is, and that gets a bit tedious.
3) the 'result' box needs a little work - doing \1\2\3 type replacements doesn't show the result properly.