Quark XML Author provides two methods for inserting referenced content into a document:
a drag-and-drop operation and pasting a reference from the clipboard—if a user copies
a component reference to the clipboard, Assign Reference becomes available on the
Quark XML Author component context menu. In both cases, Quark XML Author must be able
to resolve the reference hyperlink. The AppConfig.xml file’s ResolveReferences node
provides the means to accomplish this task.
ResolveReferences contains a collection of Reference nodes. Each Reference node identifies
the Content Management System via its pattern attribute, and calls the external DLL
that performs the download operation. ResolveReferences and the Reference node take
the following format:
<ResolveReferences>
<Reference pattern="pattern" assembly="assembly name" class="class name">
<Token>Token 1</Token>
<Token>Token 2</Token>
<Token>Token #</Token>
</Reference>
</ResolveReferences>
The pattern attribute’s value must be a regular expression that contains a matching
pattern for the URI that refers to the CMS. When an object is dragged into Quark XML
Author, Quark XML Author searches for a pattern that can be matched against the URI
for the object being dragged into it. For example:
pattern=”http://yellowstone/.*”
This would match everything following http://yellowstone in a URI.
To allow all URIs to match a single Reference node, the wildcard character phrase
(.*) can be used as the value of the pattern attribute. The period must be present; an
asterisk alone will match only one wild card character.
The assembly and class attribute values specify the assembly and class in which the
download method for the CMS can be found. The download method that must be implemented
in the DLL is discussed in section 17, “Integration with Content Management Systems”.
Specify the assembly within the class as the value of the assembly attribute. Specify
the fully qualified class name, without the .dll extension, as the value of the class
attribute.
Parameter values that are required (if any) by the download method in the external
DLL are specified as Tokens within the Reference node. Each parameter value is supplied
as the content of a separate Token element.