Autopsy  4.14.0
Graphical digital forensics platform for The Sleuth Kit and other tools.
Public Member Functions | List of all members
org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer Interface Reference

Inherited by org.sleuthkit.autopsy.centralrepository.contentviewer.DataContentViewerOtherCases, org.sleuthkit.autopsy.contentviewers.AnnotationsContentViewer, org.sleuthkit.autopsy.contentviewers.contextviewer.ContextViewer, org.sleuthkit.autopsy.contentviewers.FileViewer, org.sleuthkit.autopsy.contentviewers.MessageContentViewer, org.sleuthkit.autopsy.contentviewers.Metadata, org.sleuthkit.autopsy.contentviewers.textcontentviewer.TextContentViewer, org.sleuthkit.autopsy.corecomponents.DataContentViewerArtifact, org.sleuthkit.autopsy.corecomponents.DataContentViewerHex, and org.sleuthkit.autopsy.examples.SampleContentViewer.

Public Member Functions

DataContentViewer createInstance ()
Component getComponent ()
String getTitle ()
String getToolTip ()
int isPreferred (Node node)
boolean isSupported (Node node)
void resetComponent ()
void setNode (Node selectedNode)

Detailed Description

Interface that DataContentViewer modules must implement. These modules analyze an individual file that the user has selected and display results in some form of JPanel. We find it easiest to use the NetBeans IDE to first make a "JPanel Form" class and then have it implement DataContentViewer. This allows you to easily use the UI builder for the layout.

DataContentViewer panels should handle their own vertical scrolling, the horizontal scrolling when under their panel's preferred size will be handled by the DataContentPanel which contains them.

Definition at line 35 of file

Member Function Documentation

DataContentViewer org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer.createInstance ( )
Component org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer.getComponent ( )
String org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer.getTitle ( )
String org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer.getToolTip ( )
int org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer.isPreferred ( Node  node)

Checks whether the given viewer is preferred for the Node. This is a bit subjective, but the idea is that Autopsy wants to display the most relevant tab. The more generic the viewer, the lower the return value should be. This will only be called on viewers that support the given node (i.e., isSupported() has already returned true).

The following are some examples of the current levels in use. If the selected node is an artifact, the level may be determined by both the artifact and its associated file.

Level 7 - Based on the artifact, if any, in the selected node and specific to an artifact type or types. Current content viewers that can return level 7 are the Messages tab (only supported for email and SMS) and the Text tab when the selected node is a Keyword Search hit.

Level 6 - Based on the artifact, if any, in the selected node but not restricted to particular types. The current content viewer that can return level 6 is the Results tab. It returns this level for most artifact types, unless the associated file is assumed to be of greater interest (for example, a Hash Set Hit will not be level 6 because the file itself is of greater interest).

Level 5 - Based on the file in the selected node and very specific to the file type. The current content viewer that will return level 5 is the Application tab, which supports media files (such as images) and certain types of databases.

Level 4 - Based on the file in the selected node but fairly general. Currently this is the level returned by the Text tab if Keyword Search has been run (unless the node is a Keyword Search hit or a Credit Card account). This is the default tab for most files.

Level 3 - Based on the artifact, if any, in the selected node where the artifact is thought to be of less interest than the associated file. This level is returned by the Results tab for artifacts like Hash Set Hits.

Level 1 - Very general and should always be available. The Hex, Text, and Metadata tabs are all this level

Level 0 - For cases where the content viewer should never be displayed by default.

nodeNode to check for preference
an int (0-10) higher return means the viewer has higher priority

Implemented in org.sleuthkit.autopsy.corecomponents.DataContentViewerHex, org.sleuthkit.autopsy.contentviewers.MessageContentViewer, org.sleuthkit.autopsy.corecomponents.DataContentViewerArtifact, org.sleuthkit.autopsy.contentviewers.AnnotationsContentViewer, org.sleuthkit.autopsy.centralrepository.contentviewer.DataContentViewerOtherCases, org.sleuthkit.autopsy.contentviewers.Metadata, org.sleuthkit.autopsy.contentviewers.contextviewer.ContextViewer, org.sleuthkit.autopsy.contentviewers.FileViewer, and org.sleuthkit.autopsy.contentviewers.textcontentviewer.TextContentViewer.

boolean org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer.isSupported ( Node  node)
void org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer.resetComponent ( )
void org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer.setNode ( Node  selectedNode)

The documentation for this interface was generated from the following file:

Copyright © 2012-2020 Basis Technology. Generated on: Wed Apr 8 2020
This work is licensed under a Creative Commons Attribution-Share Alike 3.0 United States License.