rickysarraf / foxreplace

Automatically exported from code.google.com/p/foxreplace
0 stars 0 forks source link

summary or log file (i.e. smth like diff) #69

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
What steps will reproduce the problem?
1. n/a
2.
3.

What is the expected output? What do you see instead?
n/a

What version of the product are you using? On what operating system?
windows 7

Please provide any additional information below.
I have a useful idea. foxreplace has many professional users who want to be 
sure about the tasks implemented from foxreplace. So I have in my mind the 
following idea:

1) in the preferences window there should be a tick box if someone wants to see 
a dialog box with the replacements and some results

2) then after the replacements, a dialog box with which words have been 
replaced and with which word.
i.e.
The following actions performed:
from word ert to word 564 match CASE:
2 times
flert -> fl564
klertinos -> k564inos

-------- or something similar. That's only because we have to be sure about the 
changes

best regards

Original issue reported on code.google.com by ebrac...@gmail.com on 22 Jun 2012 at 5:04

GoogleCodeExporter commented 9 years ago

Original comment by marc.r...@gmail.com on 22 Jun 2012 at 5:32

GoogleCodeExporter commented 9 years ago
I was hoping for something similar. I would like to see an option to "view 
source" where the 'source' is the replaced version.

For simply debugging, to find errors I made or bugs in Foxreplace

Original comment by mpheyse%...@gtempaccount.com on 13 Jul 2012 at 2:03

GoogleCodeExporter commented 9 years ago
The source of the replaced version can already be seen in the inspector. I 
don't know if it would be possible to view it on "view source" window, or if it 
would be appropriate.

Original comment by marc.r...@gmail.com on 13 Jul 2012 at 3:24

GoogleCodeExporter commented 9 years ago
I don't know what "the inspector" is but FireBug  add-on does let you see the 
active DOM structure as a imploded tree view, which works but is a bit 
cumbersome. 

Original comment by mpheyse%...@gtempaccount.com on 15 Jul 2012 at 3:52

GoogleCodeExporter commented 9 years ago
The inspector is more or less like the Firebug DOM view but built-in in Firefox 
since version 10 or so (now I know that you have v3.6).

Original comment by marc.r...@gmail.com on 16 Jul 2012 at 4:00