Custom Page: Difference between revisions
No edit summary |
No edit summary |
||
Line 28: | Line 28: | ||
*Internal [[Internal Custom Page]] | *Internal [[Internal Custom Page]] | ||
* External | * External | ||
Line 47: | Line 45: | ||
[[Category:Custom Page]] |
Revision as of 17:49, 25 August 2014
Links
Purpose
The purpose of a user-created mhttpd Custom Web Page is to present the essential parameters of the controlled experiment in a more compact way. A custom page may even replace the default MIDAS Status Page.
Introduction
Custom web pages provide the user with a means of creating secondary user-created web page(s) activated within the standard MIDAS web interface. These custom pages can contain specific links to the ODB for the user to display and/or input information relevant to the experiment using a webpage. The user often creates a Custom Page when the standard pages do not meet his/her requirements completely.
Two ways of implementing custom pages are available:
- Internal Internal Custom Page
- External
- ODB contains links to external html or Javascript document(s).
- Multiple custom pages are supported,
- The page can be edited with an external editor.
External pages are more commonly used, hence most of the examples in this section are those of external pages. All the features described are available for both internal and external pages.
Access a Custom Page
Access to a Custom Page is set up through the /Custom ODB tree. Once a link to the page is added to the /Custom tree, a button will appear on the mhttpd Status Page to access that custom page.
Internal custom webpage
An internal custom webpage is one where the code for the webpage (html/javascript) is imported into the ODB /Custom using the odbedit import command.