();
-
- int totalImageSet = getImageSetCount();
- Element imgElement = getImagesElement();
- for(int i = 0; i < totalImageSet; i++){
- Element imgSetElement = (Element)imgElement.getElementsByTagName(IMG_SET_NAME).item(i);
- result.add(TimeZone.getTimeZone(imgSetElement.getAttribute(TIMEZONE)));
- }
-
- return result; //TODO: get time zones from db
- }
-//
-// /**
-// * Removes the imageSet of the given image ID.
-// *
-// * @param imgID the image ID of the image that going to be removed
-// */
-// public void removeImageSet(int imgID) {
-// Element imgElement = getImagesElement();
-// Element selectedElement = getImageSetElement(imgID);
-// imgElement.removeChild(selectedElement); // remove the imagesetElement
-// doc.normalize();
-//
-// // edit the modified data
-// String newDate = dateFormat.format(new Date());
-// Element rootEl = getRootElement();
-// rootEl.getElementsByTagName(MODIFIED_DATE_NAME).item(0).setTextContent(newDate);
-// }
-
/**
* Initialize the basic values for a new case management file.
* Note: this is the schema version 1.0
*
- * @param parentPath the name of the parent of the case directory.
+ * @param dirPath case directory path
* @param caseName the name of the config file to be located in the case directory
+ * @param examiner examiner for the case (optional, can be empty string
+ * @param caseNumber case number (optional), can be empty
*/
protected void create(String dirPath, String caseName, String examiner, String caseNumber) throws Exception {
clear(); // clear the previous data
@@ -748,11 +547,6 @@ public class XMLCaseManagement implements CaseConfigFileInterface{
cacheElement.setAttribute(RELATIVE_NAME, "true");
caseElement.appendChild(cacheElement);
- // create the new images
- Element imagesElement = doc.createElement(IMAGES_NAME); // ...
- imagesElement.setAttribute(NEXT_ID_NAME, Integer.toString(0)); // add nextID to 0
- rootElement.appendChild(imagesElement);
-
// write more code if needed ...
}
@@ -894,56 +688,4 @@ public class XMLCaseManagement implements CaseConfigFileInterface{
examiner = "";
}
- /**
- * Adds the image to the current document handler.
- *
- * @param images the paths of the images that want to be added
- * @param currentID the ID of the image that want to be added
- * @param timeZone the timeZone where the image is added
- */
- protected void addImage(String[] images, long currentID, String timeZone) throws Exception {
-
- //String dbName = "image-" + currentID + ".db";
-
- if (doc == null) {
- throw new Exception("No case open.");
- } else {
- Element rootEl = getRootElement();
-
- int imgCount = images.length; // how many given images to add to the config file
- Element imagesElement = getImagesElement();
-
- //int currentID = Integer.parseInt(imagesElement.getAttribute(NEXT_ID_NAME));
-
- // add the latest image set
- Element imgSetElement = doc.createElement(IMG_SET_NAME); // ...
- imgSetElement.setAttribute(IMG_SET_COUNT, Integer.toString(imgCount));
- imgSetElement.setAttribute(IMG_SET_ID, Long.toString(currentID));
- imgSetElement.setAttribute(TIMEZONE, timeZone);
- imagesElement.appendChild(imgSetElement);
-
- // add all the image Path
-// for (int i = 0; i < imgCount; i++) {
-// Element imgPathElement = doc.createElement(IMG_PATH_NAME); // ...
-// imgPathElement.setAttribute(IMG_PATH_ID, Integer.toString(i));
-// imgPathElement.setAttribute(RELATIVE_NAME, "false");
-// imgPathElement.appendChild(doc.createTextNode(images[i]));
-// imgSetElement.appendChild(imgPathElement);
-// }
-//
-// // add the database
-// Element imgDbElement = doc.createElement(IMG_DB_NAME); // ...
-// imgDbElement.setAttribute(RELATIVE_NAME, "true");
-// imgDbElement.appendChild(doc.createTextNode(dbName));
-// //imgDbElement.appendChild(doc.createTextNode("image-" + currentID + ".db"));
-// imgSetElement.appendChild(imgDbElement);
-
- // edit the modified data
- String newDate = dateFormat.format(new Date());
- rootEl.getElementsByTagName(MODIFIED_DATE_NAME).item(0).setTextContent(newDate);
- }
-
-// JOptionPane.showMessageDialog(caller, "Error while trying to add the image to XML config file.\n \nDetail: \n" + e.getMessage() + " (at " + className + ").", "Error", JOptionPane.ERROR_MESSAGE);
-
- }
}
diff --git a/Case/src/org/sleuthkit/autopsy/casemodule/package.dox b/Case/src/org/sleuthkit/autopsy/casemodule/package.dox
new file mode 100644
index 0000000000..3f438b6ecc
--- /dev/null
+++ b/Case/src/org/sleuthkit/autopsy/casemodule/package.dox
@@ -0,0 +1,61 @@
+// @@@ VERIFY THAT we mention add case wizard in here
+/**
+\package org.sleuthkit.autopsy.casemodule
+
+The org.sleuthkit.autopsy.casemodule Module is responsible for organizing a case. A case contains one or more disk images and is the highest-level unit of an investigation.
+
+\section casemodule_contents Package Contents
+The important classes in this case are:
+- Case
+
+\section casemodule_overview Overview
+All data in a case will be stored in a single database and configuration file. A case must be open before analysis can occur. You will use a Case object to get access to the data being analyzed.
+
+Case settings are stored in an XML file. See the XMLCaseManagement class for more details.
+
+Currently, only one case can be opened at a time. To determine the open case, use the Case.getCurrentCase() method.
+Do not cache the case handle object obtained from this method (for example, in member variables) unless you are sure your are acting within case context;
+It is safer to call the method more frequently to ensure the validity of the case handle object as new cases are opened.
+Once you have the object for the currently open case, Case.getRootObjects() will return the top-level Sleuth Kit Content modules. You can then get their children to go down the tree of data types.
+
+
+\section casemodule_events Case Events
+To receive an event when cases are opened, closed, or changed, use the Case.addPropertyChangeListener(PropertyChangeListener) method to register your class as a PropertyChangeListener. This is most commonly required when developing a new module that needs to get data about the currently opened case.
+
+
+\section casemodule_add_image Add Image Process
+The sleuthkit library performs most the actual work of adding the image to the database and Autopsy provides the user interface, calls methods to set up and control and finalize the process.
+
+Add image process is first invoked by AddImageAction.
+AddImageWizardIterator instantiates and manages the wizard panels.
+
+A background worker thread is spawned in AddImgTask class. The work is delegated to org.sleuthkit.datamodel.AddImageProcess, which calls into native sleuthkit methods via SleuthkitJNI interface.
+
+The entire process is enclosed within a database transaction and the transaction is not committed until user finalizes the process.
+User can also interrupt the ongoing add image process, which results in a special stop call in sleuthkit. The stop call sets a special stop flag internally in sleuthkit.
+
+The flag is checked by the sleutkit code as it is processing the image and,
+if set, it will result in breaking out of any current processing loops and methods, and return from sleuthkit.
+The worker thread in Autopsy will terminate and revert will be called to back out of the current transaction.
+During add image process, sleuthkit library reads the image and populates the TSK SQLite database with the image meta-data.
+
+The resulting database will have the TSK schema (http://wiki.sleuthkit.org/index.php?title=SQLite_Database_v2_Schema).
+After image has been processed successfully and after the user confirmation, the transaction is committed to the database.
+
+Errors from processing the image in sleuthkit are propagated using org.sleuthkit.datamodel.TskCoreException and org.sleuthkit.datamodel.TskDataException java exceptions.
+The errors are logged and can be reviewed by the user from the wizard.
+org.sleuthkit.datamodel.TskCoreException is handled by the wizard as a critical, unrecoverable error condition with TSK core, resulting in the interruption of the add image process.
+org.sleuthkit.datamodel.TskDataException, pertaining to an error associated with the data itself (such as invalid volume offset), is treated as a warning - the process still continues because there are likely data image that can be still read.
+
+\section casemodule_concurrency Concurrency and locking
+Autopsy is a multi-threaded application; besides threads associated with the GUI, event dispatching and Netbeans RCP framework,
+the application uses threads to support concurrent user-driven processes.
+For instance, user can add another image to the database while ingest is running on previously added images.
+
+During the add image process, a database lock is acquired using org.sleuthkit.datamodel.SleuthkitCase.dbWriteLock() to ensure exclusive access to the database resource.
+Once the lock is acquired by the add image process, other Autopsy threads trying to access the database as acquire the lock (such as ingest modules) will block for the duration of add image process.
+
+The database lock is implemented with SQLite database in mind, which does not support concurrent writes. The database lock is released with org.sleuthkit.datamodel.SleuthkitCase.dbWriteUnlock() when the add image process has ended. The database lock is used for all database access methods in org.sleuthkit.datamodel.SleuthkitCase.
+
+ */
+
diff --git a/Case/src/org/sleuthkit/autopsy/casemodule/package.html b/Case/src/org/sleuthkit/autopsy/casemodule/package.html
deleted file mode 100644
index 4d7d55f36f..0000000000
--- a/Case/src/org/sleuthkit/autopsy/casemodule/package.html
+++ /dev/null
@@ -1,10 +0,0 @@
-
- A case contains one or more disk images and is the highest-level unit of an investigation. All data in a case will be stored in a single database and configuration file. A case must be open before analysis can occur. You will use a {@link org.sleuthkit.autopsy.casemodule.Case#Case Case} object to get access to the data being analyzed.
-
- Case settings are stored in an XML file. See the {@link org.sleuthkit.autopsy.casemodule.XMLCaseManagement#XMLCaseManagement() XMLCaseManagement} class for more details.
-
- Currently, only one case can be opened at a time. To determine the open case, use the static {@link org.sleuthkit.autopsy.casemodule.Case#getCurrentCase() Case.getCurrentCase()} method. Once you have the object for the currently open case, {@link org.sleuthkit.autopsy.casemodule.Case#getRootObjects() Case.getRootObjects()} will return the top-level Sleuth Kit Content modules. You can then get their children to go down the tree of data types.
-
- To receive an event when cases are opened, closed, or changed, use the {@link org.sleuthkit.autopsy.casemodule.Case#addPropertyChangeListener(PropertyChangeListener) addPropertyChangeListener} method to register your class as a PropertyChangeListener. THis is most commonly required when developing a new {@link org.sleuthkit.autopsy.corecomponentinterfaces.DataExplorer#DataExplorer() DataExplorer} module that needs to get data about the currently opened case.
-
-
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/DataContentViewer.java b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/DataContentViewer.java
index f77479e6ea..bd99546299 100644
--- a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/DataContentViewer.java
+++ b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/DataContentViewer.java
@@ -71,11 +71,15 @@ public interface DataContentViewer {
/**
* Checks whether the given viewer is preferred for the Node
+ *
* @param node Node to check for preference
- * @param isSupported, true if the viewer is supported by the node
+ * @param isSupported true if the viewer is supported by the node, false otherwise
* as determined by a previous check
- * @return True if viewer preferred, else false
+ * @return an int (0-10) higher return means the viewer has higher priority
+ * 0 means not supported
+ * 1/2 means will display all supported
+ * 3-10 are prioritized by Content viewer developer
*/
- public boolean isPreferred(Node node, boolean isSupported);
+ public int isPreferred(Node node, boolean isSupported);
}
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/package.dox b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/package.dox
new file mode 100644
index 0000000000..9beb6e1d37
--- /dev/null
+++ b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/package.dox
@@ -0,0 +1,93 @@
+/**
+ * \package org.sleuthkit.autopsy.corecomponentinterfaces
+ * This package contains the interface classes that define the core components in Autopsy. These components are used in the difference zones of the GUI.
+ *
+NOTE: Much of this data may be out of date. It has not been updated
+since a major redesign was done.
+
+\section corecomponentinterface_contents Package Contents
+The following are imporant classes in this package
+- TODO
+
+
+ * Autopsy Zones
+ * There are three major zones in the Autopsy UI. The left hand side has the org.sleuthkit.autopsy.corecomponentinterfaces.DataExplorer zone. This area is where you can search for and explore data. It has all of the analysis smarts. An example of a DataExplorer is the directory tree that shows the hierarchy of directories (and hides the files from view).
+ * The DataExplorer area identifies a subset of the data to show the user and passes the data to the org.sleuthkit.autopsy.corecomponentinterfaces.DataResult area in the upper right. In the previous example, the contents of a specific folder would be passed to this area and displayed in a table or thumbnail form.
+ * When a file or object is selected in the DataResult, it is passed to the org.sleuthkit.autopsy.corecomponentinterfaces.DataContent zone in the lower right. This is where file content can be viewed in hex form, strings, etc.
+ * Data Flow
+ * Creating Nodes in DataExplorer
+ * Data flows between the areas inside of a NetBeans node. The DataExplorer modules create the NetBeans nodes. They query the SQLite database or do whatever they want to identify the set of files that are of interest. They create the NetBeans nodes based on Sleuthkit data model objects. See the org.sleuthkit.autopsy.datamodel package for more details on this.
+ * Getting Nodes to DataResult
+ * Each DataExplorer TopComponent is responsible for creating its own DataResult TopComponent to display its results. It can choose to re-use the same TopComponent for multiple searches (as DirectoryTree does) or it can choose to make a new one each time (as FileSearch does). The setNode() method on the DataResult object is used to set the root node to display. A dummy root node must be created as the parent if a parent does not already exist.
+ * The DataExplorer is responsible for setting the double-click and right-click actions associated with the node. The default single click action is to pass data to DataContent. To override this, you must create a new DataResultViewer instance that overrides the propertyChange() method. The DataExplorer adds actions to wrapping the node in a FilterNode variant. The FilterNode then defines the actions for the node by overriding the getPreferredAction() and getActions() methods. As an example, org.sleuthkit.autopsy.directorytree.DataResultFilterNode and org.sleuthkit.autopsy.directorytree.DataResultFilterChildren wraps the nodes that are passed over by the DirectoryTree DataExplorer.
+ * DataResult can send data back to its DataExplorer by making a custom action that looks up it's instance (DataExplorer.getInstance()).
+ * Getting Nodes to DataContent
+ * A default DataContent viewer is created when a case is opened. To display the contents of a node, it must be passed to a DataContent instance. The default single-click behavior of the DataResultViewers is to lookup the default DataContent TopComponent and pass the selected node to it. See org.sleuthkit.autopsy.corecomponents.AbstractDataResultViewer.propertyChange(PropertyChangeEvent) for details.
+ * Creating new Functionality
+ * Creating a DataExplorer
+ *
+ * - Create a module from within NetBeans. It must be dependent on these modules:
+ *
+ * - Case
+ *
- CoreComponentInterfaces
+ *
- CoreComponents
+ *
- DataModel
+ *
- DialogsAPI (if pop-ups and such are going to be used)
+ *
- Explorer & Property Sheet API
+ *
- Lookup
+ *
- Nodes API
+ *
- Setting API
+ *
- UI Utilities API
+ *
- Utilities API
+ *
- Window System API
+ *
+ * - Create a class that implements org.sleuthkit.autopsy.corecomponentinterfaces.DataExplorer. We have been making the TopComponent class be the one that implements DataExplorer. Register this class as a DataExplorer service provider by specifying "@ServiceProvider(service=DataExplorer.class)" in the class or using layer.xml.
+ *
- Implement the methods required by the DataExplorer interface.
+ *
- Register the class to receive property change events from the org.sleuthkit.autopsy.Case module by using its addPropertyChangeListener() method.
+ *
- Access case data using the org.sleuthkit.autopsy.Case module.
+ *
- Create Nodes for the data objects using the techniques outlined in the previous section.
+ *
- Wrap the nodes in FilterNodes to define actions as outlined in the previous section.
+ *
- Send results to DataResults using the techniques outlined in the previous section.
+ *
+ * Creating a DataResultViewer
+ * DataResultTopComponent is the high-level window in the DataResult area. Each instance of this loads up all instances of DataResultViewers that have been registered with the system. Example viewers include the table and thumbnail views. If you want to make your own type of viewer, follow the steps below. Note that the table and thumbnail viewers come with Autopsy by default and can be used by all DataExplorers.
+ *
+ * - Create a module from within NetBeans. It must be dependent on these modules:
+ *
+ * - Case
+ *
- CoreComponentInterfaces
+ *
- CoreComponents
+ *
- DataModel
+ *
- DialogsAPI (if pop-ups and such are going to be used)
+ *
- Explorer & Property Sheet API
+ *
- Lookup
+ *
- Nodes API
+ *
- Setting API
+ *
- UI Utilities API
+ *
- Utilities API
+ *
- Window System API
+ *
+ * - Make a class that extends org.sleuthkit.autopsy.corecomponents.AbstractDataResultViewer and is registered as a service provider for the org.sleuthkit.autopsy.corecomponentinterfaces.DataResultViewer class by specifying "@ServiceProvider(service = DataResultViewer.class)" or by using layer.xml. This class will extend JPanel.
+ * - See the previous sections on default actions.
+ *
+ * Creating a DataContentViewer
+ * DataContentTopComponent is the high-level window in the DataContent area. Each instance of this loads up all instances of DataContentViewers that have been registered with the system. Example viewers include the strings and hexdump views. If you want to make your own type of viewer, follow the steps below. Note that the strings, hexdump, and image viewers come with Autopsy by default and can be used by all DataExplorers and DataResults. You only need to make a new DataContentViewer if these viewers do not satisfy your needs.
+ *
+ * - Create a module from within NetBeans. It must be dependent on these modules:
+ *
+ * - Case
+ *
- CoreComponentInterfaces
+ *
- CoreComponents
+ *
- DataModel
+ *
- DialogsAPI (if pop-ups and such are going to be used)
+ *
- Explorer & Property Sheet API
+ *
- Lookup
+ *
- Nodes API
+ *
- Setting API
+ *
- UI Utilities API
+ *
- Utilities API
+ *
- Window System API
+ *
+ * - Make a class that implements org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer and is registered as a service provider for DataContentViewer.class by specifying "@ServiceProvider(service = DataContentViewer.class)" or by using layer.xml. This class must extend JPanel.
+ *
+*/
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/package.html b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/package.html
deleted file mode 100644
index a43d19c45f..0000000000
--- a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/corecomponentinterfaces/package.html
+++ /dev/null
@@ -1,106 +0,0 @@
-
-This package contains the interface classes that define the core components in Autopsy. These components are used in the difference zones of the GUI.
-
-Autopsy Zones
-
-There are three major zones in the Autopsy UI. The left hand side has the {@link org.sleuthkit.autopsy.corecomponentinterfaces.DataExplorer DataExplorer} zone. This area is where you can search for and explore data. It has all of the analysis smarts. An example of a DataExplorer is the directory tree that shows the hierarchy of directories (and hides the files from view).
-
-The DataExplorer area identifies a subset of the data to show the user and passes the data to the {@link org.sleuthkit.autopsy.corecomponentinterfaces.DataResult DataResult}s area in the upper right. In the previous example, the contents of a specific folder would be passed to this area and displayed in a table or thumbnail form.
-
-When a file or object is selected in the DataResult, it is passed to the {@link org.sleuthkit.autopsy.corecomponentinterfaces.DataContent DataContent} zone in the lower right. This is where file content can be viewed in hex form, strings, etc.
-
-
-Data Flow
-Creating Nodes in DataExplorer
-
-Data flows between the areas inside of a NetBeans node. The DataExplorer modules create the NetBeans nodes. They query the SQLite database or do whatever they want to identify the set of files that are of interest. They create the NetBeans nodes based on Sleuthkit data model objects. See the org.sleuthkit.autopsy.datamodel package for more details on this.
-
-Getting Nodes to DataResult
-
-Each DataExplorer TopComponent is responsible for creating its own DataResult TopComponent to display its results. It can choose to re-use the same TopComponent for multiple searches (as DirectoryTree does) or it can choose to make a new one each time (as FileSearch does). The setNode() method on the DataResult object is used to set the root node to display. A dummy root node must be created as the parent if a parent does not already exist.
-
-The DataExplorer is responsible for setting the double-click and right-click actions associated with the node. The default single click action is to pass data to DataContent. To override this, you must create a new DataResultViewer instance that overrides the propertyChange() method. The DataExplorer adds actions to wrapping the node in a FilterNode variant. The FilterNode then defines the actions for the node by overriding the getPreferredAction() and getActions() methods. As an example, org.sleuthkit.autopsy.directorytree.DataResultFilterNode and org.sleuthkit.autopsy.directorytree.DataResultFilterChildren wraps the nodes that are passed over by the DirectoryTree DataExplorer.
-
-DataResult can send data back to its DataExplorer by making a custom action that looks up it's instance (DataExplorer.getInstance()).
-
-Getting Nodes to DataContent
- A default DataContent viewer is created when a case is opened. To display the contents of a node, it must be passed to a DataContent instance. The default single-click behavior of the DataResultViewers is to lookup the default DataContent TopComponent and pass the selected node to it. See {@link org.sleuthkit.autopsy.corecomponents.AbstractDataResultViewer#propertyChange(PropertyChangeEvent) AbstractDataResultViewer.propertyChange()} for details.
-
-Creating new Functionality
-
-Creating a DataExplorer
-
- - Create a module from within NetBeans. It must be dependent on these modules:
-
- - Case
-
- CoreComponentInterfaces
-
- CoreComponents
-
- DataModel
-
- DialogsAPI (if pop-ups and such are going to be used)
-
- Explorer & Property Sheet API
-
- Lookup
-
- Nodes API
-
- Setting API
-
- UI Utilities API
-
- Utilities API
-
- Window System API
-
-
- - Create a class that implements {@link org.sleuthkit.autopsy.corecomponentinterfaces.DataExplorer DataExplorer}. We have been making the TopComponent class be the one that implements DataExplorer. Register this class as a DataExplorer service provider by specifying "@ServiceProvider(service=DataExplorer.class)" in the class or using layer.xml.
-
- Implement the methods required by the DataExplorer interface.
-
- Register the class to receive property change events from the org.sleuthkit.autopsy.Case module by using its addPropertyChangeListener() method.
-
- Access case data using the org.sleuthkit.autopsy.Case module.
-
- Create Nodes for the data objects using the techniques outlined in the previous section.
-
- Wrap the nodes in FilterNodes to define actions as outlined in the previous section.
-
- Send results to DataResults using the techniques outlined in the previous section.
-
-
-Creating a DataResultViewer
-DataResultTopComponent is the high-level window in the DataResult area. Each instance of this loads up all instances of DataResultViewers that have been registered with the system. Example viewers include the table and thumbnail views. If you want to make your own type of viewer, follow the steps below. Note that the table and thumbnail viewers come with Autopsy by default and can be used by all DataExplorers.
-
-
- - Create a module from within NetBeans. It must be dependent on these modules:
-
- - Case
-
- CoreComponentInterfaces
-
- CoreComponents
-
- DataModel
-
- DialogsAPI (if pop-ups and such are going to be used)
-
- Explorer & Property Sheet API
-
- Lookup
-
- Nodes API
-
- Setting API
-
- UI Utilities API
-
- Utilities API
-
- Window System API
-
-
- - Make a class that extends {@link org.sleuthkit.autopsy.corecomponents.AbstractDataResultViewer#AbstractDataResultViewer() AbstractDataResultViewer} and is registered as a service provider for the {@link org.sleuthkit.autopsy.corecomponentinterfaces.DataResultViewer DataResultViewer} class by specifying "@ServiceProvider(service = DataResultViewer.class)" or by using layer.xml. This class will extend JPanel.
-
- - See the previous sections on default actions.
-
-
-Creating a DataContentViewer
-DataContentTopComponent is the high-level window in the DataContent area. Each instance of this loads up all instances of DataContentViewers that have been registered with the system. Example viewers include the strings and hexdump views. If you want to make your own type of viewer, follow the steps below. Note that the strings, hexdump, and image viewers come with Autopsy by default and can be used by all DataExplorers and DataResults. You only need to make a new DataContentViewer if these viewers do not satisfy your needs.
-
-
- - Create a module from within NetBeans. It must be dependent on these modules:
-
- - Case
-
- CoreComponentInterfaces
-
- CoreComponents
-
- DataModel
-
- DialogsAPI (if pop-ups and such are going to be used)
-
- Explorer & Property Sheet API
-
- Lookup
-
- Nodes API
-
- Setting API
-
- UI Utilities API
-
- Utilities API
-
- Window System API
-
-
- - Make a class that implements {@link org.sleuthkit.autopsy.corecomponentinterfaces.DataContentViewer DataContentViewer} and is registered as a service provider for DataContentViewer.class by specifying "@ServiceProvider(service = DataContentViewer.class)" or by using layer.xml. This class must extend JPanel.
-
-
-
\ No newline at end of file
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/account-icon-16.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/account-icon-16.png
new file mode 100644
index 0000000000..73d9cfeabb
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/account-icon-16.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/audio-file.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/audio-file.png
new file mode 100644
index 0000000000..516ac7f233
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/audio-file.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/doc-file.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/doc-file.png
new file mode 100644
index 0000000000..2d364e1cf3
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/doc-file.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/exe-file.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/exe-file.png
new file mode 100644
index 0000000000..a886401df0
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/exe-file.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/folder-icon-16.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/folder-icon-16.png
new file mode 100644
index 0000000000..c8eb4f6708
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/folder-icon-16.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/image-file.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/image-file.png
new file mode 100644
index 0000000000..e2e79d0324
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/image-file.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/mail-icon-16.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/mail-icon-16.png
new file mode 100644
index 0000000000..a919ae3e50
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/mail-icon-16.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/pdf-file.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/pdf-file.png
new file mode 100644
index 0000000000..7a6dcb42d0
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/pdf-file.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/searchquery.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/searchquery.png
new file mode 100644
index 0000000000..d036553018
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/searchquery.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/text-file.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/text-file.png
new file mode 100644
index 0000000000..43ec054ac2
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/text-file.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/video-file.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/video-file.png
new file mode 100644
index 0000000000..c290609f59
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/video-file.png differ
diff --git a/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/web-file.png b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/web-file.png
new file mode 100644
index 0000000000..ac5957ad62
Binary files /dev/null and b/CoreComponentInterfaces/src/org/sleuthkit/autopsy/images/web-file.png differ
diff --git a/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationCleanDialog.form b/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationCleanDialog.form
new file mode 100644
index 0000000000..8c0236cde0
--- /dev/null
+++ b/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationCleanDialog.form
@@ -0,0 +1,24 @@
+
+
+
diff --git a/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationCleanDialog.java b/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationCleanDialog.java
new file mode 100644
index 0000000000..0ae2014ca4
--- /dev/null
+++ b/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationCleanDialog.java
@@ -0,0 +1,81 @@
+/*
+ * To change this template, choose Tools | Templates
+ * and open the template in the editor.
+ */
+package org.sleuthkit.autopsy.corecomponents;
+
+import java.awt.Component;
+import java.awt.Dimension;
+import java.awt.Toolkit;
+import javax.swing.JFrame;
+import javax.swing.JPanel;
+
+/**
+ * Displays a panel in a new clean dialog. A clean dialog contains nothing
+ * but the panel given to it. No additional buttons or features, except
+ * the default close operation, which is set to dispose.
+ */
+public class AdvancedConfigurationCleanDialog extends javax.swing.JDialog {
+
+ /** Creates new form AdvancedConfigurationDialog */
+ public AdvancedConfigurationCleanDialog() {
+ this(false);
+ }
+
+ /** Creates new form AdvancedConfigurationDialog */
+ public AdvancedConfigurationCleanDialog(boolean resizable) {
+ super(new JFrame(), true);
+ setResizable(resizable);
+ if(resizable) {
+ this.setIconImage(null);
+ }
+ initComponents();
+ }
+
+ /**
+ * Display the given panel on a clean dialog.
+ * @param panel the panel to display
+ */
+ public void display(JPanel panel) {
+ this.setTitle(panel.getName());
+
+ panel.setAlignmentX(Component.CENTER_ALIGNMENT);
+ this.add(panel, 0);
+ this.pack();
+
+ Dimension screenDimension = Toolkit.getDefaultToolkit().getScreenSize();
+ // set the popUp window / JFrame
+ int w = this.getSize().width;
+ int h = this.getSize().height;
+
+ // set the location of the popUp Window on the center of the screen
+ setLocation((screenDimension.width - w) / 2, (screenDimension.height - h) / 2);
+
+ this.setVisible(true);
+ }
+
+ /**
+ * Close the dialog.
+ */
+ public void close() {
+ this.dispose();
+ }
+
+ /**
+ * This method is called from within the constructor to initialize the form.
+ * WARNING: Do NOT modify this code. The content of this method is always
+ * regenerated by the Form Editor.
+ */
+ @SuppressWarnings("unchecked")
+ // //GEN-BEGIN:initComponents
+ private void initComponents() {
+
+ setDefaultCloseOperation(javax.swing.WindowConstants.DISPOSE_ON_CLOSE);
+ getContentPane().setLayout(new javax.swing.BoxLayout(getContentPane(), javax.swing.BoxLayout.LINE_AXIS));
+
+ pack();
+ }// //GEN-END:initComponents
+
+ // Variables declaration - do not modify//GEN-BEGIN:variables
+ // End of variables declaration//GEN-END:variables
+}
diff --git a/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationDialog.form b/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationDialog.form
index d99cc0b860..cc784d4d4a 100644
--- a/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationDialog.form
+++ b/CoreComponents/src/org/sleuthkit/autopsy/corecomponents/AdvancedConfigurationDialog.form
@@ -1,4 +1,4 @@
-
+