C++ front end required for CPP console application Windows 7 64 bit

I have a CPP 64 bit console application that takes two user selectable files and compares them both, looking for similarities (i.e. exact text matches of user selectable length), i.e. FILE A vs FILE B I need a front end put on this application that allows the selection of an entire folder of files and compares them against another folder full of files, i.e. cross references perhaps 100 files again 100 other files USING THE EXISTING CODE THAT ALREADY WORKS - all you will be doing is putting a graphical front end on it. I should be able to select all the SOURCE files, all the COMPARISON files and an output folder for the results. Also - I want to be able to VIEW all of the results in a 'summary' format, i.e. all file comparisons are aggregated as a graph that shows peaks or or as an excel sheet showing amalgamated results etc rather than having to trawl through each results output file one at a time. ## Deliverables Have a look at the console application [login to view URL] It is run as follows: [login to view URL] [login to view URL] [login to view URL] 12 [login to view URL] A = original file B = suspected copy 12 = number of characters to compare for, i.e. string length [login to view URL] = File that generates output. I need you to automate the whole FILE A / FILE B thing on a per folder basis, i.e. PASS 1 ===== FILEA_ORIGINAL vs FILE_A_COPY FILEA_ORIGINAL vs FILE_B_COPY FILEA_ORIGINAL vs FILE_C_COPY ..... FILEA_ORIGINAL vs FILE_Z_COPY AGGREGATE ALL RESULTS FOR FILEA_ORIGINAL IN A WAY THAT IS EASY TO READ ALL THE RESULTS GRAPHICALLY PASS 2 ===== FILEB_ORIGINAL vs FILE_A_COPY FILEB_ORIGINAL vs FILE_B_COPY FILEB_ORIGINAL vs FILE_C_COPY ..... FILEB_ORIGINAL vs FILE_Z_COPY NOW AGGREGATE ALL RESULTS FOR FILEB_ORIGINAL IN A WAY THAT IS EASY TO READ ALL THE RESULTS GRAPHICALLY FILEB_ORIGINAL vs FILE_Z_COPY If you see opportunities to improve the underlying code (i.e. multi threading etc) bonuses will be awarded. Please respond stating how you will approach this, as I belive it will not be that difficult but perhaps the aggregation of all the results from the OUTPUT files might prove difficult. It would probably be better if there was some sort of plan that held output results in memory and output them all in one go on a "per file' basis rather than writing to disk for every test, i.e. FILE_A_ORIGINAL when compared to a folder that contained (for example) 1000 files will run really slowly if all 1000 OUTPUT files are generated separately - rather they are aggregated and created in one go. Try the code out for yourself to see the contents of the OUTPUT file. The final version you submit must also have some onscreen radiobuttons / checkboxes to ignore certain matches and to be able to sort and filter the results.