Difference between revisions of "XBio:D Javascript Library Reference"

Latest revision as of 19:33, 22 July 2015

Introduction

The xBio:D JavaScript library offers the functionality to create rich, dynamic, and interactive features for use with the OJ_Break API. The OJ_Break API provides procedures to retrieve data within the xBio:D database, and the xBio:D JS library is how that data gets presented. Users planning on working with the xBio:D JS library should be familiar with JavaScript programming and object-oriented programming.

API Access

All functionality in the xBio:D JS library depends on access of data from the OJ_Break API. See OJ_Break API Access for an overview of the API and how to obtain an API access key.

Example

An easy way to become familiar with the xBio:D JS library is to see a simple example of a web application which uses two xBio:D methods. The first is a Google Maps widget which takes data from the OJ_Break method getLocalities for a specified tnuid and displays the data onto an interactive map. Read more about the Google Maps JavaScript API. The second method used in the example is a listing of included taxa for a specified tnuid by using the OJ_Break method getIncludedTaxa.

Simple example of web application.

There are a few things to note about this example:

The <!DOCTYPE html> tag is necessary for HTML 5 applications (line 1)
Jquery 1.8 library is included with a <script> tag (line 7)
Jquery UI 1.10.4 library is included with a <script> tag (line 8)
The Google Map API JavaScript library is included with a <script> tag (line 9)
The xBio:D JS library is included with a <script> tag (line 10)
A function called loader intializes the xBio:D resources when the web page has finished loading (line 15)
Two objects where created to access the xBio:D components called visual and taxon (line 22 - 23)
The applications are created by calling there respective methods via the xBio:D library components (line 26 & 29 - 30)
In the <body> there are two <div> elements which create areas to hold the widgets. The first is called map_id and the second is included_id. (line 43 - 44)

These steps will be explained below.

Declaring Application as HTML 5

It is recommended for any web application to be declared as a true DOCTYPE. This can easily be done by using the HTML 5 DOCTYPE as seen below. This allows the application to be more cross-browser compliant. Please refer to the Google Maps Documentation on HTML 5 for more info.

<!DOCTYPE html>

Loading JQuery Library

<script type="text/javascript" src="http://ajax.googleapis.com/ajax/libs/jquery/1.8/jquery.min.js"></script>

The URL in the <script> tag above is the location of the JavaScript file which allows JQuery 1.8 to run on the web application. JQuery is used in the xBio:D JS library to get methods from the OJ_Break API and other scripts. It is a necessary component of any web app that intends to use xBio:D functionality.

Loading the Google Maps API

<script type="text/javascript" src="https://maps.googleapis.com/maps/api/js?sensor=false"></script>

The URL in the <script> tag above is the location of the JavaScript file which will load all the necessary defintions to allow access to the Maps API. Normally, an access key would need to be provided in order to use the Maps library. See Loading the Maps API for more info. This script file is necessary for web apps that use Google Maps as part of the application. It is a necessary file to have in this simple example, but is not required for all xBio:D applications.

Loading the xBio:D JavaScript Library

<script type="text/javascript" src="http://xbiod.osu.edu/xbiod_lib/xbiod.js"></script>

The URL in the <script> tage above is the location of the xBio:D JavaScript Library which is a required file for this simple example and any web application that will be using xBio:D applications.

Initializing the xBio:D JS Library

