Closed pjrinaldi closed 2 years ago
this new method will alleviate a lot of the issues of adding/removing items from the build as i go html report with the id's and the searching modifying html code and html is no easier than a custom viewer or even a folder with files to open and a simple document (maybe html) to navigate the plain text files, but if i can get away from a web browser dependence, taht woudl be great.
think i've commented out all the webengine code, rudimentary report viewer and htmlviewer using textengine in place. need to test out how it works with current html set, maybe the lnkfile parser testimage would be a good test of how the replacement htmlviewer performs.
textbrowser is working and looks pretty good, just need to adjust the css for some of it and ensure parts are now working as they were with other html simplifications where needed to remain visually similar.
working on switching from css, class and the prehtml files to a set of css strings which get called as necessary for the "style" attribute
switched registry viewer code to switch class='' to style=''. still need to replace the javascript code everywhere such as in registryviewer from ShowContent() to a link with possible target
todo: continue to replace class='' to style='' everywhere it exists. also need to replace javascript ShowContent() with simple link. the link will open in existing window, so i will need to implement a back/forward button setup in the htmlviewer window.
then once the conversions are done, i will need to remove the html files from the qrc resource file and i will need to figure out where to add reporting in the newcase functionality.
I will also want to test out the new "reportviewer" paradigm for viewing the html, which "should" alleviate all the HTML id='' trickery to add/remove files from the report.
working on getting evidence content into the preview report viewer. once i get the html worked out, i will attempt to implement the same content in the reportviewer and see which is better/easier to implement.
html reporting is working. need to attempt to populate the report viewer and see how it goes..
reporting seems to go well. will move the "reportviewer out to another ticket and possible enhancement.
I want to move away from using the webengine html viewer, it is a huge chunk of code and contains way more than i want or need, will either move to a rich textedit view as read only with a subset of html, or come up with my own report viewer widget/application that can load a report and parse it into whatever gui elements such as lists for tags, evidence items, and the respective viewers, etc... maybe rely more on plain text, richtext.html or some combination