An "explore method" is a customization that can be applied to a workspace object to specialize it in some way. Yes, that is a vague definition. More importantly, explore methods provide a way for you to add a custom tab to a workspace object, which you can use to do pretty much anything.

An "explore method" is a customization that can be applied to a workspace object to specialize it in some way. Yes, that is a vague definition. More importantly, explore methods provide a way for you to add a custom tab to a workspace object, which you can use to do pretty much anything.

Explore methods are the things that you access from the Customize tab. I call them explore methods because the Customize tab used to be called the "Explore tab," and all the references in the code still use "explore".

Explore methods are the things that you access from the [[Specialize tab]]. I call them explore methods because the [[Specialize tab]] used to be called the "Explore tab," and all the references in the code still use "explore". (Including that the tab itself is created in exploretab.m)

Explore methods live in the rave\exploremethods\ folder. Just like everything other rave plugin, each explore method goes in its own folder, whose name serves as the KEYWORD. All the files related to the explore method will also contain this KEYWORD, which is how Rave knows which files to use for which purposes.  

Explore methods live in the rave\exploremethods\ folder. Just like everything other rave plugin, each explore method goes in its own folder, whose name serves as the KEYWORD. All the files related to the explore method will also contain this KEYWORD, which is how Rave knows which files to use for which purposes.  

=Required Files=

=Required Files=

Each explore method requires 3 files, but will probably also have several "update" files that run in response to certain user actions.  

Each explore method requires 2 files, but will probably also have several "update" files that run in response to certain user actions and maybe other functions used by your uicontrol callbacks.  

'''Required files:'''

'''Required files:'''

* '''exploreproperties<KEWORD>''' - this is similar to the graphproperties file used by [[workspace objects]], although it contains fewer properties. Note that the properties stored in this file should all be static. You should not add your own properties to this file... those things should be stored in [[the workspace]] object's udata.explore field as described below. This file must contain the following properties:

* '''exploreproperties<KEWORD>''' - this is similar to the graphproperties file used by [[workspace objects]], although it contains fewer properties. Note that the properties stored in this file should all be static. You should not add your own properties to this file... those things should be stored in [[the workspace]] object's udata.explore field as described below. This file must contain the following properties:

**properties.longname = the string that appears in the menu on the Customize tab. This is the name of this method that the user will see.

**properties.longname = the string that appears in the menu on the [[Specialize tab]]. This is the name of this method that the user will see.

**properties.updates = a cell array of strings that lists the [[events and updates]] that trigger an update for this explore method. This list should contain all events that require an update for ANY workspace object, i.e. if the event causes some [[workspace objects]] to require an update, but others to not require an update, the event SHOULD appear in this list.

**properties.updates = a cell array of strings that lists the [[events and updates]] that trigger an update for this explore method. This list should contain all events that require an update for ANY workspace object, i.e. if the event causes some [[workspace objects]] to require an update, but others to not require an update, the event SHOULD appear in this list.