EditLive! 9 Documentation : customMenuItem (Applet)

This element specifies the properties for a developer-defined custom menu item for use within EditLive!. 

Configuration Element Tree Structure

<editLive>
<menuBar>
<menu>
<customMenuItem (Applet)>

<editLive>
    ...
     <menuBar>
          ...
          <menu>
               <customMenuItem... />
          </menu>
          ...
     </menuBar>
     ...
</editLive>

Required Attributes

name

The name which uniquely defines this custom menu item.

text

The text to place on the menu for this item.

action

The action which this custom action performs. This attribute has the following possible values:

• insertHTMLAtCursor - Insert the given HTML at the cursor.
• insertHyperlinkAtCursor - Insert the given hyperlink at the cursor.
• raiseEvent - Call a JavaScript function with the name specified in the value attribute. The function will be called providing the id of the editor that the item was clicked on. This id is the value used in the JavaScript constructor or in the case of inline mode the div id of the editable section.
• customPropertiesDialog - Call a JavaScript function with the name specified in the value attribute. The current tag's properties are also passed to this function as a string.
• PostDocument - Post the content of the applet to a server side script.

For more information on these actions, please see the Creating Custom Menu and Toolbar Items article.

value

The value of this attribute depends on the value specified in the action attribute.

• insertHTMLAtCursor - value will be a string of HTML.
• insertHyperlinkAtCursor - value will be a URL.
• raiseEvent - value will be the name of the JavaScript function to call.
• customPropertiesDialog - value will be the name of the JavaScript function to call, passing the current tag's attributes as a string.
• PostDocument- the value attribute is used to specify several different parameters. Each parameter is delimited with the string ##ephox##. The following are the different parameters that can be specified through the value attribute:

  • Post Field
    The name of the field in the HTTP POST that EditLive! for Java uses to POST its content.

    This parameter is required.

  • Post Acceptor URL
    The URL for the POST acceptor that EditLive! for Java is to POST to.

    This parameter is required.

  • Response Processing
    The operation that EditLive! for Java is to perform with the HTTP response from the POST acceptor script. The parameter can have the following values:
    • saveToDisk - Present the user with a save file dialog, with which they can save the response to the local machine.

    • callback- Pass the entire content of th HTTP response to a specified JavaScript callback function for processing.

      This parameter is required.

  • JavaScript Callback Function
    The name of the JavaScript callback function to use for processing the response.

    This parameter should only be used if the repsonse processing is set to callback.

The parameters specified through the value attribute string must appear in the order Post Field, Post Acceptor URL, Response Processing, and JavaScript Callback Function (if needed).

Example
The following parameters specified through the value attribue string would store the contents of EditLive! in a hidden HTML form field called POST_field, sending the contents via HTTP Post to http://someserver/postacceptor.jsp, then call back the JavaScript function called JSFunction.

value="POST_field##ephox##http://someserver/postacceptor.jsp##ephox## callback##ephox##JSFunction"

Conditional Attributes

enableintag

This attribute defines in which tags the function should be enabled. For example, when set to td the function will be enabled when the cursor is within a <td> tag (i.e. a table cell).

The enableintag attribute is required when using the customPropertiesDialog action. The enableintag attribute will not work with any of the other action attributes.

Optional Attributes

imageURL

The URL of the image to be placed on the menu with the menu item text. The image should be of a .gif format and be a size of sixteen (16) pixels high and sixteen (16) pixels wide. This URL can be relative or absolute. Relative URLs are relative to the location of the page in which EditLive! is embedded.

You can also explicitly set mnemonics and shortcuts for this element using the Mnemonic and Shortcut Attributes.

designViewOnly

This attribute is used to indicate the action is only applicable to the design view of EditLive!. When set to true, the custom button (or menu item) will be disabled when the editor is switched to code view.

The default value is false.

Examples

The following example demonstrates how to define a custom menu item for use within EditLive!. The menu item defined in this example will insert HTML at the cursor. Note that the value in the example below is URL encoded.

<editLive>
    ...
    <menuBar>
        ...
        <menu name="Example">
            <customMenuItem 
                name="customItem1" 
                text="Custom Item" 
                imageURL="http://www.someserver.com/image16x16.gif"
                action="insertHTMLAtCursor" 
                value="%3Cp%3EHTML%20to%20insert%3C/p%3E" />
        </menu>
        ...
    </menuBar>    
    ...
</editLive> 

The following example demonstrates how to define a custom menu item which uses the raiseEvent action for use within EditLive!. The menu item defined in this example will call the JavaScript function called eventRaised. This JavaScript function will show an alert with the text "button clicked on " with the id of the editor when then menu item is clicked.

function eventRaised(id) {
	alert("button clicked on " + id);
}

<editLive>
   ...
   <menuBar>
      ...
      <menu name="ephox_insertmenu">
         <customMenuItem
            name="customItem1"
            text="Raise Event"
            imageURL="http://www.someserver.com/image16x16.gif"
            action="raiseEvent"
            value="eventRaised" />
      </menu>
      ...
   </menuBar>
   ...
</editLive> 

The following example demonstrates how to define a custom menu item which uses the customPropertiesDialog action for use within EditLive!. The menu item defined in this example will call the JavaScript function called DisplayAttributes. This menu item is only available when a <h1> tag is selected.

<editLive>
   ...
   <menuBar>
      ...    
      <menu name="ephox_insertmenu">
            <customMenuItem 
                name="showAttributes"
                text="H1 Properties"
                action="customPropertiesDialog"
                value="DisplayAttributes"
                enableintag="h1"
            />
      </menu>
      ...
   </menuBar>
   ...
</editLive>

For an instance of EditLive! using the <customMenuItem> created above, the following function would create a JavaScript dialog displaying each name-value pair of attributes for the <h1> tag.

function DisplayAttributes(properties)
{
   alert("VALUE-NAME pairs: " + properties);
}

The following example demonstrates how to define a custom menu item which uses the PostDocument action for use within EditLive!. The menu item defined in this example will POST the content in the field editlive_field to the script at http://someserver/post/POSTacceptor.aspx. Upon completion of the POST, the content of the HTTP response will be passed to the JavaScript callback function JSFunction.

<editLive>
   ...
   <menuBar>
      ...
      <menu>
         <customMenuItem
            name="customItem1"
            text="POST Content"
            imageURL="http://www.someserver.com/image16x16.gif"
            action="PostDocument" value="editlive_field##ephox##http://someserver/post/POSTacceptor.aspx ##ephox##callback##ephox##JSFunction" />
      </menu>
      ...
   </menuBar>
   ...
</editLive>

Remarks

The <customMenuItem> element can appear multiple times within the <menu> element.

The <customMenuItem> element must be a complete tag; it cannot contain a tag body. Therefore, the tag must be closed in the same line. See the example below:

<customMenuItem name=... />

Text assigned to the value attribute must be URL encoded as it is in the example above.

See Also

• Encoding Content for Use with EditLive!
• Creating Custom Menu and Toolbar Items