Warning: This is a facade provided for use by user code, not for implementation by user code. User implementations of this interface are highly likely to be incompatible with future releases of the product at both binary and source levels.
@mock.generateWarning: This is a facade provided for use by user code, not for implementation by user code. User implementations of this interface are highly likely to be incompatible with future releases of the product at both binary and source levels.
Parameters class represents a set of key-value pairs. The Parameters object provides a mechanism to obtain values based on a String name. There are convenience methods that allow you to use defaults if the value does not exist, as well as obtain the value in any of the same formats that are in the {@link Configuration} interface.
While there are similarities between the Parameters object and the java.util.Properties object, there are some important semantic differences. First, Parameters are read-only. Second, Parameters are easily derived from {@link Configuration} objects. Lastly, theParameters object is derived from XML fragments that look like this:
<parameter name="param-name" value="param-value" /> Note: this class is not thread safe by default. If you require thread safety please synchronize write access to this class to prevent potential data corruption.
@author Avalon Development Team @version CVS $Revision: 1.41 $ $Date: 2004/02/11 14:34:25 $A convenience class for creating parameter objects for initializing configuration builder objects.
For setting initialization properties of new configuration objects, a number of specialized parameter classes exists. These classes use inheritance to organize the properties they support in a logic way. For instance, parameters for file-based configurations also support the basic properties common to all configuration implementations, parameters for XML configurations also include file-based and basic properties, etc.
When constructing a configuration builder, an easy-to-use fluent API is desired to define specific properties for the configuration to be created. However, the inheritance structure of the parameter classes makes it surprisingly difficult to provide such an API. This class comes to rescue by defining a set of methods for the creation of interface-based parameter objects offering a truly fluent API. The methods provided can be called directly when setting up a configuration builder as shown in the following example code fragment:
Parameters params = new Parameters(); configurationBuilder.configure(params.fileBased() .setThrowExceptionOnMissing(true).setEncoding("UTF-8") .setListDelimiter('#').setFileName("test.xml")); Using this class it is not only possible to create new parameters objects but also to initialize the newly created objects with default values. This is via the associated {@link DefaultParametersManager} object. Such an objectcan be passed to the constructor, or a new (uninitialized) instance is created. There are convenience methods for interacting with the associated {@code DefaultParametersManager}, namely to register or remove {@link DefaultParametersHandler} objects. On all newly created parametersobjects the handlers registered at the associated {@code DefaultParametersHandler}are automatically applied.
Implementation note: This class is thread-safe.
@version $Id: Parameters.java 1624601 2014-09-12 18:04:36Z oheger $ @since 2.0"Parameters" (not this class) are columns in a database that this app is working with, and are used to create the axis of the images produced by this app. More specifically, they are used to determine the location of each pixel in an image, which is associated with one row in the database or one datapoint of a set. See javadoc in {@link com.visitrend.ndvis.model.DataInfo com.visitrend.ndvis.model.DataInfo}for more info.
This is a GUI that allows the user to change the order of parameters and what parameters are no what axis. It holds state on parameters like their current order and how many are assigned to each axis. Anything changing the order of parameters or how many are on each axis should do it through here (so that other relevant classes can update themselves as necessary). This can also display the values for parameters (currently in a one row com.visitrend.ndvis.table, though you can implement this however you want). For instance, this works with {@link com.visitrend.ndvis.gui.ParametersController com.visitrend.ndvis.gui.ParametersController}to show the parameter values associated with each pixel of an image as the user mouses over them.
The parameters order and values are displayed in a JTable. Reading the parameters left to right in the com.visitrend.ndvis.table, the 0th through the numParametersOnX are the parameters on the X axis (and the rest are on Y). Its important to note that in Java's TableModel, the values and indexes into its data do not change order even though the gui JTable may change the order of the columns by TableColumnModel's move(int oldIndex, int newIndex) method or the user dragging columns about. The methods in this class account for that.
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |