ASNA Monarch Master Pages

Monarch uses two master page files that contain the JavaScript coding that defines the master page layout with divisions identified by a ContentPlaceHolder ID matching the ContentPlaceHolderID in the ASPX content pages. When an ASPX Content Page is requested, the content is merged with the Master Page, which creates a standardized look and behavior for all the ASPX and windows pages in your solution. The default master pages are located in the installation default location, which is C:\Program Files (x86)\ASNA.Monarch 10.0\Templates\Themes\Current or C:\Program Files\ASNA.Monarch 10.0\Templates\Themes\Current.

MasterPage.master

The Display File agents will use this master page file, MasterPage.master, when displaying ASPX pages. A partial master page example is shown below.

Notice the first ID, HeaderPH. This identifies the place holder for the ASPX page header. The second ID, FKeyPH, identifies an area for function keys. The third and fourth ID's, CenPH and MsgPH, identifies the place for the main contents and a message line. This is where the majority of the individual ASPX content will be displayed for the user. A final placeholder section outside the form, ID PageScriptPH, is for any scripts that may be needed to execute on the page.

// section for header
  <head>
        <asp:ContentPlaceHolder ID="HeaderPH" runat="server" />
  </head>
  <body>
    <form>
// division for function keys
      <div id="Div1" >
          <asp:ContentPlaceHolder ID="FKeyPH" runat="server" />
      </div>

// divisions for main page content and messages          
      <div id="centralDiv" class="CenPH" >
          <asp:ContentPlaceHolder ID="CenPH" runat="server" />
      </div>                  
      <div id="msgDiv" >
          <asp:ContentPlaceHolder ID="MsgPH" runat="server" />
      </div>    
// section outside the form for page script                 
    </form>
         <asp:ContentPlaceHolder ID="PageScriptPH" runat="server" />
  </body>

The master page code-behind file used when your project is created will depend upon the type of project and the language being used; AVR, C#, or Visual Basic. There are three default code-behind files for this master page.

MasterPage.master
MasterPage.master.vr - This is the code-behind page for ASNA Visual RPG language projects.
MasterPage.master.cs - This is the code-behind page for C# language projects.
MasterPage.master.vb - This is the code-behind page for Visual Basic language projects.

MasterPage.Window.master

The Display File agents will switch to use this master page when a DDS Record as a WINDOW is encountered. This is specifically useful on pop-up windows to standardize the layout of the content with the defined element placement and coloring controlled by the Windows Master Page.

This file is very similar to the normal master page above. The content placeholders have a different class, but the content place holder ids are the same as shown below. This allows a content page to be displayed easily by either master page.

MasterPage.master MasterPage.Window.master
Division id Class ContentPH ID Division id Class ContentPH id
None None HeaderPH None None HeaderPH
FunkeyDiv FKeyPH FKeyPH FunkeyDiv FKeyWinPH FKeyPH
centralDiv CenPH CenPH centralDiv CenWinPH CenPH
msgDiv MsgPH MsgPH msgDiv MsgWinPH MsgPH
None None PageScriptPH None None PageScriptPH

The master page code-behind file used when your project is created will depend upon the type of project and the language being used; AVR, C#, or Visual Basic. There are three default code-behind files for this master window page.

MasterPage.Window.master
MasterPage.Window.master.vr – This is the code-behind page for ASNA Visual RPG language projects.
MasterPage.Window.master.cs – This is the code-behind page for C# language projects.
MasterPage.Window.master.vb – This is the code-behind page for Visual Basic language projects.

Next: ASNA Cascading Style Sheets

Previous: ASNA Monarch Templates