Difference: DpHipeComponents (19 vs. 20)

Revision 202012-07-11 - DavideRizzo

Line: 1 to 1
 
META TOPICPARENT name="DpHipe"
Line: 46 to 49
 

Outline View

Changed:
<
<
Whenever the user selects a session variable in the [[http://herschel.esac.esa.int/hcss-doc-12.0/index.jsp#hcss_drm:herschel.ia.inspector.views.VariablesView][VariablesView]], a [[http://herschel.esac.esa.int/hcss-doc-12.0/index.jsp#hcss_drm:herschel.ia.gui.kernel.event.SelectionEvent][SelectionEvent]] is sent around.
The [[http://herschel.esac.esa.int/hcss-doc-12.0/index.jsp#hcss_drm:herschel.ia.inspector.views.OutlineView][OutlineView]] is listening to such event and it tries to find the appropriate component that can show the outline information of that variable.
>
>
Whenever the user selects a session variable in the VariablesView, a SelectionEvent is sent around.
The OutlineView is listening to such event and it tries to find the appropriate component that can show the outline information of that variable.
  The contract for outline components is:
Changed:
<
<
  • Implement the [[http://herschel.esac.esa.int/hcss-doc-12.0/index.jsp#hcss_drm:herschel.ia.gui.apps.views.outline.OutlineComponent][OutlineComponent]] interface by extending a javax.swing.JComponent.
>
>
 
Changed:
<
<
The recommended way of implementing [[http://herschel.esac.esa.int/hcss-doc-12.0/index.jsp#hcss_drm:herschel.ia.gui.apps.views.outline.OutlineComponent][OutlineComponent]] is by extending ObjectOutline, which provides a table with basic information about the variable.
>
>
The recommended way of implementing OutlineComponent is by extending ObjectOutline, which provides a table with basic information about the variable.
 Methods getExtraTableInfo() and getExtraComponent() may be overriden as needed for providing extra information about your type.

For example, suppose you want to create an outline for FineTime variables to show their contents in the outline view whenever a session variable of that type is selected by the user.

Line: 95 to 98
 

Source Code of Basic implementations

Changed:
<
<
Package herschel.ia.dataset.gui contains some basic implementations for OutlineComponents:
  • ArrayDataOutline: a simple outline for any array data
  • DatasetOutline: a simple outline for any dataset
  • ProductOutline: a simple outline for any product
>
>
Package herschel.ia.dataset.gui contains some basic implementations for OutlineComponent objects:
 
  • __init__.py: how the above get registered
Changed:
<
<
Tip, idea If you have a sub-class of e.g. a product, you can also create a dedicated OutlineComponent for that sub-class, which will be picked up instead of the default ProductOutline.
>
>
Tip, idea If you have a sub-class of e.g. a product, you can also create a dedicated OutlineComponent for that sub-class, which will be picked up instead of the default ProductOutline.
 
Line: 110 to 113
 
A special kind of outline is devoted to show previews of FITS files (for images, cubes, spectra...).
Changed:
<
<
This is managed by FitsFileOutline, which reads the product contained in the FITS file in the background, and shows an image preview for it when done.
>
>
This is managed by FitsFileOutline, which reads the product contained in the FITS file in the background, and shows an image preview for it when done.
  For this to work properly, any type that is meaningful to produce a preview should:
Changed:
<
<
1. Extend herschel.ia.gui.kernel.PreviewMaker. For example, for images (herschel.ia.gui.image.Image):
>
>
1. Extend herschel.ia.gui.kernel.PreviewMaker. For example, for images (herschel.ia.gui.image.Image):
 
import herschel.ia.gui.image.Image;

Line: 202 to 205
 

Source Code of Basic implementations

Changed:
<
<
The herschel.ia.gui.apps package contains some basic implementations for EditorComponents:
  • ListEditorComponent: a simple viewer of lists.
  • DefaultFileEditorComponent: a simple viewer of a file.
>
>
The herschel.ia.gui.apps package contains some basic implementations for EditorComponent objects:
 
  • __init__.py: how the above get registered.
Line: 213 to 216
 
You may have created an implementation of the former Explorer interface which is used by the dataset inspector (and is registered within that inspector).
Changed:
<
<
If you do not expect that your explorer needs to talk to other parts within the HIPE application, you can simply extend ia.dataset.gui.views.AbstractExplorerComponent:
>
>
If you do not expect that your explorer needs to talk to other parts within the HIPE application, you can simply extend [[http://herschel.esac.esa.int/hcss-doc-12.0/index.jsp#hcss_drm:herschel.ia.dataset.gui.views.AbstractExplorerComponent][ia.dataset.gui.views.AbstractExplorerComponent]:
 
public class ArrayDataComponent extends AbstractExplorerComponent<ArrayData> {

 
This site is powered by the TWiki collaboration platform Powered by Perl