If we change our design to only add the Custom Artifact to “tag” a file as being Swarmed with one attribute like “Swarmed”. We could leave the abstractFile/artifact at that, and not add more attributes.
We could then add more columns to the sqlite db to keep track of the stages of the polyswarm process and the results from each stage.
We could then add a ContentViewer tab in the bottom right frame that displays the info from the db for a selected file. This would then be able to display anything we want. And we could update the db anytime we want.
With this design, we would never delete any rows form the db. And we would have the background process only checking the status of rows that have not been fully resolved.
If we change our design to only add the Custom Artifact to “tag” a file as being Swarmed with one attribute like “Swarmed”. We could leave the abstractFile/artifact at that, and not add more attributes.
We could then add more columns to the sqlite db to keep track of the stages of the polyswarm process and the results from each stage.
We could then add a ContentViewer tab in the bottom right frame that displays the info from the db for a selected file. This would then be able to display anything we want. And we could update the db anytime we want.
With this design, we would never delete any rows form the db. And we would have the background process only checking the status of rows that have not been fully resolved.