Changes between Initial Version and Version 1 of MindSeer_Plugin_File


Ignore:
Timestamp:
05/08/06 16:23:24 (13 years ago)
Author:
trac
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • MindSeer_Plugin_File

    v1 v1  
     1== Version 1.0 == 
     2The comments are inline, a DTD or schema does not exist yet. 
     3 
     4== Recurring Attributes == 
     5 * ''class'' refers to a fully qualified Java class name that can be found on the class path. 
     6 * ''name'' refers to a human readable name that should uniquely identify the object. 
     7 * ''file'' refers to either a full URL to the file, or a relative URL that can be found with {{{ClassLoader.getResource(file)}}}. 
     8 * ''ident'' refers to an identifier for referencing the object from within the config files and MindSeer. 
     9 * When refering to another object within this file, the common form is lower case tag name = ident (i.e. {{{viewport=ident}}}). 
     10 
     11== File == 
     12{{{ 
     13<?xml version="1.0" encoding="UTF-8"?> 
     14<MindSeer version="1.0"> 
     15        <!--The order to define nodes in is important: 
     16                1. Types and TypeGroups 
     17                2. Template or View or ViewPort 
     18                3. ViewMapping 
     19                 
     20                Info nodes can go anywhere. 
     21        --> 
     22        <!--Types can either be part of a group or independent.  TypeGroups 
     23            have a human readable name and an ident that is used to refer 
     24            to it regardless of language or terminology.   
     25            Likewise, the type has a name and ident, but it also has the 
     26            class that generates it and a preference (pref).  The 
     27            preference is a number from 1 to 3.  The most preferred type 
     28            for a group should be "1" (an encoder must also be defined). 
     29            "2" signifies that the type is acceptable and there is 
     30            particularly good or bad about it. 
     31            "3" means that the type is discouraged.  For some reason it is  
     32            not as efficient or expressive as a preferred or acceptable 
     33            type. 
     34            The optional "creatable" flag defaults to false, but signals to 
     35            MindSeer that an blank file of this type can be created out of 
     36            thin air.  If a type is not encodable or requires any special 
     37            steps to create, then it should not be creatable. 
     38        --> 
     39        <TypeGroup name="Surface" ident="Surface"> 
     40                <Type name="SPM Surface" ident="SPMSurface" class="edu.washington.biostr.sig.brainj3d.model.MatModelType" pref="3"/> 
     41                <Type name="OBJ Surface" ident="ObjSurface" class="edu.washington.biostr.sig.brainj3d.model.ObjFileType" pref="3"/> 
     42                <Type name="OFF Surface" ident="OFFSurface" class="edu.washington.biostr.sig.brainj3d.model.geomview.OFFModelType" pref="1"/> 
     43        </TypeGroup> 
     44        <TypeGroup name="Volume" ident="Volume"> 
     45                <Type name="Minc Volume" ident="Minc" class="edu.washington.biostr.sig.brainj3d.volume.MincFileType" pref="2"/> 
     46                <Type name="Analyze Volume" ident="Analyze" class="edu.washington.biostr.sig.brainj3d.volume.AnalyzeFileType" pref="2"/> 
     47        </TypeGroup> 
     48        <TypeGroup name="Labels" ident="Map"> 
     49                <Type name="Labels" ident="xmlMap" class="edu.washington.biostr.sig.brainj3d.map.XMapType" creatable="true" pref="1"/> 
     50                <Type name="Skandha Labels" ident="OldMap" class="edu.washington.biostr.sig.brainj3d.map.OldMapType" pref="2"/> 
     51        </TypeGroup> 
     52        <Type name="Image" ident="Image" class="edu.washington.biostr.sig.brainj3d.image.ImageType"/> 
     53        <Type name="Plain Text" ident="PlainText" class="edu.washington.biostr.sig.brainj3d.plugin.plaintext.PlainTextType"/> 
     54        <Type name="Workspace" ident="Workspace" class="edu.washington.biostr.sig.brainj3d.core.files.WorkspaceType" creatable="true"/> 
     55 
     56        <!--Templates are used to create new subtrees in the workspace (vault). 
     57            There are also user templates which are discovered automatically from 
     58            the user directory. 
     59        --> 
     60        <Template file="resources/templates/Coordinate Space.tree.xml"/> 
     61        <Template file="resources/templates/Subject.tree.xml"/> 
     62        <Template file="resources/templates/Modality.tree.xml"/> 
     63 
     64        <!--A view specifies a mapping between a class of Data (data) and 
     65            a DataView (class). 
     66        --> 
     67        <View class="edu.washington.biostr.sig.brainj3d.view3D.IndexedSurface3DView"  
     68                data="edu.washington.biostr.sig.brainj3d.model.IndexedModel3DData"/> 
     69        <View class="edu.washington.biostr.sig.brainj3d.view3D.BranchGroupSurface3DView"  
     70                data="edu.washington.biostr.sig.brainj3d.model.SharedGroupData"/> 
     71        <View class="edu.washington.biostr.sig.brainj3d.view.ImageView"  
     72                data="edu.washington.biostr.sig.brainj3d.image.ImageData"/> 
     73        <View class="edu.washington.biostr.sig.brainj3d.viewvolume.VolumeDataView"  
     74                data="edu.washington.biostr.sig.brainj3d.volume.VolumeData"/> 
     75        <View class="edu.washington.biostr.sig.brainj3d.view3D.VolumeSurface3DView"  
     76                data="edu.washington.biostr.sig.brainj3d.volume.VolumeData"/> 
     77        <View class="edu.washington.biostr.sig.brainj3d.view3D.MapSurface3DView"  
     78                data="edu.washington.biostr.sig.brainj3d.map.LabelData"/> 
     79        <View class="edu.washington.biostr.sig.brainj3d.viewvolume.MapVolumeView"  
     80                data="edu.washington.biostr.sig.brainj3d.map.LabelData"/> 
     81        <View class="edu.washington.biostr.sig.brainj3d.map.LabelDataView"  
     82                data="edu.washington.biostr.sig.brainj3d.map.LabelData"/> 
     83        <View class="edu.washington.biostr.sig.brainj3d.plugin.plaintext.PlainTextView"  
     84                data="edu.washington.biostr.sig.brainj3d.plugin.plaintext.PlainTextData"/> 
     85 
     86        <!--View Ports specify the displayable name (name), the identifier 
     87            used in configuration files (ident) and the class (class). 
     88            Additionally, they may have 2 kinds of controls specified 
     89            beneath them: ViewControl (which should control the view) and 
     90            AdvancedControl (which is not a data, appearance or view  
     91            control). 
     92            These have the same format.  They just require the human  
     93            displayable name (name) and the class (class). 
     94        --> 
     95        <ViewPort name="Surface ViewPort" ident="SurfaceVP" class="edu.washington.biostr.sig.brainj3d.view3D.Model3DViewPort"> 
     96                <ViewControl name="Viewing Angle" class="edu.washington.biostr.sig.brainj3d.view3D.Focus3DController"/> 
     97                <ViewControl name="Wedge" class="edu.washington.biostr.sig.brainj3d.view3D.CutawayController"/>          
     98        </ViewPort> 
     99        <ViewPort name="Image ViewPort" ident="ImageVP" class="edu.washington.biostr.sig.brainj3d.view.ImageViewPort"/> 
     100        <ViewPort name="Slice ViewPort" ident="SliceVP" class="edu.washington.biostr.sig.brainj3d.viewvolume.VolumeViewPort"> 
     101                <ViewControl name="Volume Order" class="edu.washington.biostr.sig.brainj3d.viewvolume.VolumeOrder"/> 
     102        </ViewPort> 
     103        <ViewPort name="Label ViewPort" ident="LabelVP" class="edu.washington.biostr.sig.brainj3d.view.MapViewPort"/> 
     104        <ViewPort name="Text ViewPort" ident="PlainTextVP" class="edu.washington.biostr.sig.brainj3d.plugin.plaintext.PlainTextViewPort"/> 
     105 
     106        <!--View Mappings specify the default ViewPort for a given type. 
     107            These are required for each type. They are kept separate  
     108            because they should be set independently of the type and  
     109            viewport.     
     110        --> 
     111        <ViewMapping type="OFFSurface" viewport="SurfaceVP"/> 
     112        <ViewMapping type="ObjSurface" viewport="SurfaceVP"/> 
     113        <ViewMapping type="SPMSurface" viewport="SurfaceVP"/> 
     114        <ViewMapping type="Minc" viewport="SliceVP"/> 
     115        <ViewMapping type="Analyze" viewport="SliceVP"/> 
     116        <ViewMapping type="xmlMap" viewport="LabelVP"/> 
     117        <ViewMapping type="OldMap" viewport="LabelVP"/> 
     118        <ViewMapping type="Image" viewport="ImageVP"/> 
     119        <ViewMapping type="PlainText" viewport="PlainTextVP"/> 
     120 
     121        <!--Info nodes contain other info in a  
     122            key (which is unique)->value mapping. 
     123            A mapping for "help" is required so that MindSeer can find the 
     124            user help documentation. 
     125        --> 
     126        <Info key="help" value="user"/> 
     127</MindSeer> 
     128}}}