XMLmind XML Editor - Configuration and Deployment

Generated when the user drags something other than an drag-source (see Section 15, “drag-source” in XMLmind XML Editor - Support of Cascading Style Sheets (W3C CSS)) in the document view.

	Dragging an object in the document view means: dragging the mouse over the object while keeping the left button and the Alt key pressed.

The command bound to this application event must return a string. This string will be passed as is to the drop target.

By default, XXE uses the following binding:

<binding>
  <appEvent name="drag" />
  <command name="drag" />
</binding>

DITA example: a example of a contextual drag command:

<binding>
  <appEvent name="drag" />
  <command name="dita.drag" />
</binding>

<command name="dita.drag">
  <macro>
    <sequence>
      <!-- Either drag the selection or 
           select+drag the element clicked upon. -->
      <command name="ensureSelectionAt" parameter="selectElement" />

      <choice>
        <sequence>
          <match context="$selectedElement" 
                 pattern="xref[@href]|xref[@href]//*|
                          link[@href]|link[@href]//*|
                          longdescref[@href]|
                          longquoteref[@href]|
                          image[@href]" />
          <set variable="selectedElement" context="$selectedElement"
               expression="(ancestor-or-self::*[@href])[last()]" />
          <get context="$selectedElement" expression="resolve-uri(@href)" />
        </sequence>

        <!-- Default drag action. -->
        <command name="drag" />
      </choice>
    </sequence>
  </macro>
</command>

Generated when the user drops a string in the document view.

If the object dropped from an external application is not a string, this object will be automatically converted to a string. For example, a file is converted to a string by using its absolute filename.

In addition to %{value}, which is substituted with the dropped string, the following convenience variables are also supported:

By default, XXE uses the following binding: (notice how the string is passed to the drop command):

<binding>
  <appEvent name="drop" />
  <command name="drop" parameter="%{value}" />
</binding>

DocBook example: a contextual drop command:

<binding>
  <appEvent name="drop" />
  <command name="docb.drop" parameter="%{value}" />
</binding>

<command name="docb.drop">
  <macro>
    <choice>
      <sequence>
        <pass>
          <match context="$clickedElement" pattern="ulink|ulink//*" />
          <test expression="uri-or-file-name('%*') != ''" />
        </pass>

        <set variable="selectedElement" context="$clickedElement" 
             expression="(ancestor-or-self::ulink)[last()]" />

        <set variable="relativeURI" context="$selectedElement" 
             expression="relativize-uri(uri-or-file-name('%*'))" />
        <get expression="$relativeURI" />
        <command name="putAttribute" parameter="url '%_'" />

        <get expression="$relativeURI" />
        <command name="status" parameter="url='%_'" />
      </sequence>

      <!-- Default drop action. -->
      <command name="drop" parameter="%*" />
    </choice>
  </macro>
</command>

Application event drop-image is generated when the user drops a file onto an image view. When no command is bound to this application, which is the case by default, a dialog box is displayed allowing the user to specify what she/he wants to do with the image file: copy it or simply reference it.

The variables substituted in the parameter of the bound command are %{url}, %{attribute}, %{dataType}, %{gzip}. Please refer to the documentation of command setObject in XMLmind XML Editor - Commands to learn about the values of these variables.

Simple example which works for XHTML, DITA Topic, DocBook or any document type in which the source of an image is specified using an attribute:

<binding>
  <appEvent name="drop-image" />
  <command name="putAttribute" parameter="%{attribute} %{url}" />
</binding>

The following application events are generated by an image-viewport() in XMLmind XML Editor - Support of Cascading Style Sheets (W3C CSS) when the user drags one of the handles displayed around the image:

Binding one of the above application events to a command allows to have one or more of the following variables substituted in the parameter of the bound command:

XHTML example:

<binding>
  <appEvent name="resize-image" />
  <command name="resizeImage" 
           parameter="height=%{height} width=%{width}" />
</binding>

<binding>
  <appEvent name="rescale-image" />
  <command name="resizeImage" parameter="height width=%{width}" />
</binding>

DocBook example:

<binding>
  <appEvent name="resize-image" />
  <command name="resizeImage" 
           parameter="contentdepth=%{height} contentwidth=%{width} 
                      scale scalefit" />
</binding>

<binding>
  <appEvent name="rescale-image" />
  <command name="resizeImage" 
           parameter="contentdepth contentwidth=%{width} 
                      scale scalefit"/>
</binding>

Notice that both the above examples use the same, generic, command resizeImage in XMLmind XML Editor - Commands.

The name of the corresponding application event is resize-table-column. Binding this application event to a command allows to have one or more of the following variables substituted in the parameter of the bound command:

XHTML example:

<binding>
  <appEvent name="resize-table-column" />
  <command name="xhtml.resizeTableColumn" 
           parameter="%{resizedColumn} %{columnCount} 
                      %{oldColumnWidths} %{newColumnWidths}" />
</binding>

<command name="xhtml.resizeTableColumn">
  <class>com.xmlmind.xmleditext.xhtml.table.ResizeTableColumn</class>
</command>

DocBook 5 example:

<binding>
  <appEvent name="resize-table-column" />
  <command name="db5.resizeTableColumn" 
           parameter="%{resizedColumn} %{columnCount} 
                      %{oldColumnWidths} %{newColumnWidths}" />
</binding>

<command name="db5.resizeTableColumn">
  <macro>
    <choice>
      <!-- tgroup is selected -->
      <command name="db5.resizeCALSTableColumn" parameter="%*" />

      <!-- table or informaltable is selected -->
      <command name="db5.resizeHTMLTableColumn" parameter="%*" />
    </choice>
  </macro>
</command>

<command name="db5.resizeCALSTableColumn">
  <class>com.xmlmind.xmleditext.docbook.table.ResizeTableColumn</class>
</command>

<command name="db5.resizeHTMLTableColumn">
  <class>com.xmlmind.xmleditext.xhtml.table.ResizeTableColumn</class>
</command>

There is no generic command which, after a proper parameterization, would allow to resize the columns of all kinds of tables. However, as shown in the above examples, you can apply com.xmlmind.xmleditext.xhtml.table.ResizeTableColumn to HTML tables and com.xmlmind.xmleditext.docbook.table.ResizeTableColumn to DocBook (CALS) tables.