kielx / anygrabber Goto Github PK

Found log files should be secured.

1. Create a folder with timestamp and computer name for future searching
2. Copy found log file
3. Generate checksum for the file
4. Save checksum

It would be a good idea to show users how to use application. There could be a button located at the bottom of main screen that opens help in a new window. In that window there could be a similar sidebar and main panel like those in main type of window. Sidebar would contain each topic like 'Getting Logs', 'Browsing Reports' and so on, while the main one will display content of help topic - with images for example

Users should be able to stop a search which is in progress

The searching function is buggy, because if the AnyGrabber folder is located in a particular location, then it will not look inside directories in the same directory. It should avoid searching only in that specific folder named AnyGrabber instead.

User should be able to generate text report and/or .csv report for further usage.

If the file is located at path like D:/file.trace, then the program fails to copy because it cannot resolve the path.

• Create a new frame
• On one side it should have a list of reports
• On the other side it should have reports details - but probably only numerical short details - like '10 IP's' or/and '3 files found'
• On the bottom there should be a button with "Open report"
• Add test to split filename and get dirname with wrong input

It prevents users from switching languages mid-search and having language bugs inside reports.

It would be a good idea to test how app works on log files that contain actual logs, that do not contain any data and at location that contains no data at all.

It might be worth considering the option to grab the whole folder created by anydesk that supposedly includes chat logs

Thanks to this rework, the functions that depend on the output could format it the way that is needed. For example .txt report could include only IP addresses, only dates or both.

At current state the frame gets refreshed each time the button is pressed. It should refresh the state only when the list gets updated.

A button should be displayed on browse reports frame that allows the user to delete a particular report. Confirmation of some kind should be required before deletion.