Difference between revisions of "XBio:D Applications"
(Created page with "---- '''xBio:D Applications''' This section provides basic information on the structure of xBio:D web applications and links to pages for each individual application. The a...") |
|||
| (3 intermediate revisions by the same user not shown) | |||
| Line 8: | Line 8: | ||
== Basic Structure == | == Basic Structure == | ||
| + | Each xBio:D web application is built upon a MVC (Model-View-Controller) concept. The model, which contains the data, is located in the xBio:D database and is accessed via xBio:D APIs. Each application tends to have its own API for entering and retrieving application-specific information into the database and uses the OJ_Break API to obtain general information. The view of the applications are the HTML pages and CSS styling that provide a look-and-feel and structure for the data handled by the controller. The controller part is mediated by JavaScript and uses the xBio:D APIs to populate information retrieved from the database into the structure from the HTML pages. Each HTML page has its own JavaScript page that is included on page load. Every application has its own JavaScript page as well that is also included on page load for each page. | ||
== Applications == | == Applications == | ||
| − | * [HOL Application Information] | + | * [[HOL Application Information]] |
| − | * [DEA Application Information] | + | * [[DEA Application Information]] |
| − | * [Database Manager Application Information] | + | * [[Database Manager Application Information]] |
| − | * [vSysLab Application Information] | + | * [[vSysLab Application Information]] |
| − | * [Specimage Application Information] | + | * [[Specimage Application Information]] |
[[Category:OSUC Private]] | [[Category:OSUC Private]] | ||
| + | [[Category:xBio:D Application Info]] | ||
Latest revision as of 16:11, 7 August 2015
xBio:D Applications
This section provides basic information on the structure of xBio:D web applications and links to pages for each individual application. The application pages have information on which server the application is located, the file structure and interactions, and any niche maintenance feature that may be useful.
Basic Structure
Each xBio:D web application is built upon a MVC (Model-View-Controller) concept. The model, which contains the data, is located in the xBio:D database and is accessed via xBio:D APIs. Each application tends to have its own API for entering and retrieving application-specific information into the database and uses the OJ_Break API to obtain general information. The view of the applications are the HTML pages and CSS styling that provide a look-and-feel and structure for the data handled by the controller. The controller part is mediated by JavaScript and uses the xBio:D APIs to populate information retrieved from the database into the structure from the HTML pages. Each HTML page has its own JavaScript page that is included on page load. Every application has its own JavaScript page as well that is also included on page load for each page.