<script>
    // Call the loader for the current page
    $(document).ready(loader);

        function loader() {

            // Initialize xBio:D library
            xbiod.init(['visual','taxon'], /*API_KEY*/, function(){

To begin using the xBio:D library, first the components need to be loaded. This is done through the xBio:D init function which takes three parameters: an array of the components to be loaded, an API access key, and a callback function. In this example, the visual and taxon resources are passed to the init function for loading (all resources and their methods can be found in the Reference section below). This example also shows where a user would provide an OJ_Break API access key. See OJ_Break API Access for more information on access keys. Lastly, a callback method needs to be provided which will create the component objects.

Component Objects

// Load xBio:D components
var visual = new xbiod.visual();
var taxon = new xbiod.taxon();

An object derived from a class is instatiated using the new keyword and a namespace's constructor. The JavaScript namespace that represents the xBio:D visual applications is the visual namespace/component and similarly the namespace that represents the xBio:D taxon applications is the taxon namespace/component. Access to functionality from either of these components requires an object with a reference to that component. These objects allow methods from each component to be called to the web page.

Calling Application Methods

// Load map
visual.showGoogleMap('map_id', tnuid);
		
// Load included taxa
taxon.showIncludedTaxa('included_id', tnuid, {show_num_spms: 'Y', taxonFormat: '<a href="test.html?tnuid=%tnuid%">%taxon%</a> %author% - %num_spms%'});

Each application has a method associated with it which takes several parameters which will dictate what data it loads, where it will be contained, and options for how it should be presented. These methods and requirements can be found in the Reference section.

In the above example, the visual method showGoogleMap gets passed a <div> element ID string which decides where it will be contained and a tnuid which will dictate which taxon data the map will locate.

The taxon method showIncludedTaxa gets passed similar parameters (a specified <div> element ID string and a tnuid) however it also gets additional options in the form of a JavaScript object literal. In this example, the option show_num_spms is given the Boolean_flag 'Y' signifying that the application should display the number of specimens for that particular taxon and taxonFormat is assigned to present the data as links using the <a> tag.

Element Containers

Each method requires one or more unique <div> tag IDs as string parameters (seen in the example <body> below). This will be used to specify where the resource will be contained in the web page.

<body>
    <div id="map_id"/>
    <div id="included_id"/>
</body>

Reference

Agent

showAgentInfo

Description

Displays information about an agent, including name, contact information, and a short biography.

Parameters

element_id (?)
agent_id
options

Options

widget_options - Object

showAgentOccurrences

Description

Displays collected occurrences for a specified agent on a Google Map. Creates two windows.

Parameters

element_id (?)
agent_id (?)
options

Options

info_element_id - ID String (defaults to element_id parameter)
generalFormat - HTML String
markers - String ('spiderfy' or undefined). Requires additional dependencies (see below).
offset - Number
limit - Number
icons - Object
widget_options

Additional Requirements

showAgentOccurrenceLocalityInfo

Description

Displays locality information for a certain agent's collecting occurrence.

Parameters

element_id (?)
loc_id (?)
options

Options

None

showDescribedTaxa

Description

Displays all taxa described by the specified agent.

Parameters

element_id (?)
author_id (?)
options

Options

taxonFormat - String
useTaxonItalics - Boolean
limit - Number
offset - Number
widget_options - Object

showPublications

Description

Displays all publications for a specified agent.

Parameters

element_id (?)
author_id (?)
options

Options

limit - Number
offset - Number
widget_options - Object

Occurrence

showBiologicalInfo

Description

Displays both the habitat and associations for a selected occurrence identifier.

Parameters

element_id (?)
occurrence_id (?)
options

Options

widget_options - Object

showOccurrenceInfo

Description

Displays collecting trip info for a specified occurrence.

Parameters

element_id (?)
occurrence_id (?)
options

Options

widget_options - Object

showDeterminations

Description

Displays determinations for a specified occurence.

Parameters

element_id (?)
occurrence_id (?)
options

Options

widget_options - Object

showLocalityInfo

Description

Displays locality info for a specified occurrence.

Parameters

element_id (?)
occurrence_id (?)
options

Options

widget_options - Object

showSpecimenInfo

Description

Displays specimen info for a specified occurrence.

Parameters

element_id (?)
occurrence_id (?)
options

Options

widget_options - Object

Search

showSearch

Description

A JQuery UI autocomplete search bar which can search for taxa, occurrences, institutions, agents, journals, localities, and places.

Parameters

element_id
options

Options

search - the type of search to execute. Controls the passing of URL parameters to methods. Can be specified a either 'id' or 'name'. Defaults to 'id'
domains - array of the below object elements
- type - a domain keyword for which data gets searched for
- handler_url - a URL that will be passed the ID of the selected type option

Additional Information

Category Options Formatting

Below is an example of how the categories should be input:

// Load search
search.showSearch('search_id', {domains: [{type: 'taxon', handler_url: 'http://domain.url/index.html'}, {type: 'occurrence', handler_url: 'http://domain.url/occurrence.html'}]});

Taxon

showAssociations

Description

Displays all associations for a specified taxon.

Parameters

element_id
tnuid
options

Options

basic_only - Boolean_flag
limit - Number
offset - Number
widget_options

showInstitutions

Description

Displays institutions for which specimens of the selected taxon level belong.

Parameters

element_id
tnuid
options

Options

limit - Number
offset - Number
widget_options - Object

showContributors

Description

Displays all contributing agents related to the occurrence, taxonomy, literature, and media of a taxon.

Parameters

element_id
tnuid
options

Options

inst_id
widget_options

showDeterminers

Description

Displays determiners for a specified taxon.

Parameters

element_id
tnuid
options

Options

limit - Number
offset - Number
inst_id
widget_options

showHabitats

Description

Displays all identified habitats for a selected taxon.

Parameters

element_id
tnuid
options

Options

limit - Number
offset - Number
widget_options

showIncludedTaxa

Description

Displays taxa directly included within a taxon but not synonymous with it.

Parameters

element_id
tnuid
options

Options

inst_id
show_syns
show_fossiles
types_only
useTaxonItalics - Boolean
limit - Number
offset - Number
widget_options

showLiterature

Description

Displays relevent publications for a specified taxon with links to the literature when available.

Parameters

element_id
tnuid
options

Options

show_children - Boolean_flag
show_bib - Boolean_flag
useTaxonItalics - Boolean
limit - Number
offset - Number
widget_options

showSubordinateTaxa

Description

Displays the count of valid taxa levels available below the current taxon rank.

Parameters

element_id
tnuid
options

Options

inst_id
widget_options

showSynonyms

Description

Displays all taxa which are objectively or subjectively synonymous with a selected taxon.

Parameters

element_id
tnuid
options

Options

show_fossils
useTaxonItalics - boolean
limit - Number
offset - Number
widget_options

showTaxonMedia

Description

Displays a table of all media associated to a specific taxon rank.

Parameters

element_id
tnuid
options

Options

inst_id
row_count - Number
media_type
limit - Number
offset - Number
widget_options

showTypes

Description

Displays information and specimen types for a specified taxon.

Parameters

element_id
tnuid
options

Options

show_children
inst_id
primary_only - Boolean_flag
basic_only - Boolean_flag
offset - number
limit - number
useTaxonItalics - boolean
widget_options

Visual

showGoogleMap

Description

A Google map which displays locality markers for a specified taxon.

Parameters

element_id (?)
tnuid (?)
options

Options

place_id - Number
inst_id - Number
use_sex_icons - Boolean_flag
show_children - Boolean_flag
limit - Number
offset - Number
markers - Number
widget_options - Object

Additional Requirements

showTaxonHierarchy

Description

An interactive, tree-based animation which allows a user to navigate through a selected taxon's hierarchy and all taxa available through the OJ_Break API.

Parameters

element_id (?)
tnuid (?)
requestedNode
options

Options

show_num_spms - Boolean_flag
inst_id - Number
show_syns - Boolean_flag
show_fossils - Boolean_flag
types_only - Boolean_flag
nodeColor - string or hexadecimal number
backgroundColor - string or hexadecimal number
handler_url - File path string/URL
size - JavaScript object with two string properties:
- width - either a number or string in pixels
- height - either a number of string in pixels
imagePath - string of relative path to a folder containing necessary images.
widget_options - Object

Additional Requirements

Processing.js 1.4.1+
Pass requestedNode parameter a value of null when calling function. See below:

// Load taxon hierarchy
visual.showTaxonHierarchy('canvas_id', tnuid, null, { /*options*/ });

Additional Information

URL Handler Option

The handler_url option can be used to allow the nodes to have links attached to them, so that a user may follow the link for more information on that specific taxon.

// Load taxon hierarchy
visual.showTaxonHierarchy('canvas_id', tnuid, null, {nodeColor: 'cyan', backgroundColor: '#FFFFFF', handler_url: 'http://hol.osu.edu/index.html'});

In this example, a default web page URL is given (note the use of http:// at the beginning). When provided a URL, the taxon hierachy animation will present a link button to the top right of the node that is currently being highlighted (see image below). This link will not be present if a URL is not specified. If this button is clicked, the handler_url link will be followed.

Size Option

The taxon hierarchy application can be resized in one of two ways: via CSS (preferred) or by inputting the dimensions of the HTML canvas into the API method call as options. One way this can be done is by specifying the width and height as numbers:

// Load taxon hierarchy
visual.showTaxonHierarchy('canvas_id', tnuid, null, {size: {width: 300, height: 900}});

The dimensions of the canvas can also be input as pixels:

// Load taxon hierarchy
visual.showTaxonHierarchy('canvas_id', tnuid, null, {size: {width: "300px", height: "900px"}});

Both of these methods (CSS and parameter passing) are valid, but they should never both be used at the same time since unexpected errors may occur.

Image Path Option

Due to security restrictions, Processingjs is limited in its function to request images. As a consequence, any user wishing to use the animation must have copies of the required images available locally on their server. To access these images, a relative directory path must be input in the form of a optional parameter. The call may look something like this:

// Load taxon hierarchy
visual.showTaxonHierarchy('canvas_id', tnuid, null, {imagePath: "media/images/"});

Portions of this page are modifications based on work created and shared by Google and used according to terms described in the Creative Commons 3.0 Attribution License.

@@ Line 11: / Line 11: @@
 An easy way to become familiar with the xBio:D JS library is to see a simple example of a web application which uses two xBio:D methods. The first is a Google Maps widget which takes data from the OJ_Break method [[OJ_Break API Reference#getLocalities|getLocalities]] for a specified [[OJ_Break API Data Type Glossary#tnuid_2|tnuid]] and displays the data onto an interactive map. Read more about the [https://developers.google.com/maps/documentation/javascript/tutorial Google Maps JavaScript API]. The second method used in the example is a listing of included taxa for a specified tnuid by using the OJ_Break method [[OJ_Break API Reference#getIncludedTaxa|getIncludedTaxa]].
-<!--[[File:Xbiodjslib.png|alt=source code for a simple xBio:D web application.|Simple example of web application.]]-->
+[[File:wiki-test.png|alt=source code for a simple xBio:D web application.|Simple example of web application.]]
-<span style="color:purple"><!DOCTYPE HTML></span>
+<!--  1 <span style="color:purple"><!DOCTYPE HTML></span>
 <span style="color: blue"><html></span>
 <span style="color: blue"><head></span>
@@ Line 57: / Line 57: @@
     <span style="color: blue"><div </span><span style="color: purple">id</span>=<span style="color: green">"included_id"</span><span style="color: blue">/></span>
 <span style="color: blue"></body></span>
-<span style="color: blue"></html></span>
+<span style="color: blue"></html></span>-->
@@ Line 91: / Line 91: @@
 === Loading the xBio:D JavaScript Library ===
-  <span style="color: blue"><script </span><span style="color: purple">type</span>=<span style="color: green">"text/javascript"</span> <span style="color: purple">src</span>=<span style="color: green"><nowiki>"http://osuc.biosci.ohio-state.edu/JSLib/xbiod_lib/xbiod.js"</nowiki></span><span style="color: blue">></script></span>
+  <span style="color: blue"><script </span><span style="color: purple">type</span>=<span style="color: green">"text/javascript"</span> <span style="color: purple">src</span>=<span style="color: green"><nowiki>"http://xbiod.osu.edu/xbiod_lib/xbiod.js"</nowiki></span><span style="color: blue">></script></span>
 The URL in the '''<script>''' tage above is the location of the xBio:D JavaScript Library which is a required file for this simple example and any web application that will be using xBio:D applications.
@@ Line 110: / Line 110: @@
   <span style="color: blue">var</span> taxon = <span style="color: red">new</span> xbiod.taxon();
-An object derived from a namespace is instatiated using the '''new''' keyword and a namespace's constructor. The JavaScript namespace that represents the xBio:D visual applications is the '''visual''' namespace/component and similarly the namespace that represents the xBio:D taxon applications is the '''taxon''' namespace/component. Access to functionality from either of these components requires an object with a reference to that component. These objects allow methods from each component to be called to the web page.
+An object derived from a class is instatiated using the '''new''' keyword and a namespace's constructor. The JavaScript namespace that represents the xBio:D visual applications is the '''visual''' namespace/component and similarly the namespace that represents the xBio:D taxon applications is the '''taxon''' namespace/component. Access to functionality from either of these components requires an object with a reference to that component. These objects allow methods from each component to be called to the web page.
 ==== Calling Application Methods ====
@@ Line 156: / Line 156: @@
 * info_element_id - ID String (defaults to element_id parameter)
 * generalFormat - HTML String
-* markers - String ('spiderfy' or 'cluster')
+* markers - String ('spiderfy' or undefined). Requires additional dependencies (see below).
 * offset - Number
 * limit - Number
 * icons - Object
 * widget_options
 ===== Additional Requirements =====
 * [https://developers.google.com/maps/documentation/javascript/ Google Maps API v3]
-* [http://google-maps-utility-library-v3.googlecode.com/svn/trunk/markerclusterer/docs/reference.html MarkerClusterer]
 * [https://github.com/jawj/OverlappingMarkerSpiderfier Overlapping Marker Spiderfier]
@@ Line 205: / Line 205: @@
 ==== showBiologicalInfo ====
 ===== Description =====
-Displays both the habitat and associations for a selected occurrence identifier (cuid).
+Displays both the habitat and associations for a selected occurrence identifier.
 ===== Parameters =====
@@ Line 212: / Line 212: @@
 * options
 ===== Options =====
-* widget_options - string
+* widget_options - Object
 ==== showOccurrenceInfo ====
@@ Line 253: / Line 253: @@
 ===== Options =====
 * widget_options - Object
 === Search ===
 ==== showSearch ====
 ===== Description =====
-A JQuery UI autocomplete search bar which can search for taxa, cuids, institutions, agents, journals, organizations, collecting methods, localities, and places.
+A JQuery UI autocomplete search bar which can search for taxa, occurrences, institutions, agents, journals, localities, and places.
 ===== Parameters =====
 * element_id
@@ Line 265: / Line 265: @@
 ===== Options =====
 * search - the type of search to execute. Controls the passing of URL parameters to methods. Can be specified a either 'id' or 'name'. Defaults to 'id'
-* category - array of the below object elements
+* domains - array of the below object elements
-** type - a category keyword that will control which data gets searched for
+** type - a domain keyword for which data gets searched for
 ** handler_url - a URL that will be passed the ID of the selected type option
@@ Line 274: / Line 274: @@
   <span style="color:green;">// Load search</span>
-  search.showSearch(<span style="color:green">'search_id'</span>, {category: [{type: <span style="color: green">'taxa'</span>, handler_url: <span style="color: green">'<nowiki>http://hol.osu.edu/index.html</nowiki>'</span>}, {type: <span style="color: green">'cuids'</span>, handler_url: <span style="color: green">'<nowiki>http://hol.osu.edu/spmInfo.html</nowiki>'</span>}]});
+  search.showSearch(<span style="color:green">'search_id'</span>, {domains: [{type: <span style="color: green">'taxon'</span>, handler_url: <span style="color: green">'<nowiki>http://domain.url/index.html</nowiki>'</span>}, {type: <span style="color: green">'occurrence'</span>, handler_url: <span style="color: green">'<nowiki>http://domain.url/occurrence.html</nowiki>'</span>}]});
-====== Valid Category Keywords ======
-Below is a list of available category keywords that the ''category'' array option can take (Note: the keyword spelling must match exactly what is seen below):
-* '''all'''
-* '''taxa'''
-* '''cuids'''
-* '''inst'''
-* '''agents'''
-* '''journals'''
-* '''orgs'''
-* '''coll_methods'''
-* '''locs'''
-* '''places'''
 === Taxon ===
@@ Line 294: / Line 281: @@
 Displays all associations for a specified taxon.
 ===== Parameters =====
-* element_id ([[xBio:D Javascript Library Reference#Element_Containers|?]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
-* tnuid ([[OJ_Break API Data Type Glossary#tnuid_2|?]])
+* tnuid
 * options
 ===== Options =====
@@ Line 307: / Line 294: @@
 Displays institutions for which specimens of the selected taxon level belong.
 ===== Parameters =====
-* element_id ([[xBio:D Javascript Library Reference#Element_Containers|?]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
-* tnuid ([[OJ_Break API Data Type Glossary#tnuid_2|?]])
+* tnuid
 * options
 ===== Options =====
 * limit - Number
 * offset - Number
-* widget_options
+* widget_options - Object
 ==== showContributors ====
@@ Line 319: / Line 306: @@
 Displays all contributing agents related to the occurrence, taxonomy, literature, and media of a taxon.
 ===== Parameters =====
-* ([[xBio:D Javascript Library Reference#Element_Containers|element_id]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
 * tnuid
 * options
@@ Line 330: / Line 317: @@
 Displays determiners for a specified taxon.
 ===== Parameters =====
-* element_id ([[xBio:D Javascript Library Reference#Element_Containers|?]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
-* tnuid ([[OJ_Break API Data Type Glossary#tnuid_2|?]])
+* tnuid
 * options
 ===== Options =====
@@ Line 343: / Line 330: @@
 Displays all identified habitats for a selected taxon.
 ===== Parameters =====
-* ([[xBio:D Javascript Library Reference#Element_Containers|element_id ]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
 * tnuid
 * options
@@ Line 355: / Line 342: @@
 Displays taxa directly included within a taxon but not synonymous with it.
 ===== Parameters =====
-* ([[xBio:D Javascript Library Reference#Element_Containers|element_id]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
 * tnuid
 * options
@@ Line 372: / Line 359: @@
 Displays relevent publications for a specified taxon with links to the literature when available.
 ===== Parameters =====
-* ([[xBio:D Javascript Library Reference#Element_Containers|element_id]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
 * tnuid
 * options
@@ Line 387: / Line 374: @@
 Displays the count of valid taxa levels available below the current taxon rank.
 ===== Parameters =====
-* ([[xBio:D Javascript Library Reference#Element_Containers|element_id]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
 * tnuid
 * options
@@ Line 398: / Line 385: @@
 Displays all taxa which are objectively or subjectively synonymous with a selected taxon.
 ===== Parameters =====
-* ([[xBio:D Javascript Library Reference#Element_Containers|element_id]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
 * tnuid
 * options
@@ Line 412: / Line 399: @@
 Displays a table of all media associated to a specific taxon rank.
 ===== Parameters =====
-* ([[xBio:D Javascript Library Reference#Element_Containers|element_id]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
 * tnuid
 * options
@@ Line 427: / Line 414: @@
 Displays information and specimen types for a specified taxon.
 ===== Parameters =====
-* ([[xBio:D Javascript Library Reference#Element_Containers|element_id]])
+* [[xBio:D Javascript Library Reference#Element_Containers|element_id]]
 * tnuid
 * options
@@ Line 449: / Line 436: @@
 * options
 ===== Options =====
-* pnids ([[OJ_Break API Data Type Glossary#pnid_2|?]]) - array of number
+* place_id - Number
-* inst_id ([[OJ_Break API Data Type Glossary#inst_id_2|?]])
+* inst_id - Number
-* precDecimals ([[OJ_Break API Data Type Glossary#precDecimals|?]])
+* use_sex_icons - Boolean_flag
-* showChildren ([[OJ_Break API Data Type Glossary#showChildren|?]])
+* show_children - Boolean_flag
+* limit - Number
+* offset - Number
+* markers - Number
+* widget_options - Object
 ===== Additional Requirements =====
 * [https://developers.google.com/maps/documentation/javascript/ Google Maps API v3]
+* [https://github.com/jawj/OverlappingMarkerSpiderfier Overlapping Marker Spiderfier]
 ==== showTaxonHierarchy ====
@@ Line 467: / Line 459: @@
 ===== Options =====
-* show_num_spms ([[OJ_Break API Data Type Glossary#show_num_spms|?]])
+* show_num_spms - Boolean_flag
-* inst_id ([[OJ_Break API Data Type Glossary#inst_id_2|?]])
+* inst_id - Number
-* showSyns ([[OJ_Break API Data Type Glossary#showSyns|?]])
+* show_syns - Boolean_flag
-* showFossils ([[OJ_Break API Data Type Glossary#showFossils|?]])
+* show_fossils - Boolean_flag
-* typesOnly ([[OJ_Break API Data Type Glossary#typesOnly|?]])
+* types_only - Boolean_flag
 * nodeColor - string or hexadecimal number
 * backgroundColor - string or hexadecimal number
-* handler_url - URL string
+* handler_url - File path string/URL
 * size - JavaScript object with two string properties:
 ** width - either a number or string in pixels
 ** height - either a number of string in pixels
 * imagePath - string of relative path to a folder containing necessary images.
+* widget_options - Object
 ===== Additional Requirements =====
@@ Line 487: / Line 480: @@
 ===== Additional Information =====
-====== Valid Color Options ======
-Below is a list of the available colors that can be used as the background or node color:
-* red
-* scarlet
-* orange
-* yellow
-* green
-* blue
-* cyan
-* violet
-* purple
-* grey/gray
-* white
-NOTE: any color (that is, not limited to the above list) can be chosen by specifying its hexadecimal color string (for example, #70CFF5).
 ====== URL Handler Option ======
 The ''handler_url'' option can be used to allow the nodes to have links attached to them, so that a user may follow the link for more information on that specific taxon.
@@ Line 510: / Line 487: @@
 In this example, a default web page URL is given (note the use of http:// at the beginning). When provided a URL, the taxon hierachy animation will present a link button to the top right of the node that is currently being highlighted (see image below). This link will not be present if a URL is not specified. If this button is clicked, the ''handler_url'' link will be followed.
-[[File:link_button_tut.png|none|frame|Link button present on highlighted node. This button would not be present if handler_url option was not specified.]]
 ====== Size Option ======

Difference between revisions of "XBio:D Javascript Library Reference"

Latest revision as of 19:33, 22 July 2015

Contents

API Access

Example

Declaring Application as HTML 5

Loading JQuery Library

Loading the Google Maps API

Loading the xBio:D JavaScript Library

Initializing the xBio:D JS Library

Component Objects

Calling Application Methods

Element Containers

Reference

Agent

showAgentInfo

Description

Parameters

Options

showAgentOccurrences

Description

Parameters

Options

Additional Requirements

showAgentOccurrenceLocalityInfo

Description

Parameters

Options

showDescribedTaxa

Description

Parameters

Options

showPublications

Description

Parameters

Options

Occurrence

showBiologicalInfo

Description

Parameters

Options

showOccurrenceInfo

Description

Parameters

Options

showDeterminations

Description

Parameters

Options

showLocalityInfo

Description

Parameters

Options

showSpecimenInfo

Description

Parameters

Options

Search

showSearch

Description

Parameters

Options

Additional Information

Category Options Formatting

Taxon

showAssociations

Description

Parameters

Options

showInstitutions

Description

Parameters

Options

showContributors

Description

Parameters

Options

showDeterminers

Description

Parameters