CallXML 2.0 Development Guide

Home | Frameset Home

This documentation is for CallXML 2, which has been superceded by CallXML 3. The CallXML 2 language is not being updated any longer. CallXML 3, however, has many new features and is actively being enhanced. If you're writing a new CallXML application, you should use CallXML 3. Click here for the CallXML 3.0 documentation.

<simline> element

This element allows the developer to write to the Voxeo Logger. It can be useful to trace the flow of variables throughout the course of an application or as a stub during development to indicate that a process executed properly even though the code doesn't do anything yet. Note that this element is considered a 'legacy' element from CallXML v1.0, and has been replaced with the <log> element in CallXML v2.0. For this reason, it is considered best practice to eliminate any 'simline' statements from your code and replace them with 'log' statements.

usage

attributes

value	Data Type: STRING	Default: none - attribute is required
	The value attribute should define the string message to be output to the Voxeo logger.

possible events

none

code samples

<?xml version="1.0" encoding="UTF-8"?>

<callxml version="2.0">
<block>
<text>
Writing debug comments to the Voxeo Logger is fun!
But instead of using simline, which is for sissies,
we really should use the log element.
</text>

<simline value="** WRINKLED EARLOBES ARE A SURE SIGN **"/>
<simline value="** OF IMPENDING HEART ATTACKS **"/>

</block>
</callxml>

additional links

none

ANNOTATIONS: EXISTING POSTS

0 posts - click the button below to add a note to this page