Notable Properties

• Caption: Changes the label text.

• Font: Sets the font type and size.

Script Example

Notable Properties

• EnableSpellCheck: Enables spell checking for the text field.

• Name: Sets the name of the text field.

• UTF8Text: Sets the text in the text field.

Script Example

The text field can be set as follows: TWUniEdit1.UTF8Text = Date

or, alternatively, using: SetUnicodeValue TTWUniEdit1, Date

where SetUnicodeValue takes the unicode input parameter, UTF8-encodes it and sets the .UTF8Text property.

GetUnicodeValuereads the .UTF8Text property from components, UTF8-decodes it and returns, for example:

Sub TWUniButton1Click(Sender)

MsgBox GetUnicodeValue(TWUniEdit1)

End sub

Another example using the Unicode Edit field is described in this Script Example (Image with Name, Unicode Edit and Template Info).

To enable spell checking in Unicode Edit and Unicode Memo fields

1. Use the Wizard to create a new template.

2. Add a Unicode Edit Component or Unicode Memo Component field to the template.

3. Check the EnableSpellCheck property for each field that requires spell checking.

4. Save the template.

   Note: The actual spell checking will only occur when the template is saved as a data element in the Newsroom System or Director.

Notable Properties

• EnableSpellCheck: Enables spell checking for the text field.

• Name: Sets the name of the multiline text field.

• UTF8Text: Sets the text in the text field.

• WordWrap: Wraps a section of words, adding line breaks (this property is listed in the All tab). Refer to the example below for more information.

Script Example

When enabling the WordWrap property, the width of the template’s text box decides where the line breaks in the graphics will be. Hence, the output on the renderer might not be as intended. If the template’s text box is narrower than what the scene allows, the output will have line breaks according to the text box, and not according to the scene design. To solve this, either use the Wrap Fixed Unicode Memo component without WordWrap, or add a script that can remove all line breaks. The example below is most useful for scenes with only one text paragraph.

Notable Properties

• AllowCropAspectOverride: Enables users to select a different aspect ratio than the one given by the DestHeight and DestWidth properties, when using Crop Service. Default value = False. See Preset Image Size.

• AlwaysUseCropTool: Enables the user to always use the crop tool by default when an image is added to the template when using the isImageMediaSearch, isFileOpen and isPaste image source options. See To enable the crop tool.

• ControlObjectName: Links the component to an exposed scene object.

• DestWidth/DestHeight: Sets the destination width/height of the image, forcing the size of the image used in the scene to be of a specific width/height. For details, see Preset Image Size.
  When set to values greater than 0 (zero), it will enable the crop tool. The parameters set a fixed height and width for the crop tool. Using this setting will force the user to use the configured height and width, and the aspect. Meaning, if the selection is greater than then actual height and width parameters, the image will be scaled to fit.

• DisallowedKeywords: Defines the disallowed keywords used when searching for media content. When a user searches and finds an image, they are not allowed to select the image if it contains a keyword that is present in the DisallowedKeywords property.

  Note: The DisallowedKeywords property is available for RestVOS and Viz One searches, but not for Object Store searches.

• EvObjects: Add the path to more object containers to receive the same value as the object defined in ObjectPath. Add the name of containers with “$containername” or the full Viz Engine path. Other objects must have the same keyframe name as the main object.

• HideObjects: Define other objects that should be hidden when the main image object is hidden.

• HideOnEmpty: If selected, the object is set to hidden in the scene if no image is loaded.

• ImageSources: Sets one or multiple image source locations. The default settings are isImage and isImageMediaSearch; however, in most cases the actual control object properties of the scene will decide what components and settings to use.

  • isAdvancedCuriousMap: Allows the user to search and select a map from the Viz World Client using the Classic Edition Editor.

    Note: The isAdvancedCuriousMap property is deprecated from Viz Pilot 5.7 and only available for backward compatibility. Use the World Maps Editor Component component instead.

  • isArdome: Allows the user to search and select clips from Viz Ardome.

    Note: The isArdome property requires an Ardome connection and setup.

  • isCuriousMap: Allows the user to search and select a map from the Viz World Client using the Lite Edition Editor.

    Note: The isCuriousMap property is deprecated from Viz Pilot 5.7 and the Lite Edition editor is not the recommended editor. These features are only available for backward compatibility. Use the World Maps Editor Component component instead.

  • isFileOpen: Allows the user to search and select an image from disk. Note that the image must be available on the Viz Engine using the same shared path.

  • isImage: Allows the user to search the Viz image pool for images through Director’s Viz resource tab. Viz 3.x images are stored on the Viz Graphic Hub while Viz images are stored on its data root.

  • isImageMediaSearch (previously named isDatabase): Allows the user to search and select a still image from the configured service providers (eg. Object Store, Viz One).

  • isMaterial: Allows the user to select a material from the Viz material pool through Director’s Viz resource tab.

  • isObject: Allows the user to select an object from the Viz object pool through Director’s Viz resource tab.

    Note: The isObject property requires a local Viz Engine connection.

  • isPaste: Allows the user to paste images from the Windows clipboard by right-clicking the Image icon and selecting Paste... on the context menu. Pasting will open the Crop Image tool. Pasted images should be added to a shared drive accessible to Viz Engine. The crop tool save path is set in Director’s Preferences window under General settings. isPaste does not add images to Object Store, and does not preserve alpha values.

  • isProximity: Allows the user to search and select images or clips from Proximity’s Artbox. Requires the Proximity Artbox asset management system.

  • isRGB: Allows the user to select an image from the Viz RGB pool through Director’s Viz files tab.

    Note: Viz Pilot News cannot use isRGB, as this relates to a Director specific function.

  • isScene: Allows the user to select a scene from the Viz scene pool through Director’s Viz resource tab.

  • isVideoMediaSearch (previously named isVideoHub): Allows the user to search and select a video from the configured service providers (eg. Object Store, Viz One). When selected, it allows the user of the template to preview a video item using the Timeline Editor within Director or Viz Pilot News.

• RequiredKeyWords: Defines the required keywords used when searching for media content. See Required Keywords.

• RequiredKeywordsMode: Sets the options RequireOne or RequireAll. Searches can be performed with information from the RequiredKeyWords field.

Events

• OnImageInfoChanged: Enables Object Store To add person information to the template. Person information is often registered in Object Store with images of persons in order to easily get the right name of the person in question. See Person Information Component.

• CreatingMediaOrder: Used with Order Management. This event is raised just before the Order Management window is shown. Its signature looks like:

  Sub TWImageInf1CreatingMediaOrder(Sender, CustomParameters, ReservedParameterKeys)

  • Sender is set to the image control itself.

  • CustomParameters is a key-value collection where you can add items. For example: CustomParameters.Add("this=1")

  • ReservedParameterKeys is a list containing all the keys that are set by the client for various purposes. It has the following values: keywords, asset_type, destination_width, destination_height, template_name, concept_name, variant_name. If any of these keys is set in CustomParameters then it will be ignored and the value provided by the client will be used instead.
    For example:

    Sub TWImageInf1CreatingMediaOrder(Sender, CustomParameters, ReservedParameterKeys)

    ' Add key value parameter pair

    CustomParameters.Add "Param1=Value1"

    ' Get index of key

    CustomParameters.IndexOfName("Param1") ' returns 0 (-1 if name is not found)

    ' Get the key for a given index

    CustomParameters.Names(o) ' returns "Param1"

    ' Get the value for a key

    CustomParameters.Values( "Param1" ) ' returns "Value1"

    End sub

Script Example (Image with Name, Unicode Edit and Template Info)

The following example describes how to include the Object Store image name in the data element name.

1. Add a Unicode Edit Component field (name txtImageName) and set it to be invisible.

2. Add a Template Information Component component and add in txtImageName as one of the save name fields.

3. On any of the image components (here named "image") add the following script on the OnFilenameChanged event:

   Sub imageFilenameChanged(Sender)

   txtImageName.UTF8Text = "" 'Clear the save name before starting

   \qFirst test if the returned image is from a Viz One server

   if Left(image.picFilename, 8) = "https://" then

   txtImageName.UTF8Text = "Viz One Image"

   else '...it should be an Object Store image

   \qGet the number of arrays if the picfilename divided by "\" mark

   NumberOfElements = UBound(Split(image.picFilename, "\"))

   if NumberOfElements > 0 then

   txtImageName.UTF8Text = Split(image.picFilename, "\")(NumberOfElements)

   End if

   End if

   End sub

Preset Image Size

A scene designer can design a scene to use an image of a specific size. By setting a specific width and height the template designer can, in accordance with the scene design, control the aspect. When selecting an image, a crop tool, with a preset aspect ratio, is automatically opened requiring the user to crop the image. Images from Object Store will use the legacy Crop Tool while images fetched with RestVOS from Object Store or Viz One will be cropped using Crop Service.

DestWidth and DestHeight is used as parameters to preset the crop tool and to scale the image further after save, if needed.

If the property AllowCropAspectOverride is true, users can select a different aspect ratio than the one given by the DestHeight and DestWidth properties. This is only supported for images cropped with Crop Services.

Required Keywords

The properties RequiredKeyWords and RequiredKeywordsMode allow the Object Store (VOS), RestVOS or Viz One search to be restricted by keyword in two ways.

RequiredKeywordsMode = RequireOne:

• The media search will return images containing ONE OR MORE of the keywords specified in the RequiredKeyWords property in the template.

• When using the template in Viz Pilot News, deselecting some of the keywords is possible, and will narrow down the search. Selecting additional keywords will broaden the search.
  RequiredKeywordsMode = RequireAll:

• The media search will ONLY return images containing ALL of the keywords specified in the RequiredKeyWords property in the template.

• When using the template in Viz Pilot News, deselecting a required keyword is not possible. Selecting additional keywords will narrow down the search.

  Note: The functionality of Viz One and RestVOS allow multiple keywords in the Viz One or RestVOS to map to a single keyword in the interface. If such mappings exist, any RequireAll searches that include such keywords, will be run as RequireOne searches. The result of this is that the user will see more results than is strictly correct. However the user will not be able to use any of the incorrect images as the "OK" button will only be enabled when an image with all the required keywords is selected. To avoid this situation, the keywords in the Viz One or RestVOS should be labeled with unique names.

To enable the crop tool

If the image component uses AlwaysUseCropTool, DestHeight or DestWidth, then the crop tool will be called.

1. In Template Wizard open a template with an image component.

2. Select the image component and set one or both of the following properties:

   • AlwaysUseCropTool: Use the crop tool by default.

   • DestHeight and DestWidth: When set to values greater than 0 (zero), it will enable the crop tool. The parameters set a fixed height and width for the crop tool.

3. Select one or several image sources.

   • ImageSources: Valid sources for the crop tool are isImageMediaSearch, isFileOpen and isPaste.

4. Save the template.

To add person information to the template

In addition to fetching the person information and adding it to the proper text fields, the following procedure will use the SC_SaveName function to fill the Save dialog box with a save name based on the image’s file name.

1. Start Template Wizard.

2. Create a new template of a scene with an image.

3. Select the image component (TTWImageInf1) that was added to the template.

4. Check the Enable script option in the Object Inspector (CTRL+F12) to enable scripting

5. Select the Events tab, and double-click the OnImageInfoChanged event to add the procedure to the Script Editor.

6. Add the following script:

   option explicit

   dim level

   dim savename

   function SC_SaveName

   SC_Savename = savename

   end function

   Sub TTWImageInf1ImageInfoChanged(ImageInfoList, PersonInfoList, KeywordsList)

   dim i

   TWUniMemo1.Lines.Clear

   TWUniMemo2.Lines.Clear

   TWUniMemo3.Lines.Clear

   for i = 0 to ImageInfoList.Count - 1

   TWUniMemo1.Lines.Add(ImageInfoList(i))

   next

   for i = 0 to PersonInfoList.Count - 1

   TWUniMemo2.Lines.Add(PersonInfoList(i))

   next

   for i = 0 to KeywordsList.Count - 1

   TWUniMemo3.Lines.Add(KeywordsList(i))

   next

   savename=ImageInfoList.Values("FileName")

   End sub

7. Save the template and open it in Director or Viz Pilot News to test it.

To use additional fields

1. Add the ImageInfoChanged event to your script:

   Sub TTWImageInf1ImageInfoChanged(ImageInfoList, PersonInfoList, KeywordsList)

   TTWUniEdit1.Text = ImageInfoList.Values("Nationality")

   End sub

   Note: Nationality refers to an Additional Field added to Object Store.

Notable Properties

• ControlObjectName: Links the component to an exposed scene object.

• MapXML: Stores the XML that is returned from the Viz World Server once the user has selected a map.

• VizWorldEditor: Defines the editor to be launched when a map is added to the template.

  • vwClassic_Edition: Classic is the default editor. All the map features are exposed and the user has full control over the map selected.

  • vwSecond_Edition: Second Edition is the next generation map editor. It is more user friendly and will soon have a full set of features.
    For more information on how to work with maps, please refer to the Viz World User’s Guide.

Notable Properties

• Caption: Sets a text string to identify the panel to the user.

• Name: Sets the name of the panel to use as a reference when scripting.

• Height and width: Sets the size of the panel.

Script Example (Panel and Unicode Button)

This example shows how a panel can be switched on and off using the Visible property. The color of the buttons change accordingly.

Notable Properties

• Name: Specifies the name of the control as referenced in code.

Script Example

An example using Unicode Buttons is described in this Script Example (Panel and Unicode Button).

Notable Properties

• Checked: Specifies whether the check box is checked.

Script Example

The following script example uses a sub procedure and a function. Components used are; one Unicode button, three Unicode edit fields and two Unicode check boxes.

The Sub procedure TWUniButton1Click calls the function setText using the text string of the TWUniEdit0 edit field as argument.

The setText function tests to see if the corresponding check boxes are checked. If they are, newText is assigned to the edit fields.

Notable Properties

• Checked: Determines whether the option represented by the radio button is selected.

• Enabled: Controls whether the radio button is enabled or disabled.

Notable Properties

• UTF8Text: Displays the current combo-box selection.

• UTF8Items: Lists the items (strings) in the list portion of the combo box. Use the methods of Items to add, delete and clear items, for example:

  TWUniComboBox1.Items.Add(TWUniEdit1.Text)

  TWUniComboBox1.Items.Delete(TWUniComboBox1.ItemIndex)

  TWUniComboBox1.Items.Clear

Script Example

See the Unicode ListBox Component for a scripting example that can be used with the ComboBox.

Notable Properties

• UTF8Items: Lists the items (strings) in the list box. Use the methods of Items to add, delete and clear items, for example:

  TWUniListBox1.Items.Add(TWUniEdit1.Text)

  TWUniListBox1.Items.Delete(TWUniListBox1.ItemIndex)

  TWUniListBox1.Items.Clear

Script Example

The following script example uses a sub procedure and a function. Components used are; one Unicode button, two Unicode edit fields, one Unicode check box and a Unicode listbox.

The setText function tests to see if the checkbox is checked. If it is, newText is added to the listbox the number of times given in the “Number of copies” text field (e.g. 5). If not checked the text is added once to the listbox.

The Sub procedure TWUniButton1Click calls the function setText using the text string of the TWUniEdit0 edit field as argument.

Notable Properties

• AllowEditingOfDefaultName: Determines if the user should be allowed to edit the suggested name in the save dialog.

• DefaultSaveName: Set by the SaveNameTextFields and Separator properties.

• Prefix: Used to set a prefix for save names.

• SaveNameTextFields: Click the ellipsis button to bring up an editor to select the edit boxes that should be used for generating a save name.

• Separator: Set a separator (for example a space, dot or underscore). This is used to separate text strings added to the DefaultSaveName from the edit boxes selected in the SaveNameTextFields property.

• ShowSaveDialog: Determines whether Director should show the save dialog when saving the template.

Advanced Properties

Some of the Template Information properties are used to set a default start time and duration for a data element when it is saved using Viz Pilot News. The properties described below are primarily used with automation systems, and can only be used with Viz Pilot News.

• DefaultStartTime: (mm:ss) Sets the start time of the data element in the playlist. The start time is relative to the start time of the playlist.

• DefaultDuration: (mm:ss) Sets the duration of the data element in the playlist.

  Note:DefaultStartTime _and _DefaultDuration always contain the current timing information for a data element. So, for example, a script could access these values and include timing information in the name of the data element when saving it.

• ShowGraphicEventTiming: Can be set as follows:

  • stShow: Display the Graphic Event Timing checkbox when Saving an Element in Viz Pilot News. The timing properties relate to DefaultDuration and DefaultStartTime.

  • stHide: Do not display the Graphic Event Timing checkbox when Saving an Element in Viz Pilot News. In this case you can script the values and use them as part of the template.

  • stDefault: Use the Database Parameters (ax_dataelement_timer_enabled) to determine whether to show or hide the Graphic Event Timing checkbox.

    Note: The stShow and the stHide value will override the database setting on a template by template basis.

• TimingMode: Flag indicating the value of the Graphic Event Timing checkbox. This property only takes effect if the Graphic Event Timing checkbox is shown.

  • tmManual: Graphic Event Timing is not checked.

  • tmAutomatic: Graphic Event Timing is checked.

Script Example

See the Script Example (Image with Name, Unicode Edit and Template Info).

Notable Properties

• UTF8Text: Displays the current drop-list selection.

• LinkName: Sets the TV name property to the component selected.

• LinkTitle: Sets the Title property to the component selected.

Using a Person Information component in a template

The component also has some features that are available to the template user. A context menu appears when right-clicking the drop-down list. The options are:

• Refresh Datasource: Refreshes the data source, making new database entries available to the user.

• Searchfield: Displays a sub menu with the following options:

  • FULL_NAME: Displays all available full names in the drop-list.

  • TV_NAME: Displays all available TV names in the drop-list.

  • FIRST_NAME: Displays all available first names in the drop-list.

  • MIDDLE_NAME: Displays all available middle names in the drop-list.

  • LAST_NAME: Displays all available last names in the drop-list.

  • TITLE: Displays all available titles in the drop-list.

Notable Properties

• Source: Specifies the URI of the feed the user will be able to select items from.
  See also The Following Fields can be Linked and The Following Fields cannot be Linked

Events

• OnFeedItemSelected: Specifies the properties and methods that are available for mapping the feed data to fields in the template.
  Properties:

  • Title

  • Summary

  • ContentType

  • MediaContent(<attribute>): Returns the value of the given attribute from the main media content of the item. See Script Example 3 - Mapping Title, MediaContent and XML.

  • Xml: Returns an XML representation of the selected entry. The template designer can then extract any additional values from the item as desired by using the entry.xml property. See Script Example 3 - Mapping Title, MediaContent and XML.

  • Payload: If the item contains a payload as the main content, it can be accessed using this property. The data parameter in the OnUpdatePayload method represents a payload. See Script Example 2 - Mapping a name.
    Methods:

  • GetLinkWithRelation. See Script Example 1 - Mapping data.

To use the Feed Linker component

1. Add the Feed Linker component to a template.

2. In the Object Inspector set the Source property to the URI of a feed.
   e.g. http://site.example.com/feeds/posts

3. See how To add an event.

4. Double-click the event OnFeedItemSelected.

5. In the script editor, map feed data to template fields, see Script Example 1 - Mapping data.

Technical

The following XML Namespace Prefixes are used when referring to XML elements:

The keywords MUST, MUST NOT, REQUIRED, SHALL, SHALL NOT, SHOULD, SHOULD NOT, RECOMMENDED, MAY, and OPTIONAL in this document are to be interpreted as described in RFC 2119.

The Following Fields can be Linked

• <atom:author>
  The personal details of the author of the selected <atom:entry>, which might be an individual person or an organization. The data is provided in child elements as follows:

  • <atom:name>: The name of the author. The value of the <atom:name> element inside the first <atom:author> element that applies for the entry is recorded as the field value. This child element is required if you are specifying the <atom:author> element.

  • <atom:uri>: A URL associated with the author, such as a blog site or a company web site. The value of the <atom:uri> element inside the first <atom:author> element that applies for the entry is recorded as the field value. This child element is optional.

  • <atom:email>: The e-mail address of the author. The value of the <atom:email> element inside the first <atom:author> element that applies for the entry is recorded as the field value. This child element is optional.

• <atom:content>
  <atom:content>...</atom:content>
  <atom:content src="..." />

  • Either inline or URL content is supported.

  • There is no type match, so it is up to the Viz Pilot operator to figure out what content can be used.

  • For URL content the resource is downloaded first and then applied as the value. If you just want the URL use <atom:link>.

• <atom:entry>
  The whole entry XML.

• <atom:link>
  This element defines a reference from an entry to a Web resource; in other words this is the value of the href attribute.

• <vaext:locator>
  The text of the Vizrt Atom Extension <vaext:locator> element which has a vaext:type attribute equal to the mediatype attribute of <viz:fielddef> element in the model.

• <atom:published>
  This element is a Date construct indicating the initial creation or first availability of the entry. The value of the <atom:published> element in the entry is recorded as the field value.

• <atom:summary>
  This element is a Text construct that conveys a short summary, abstract, or excerpt of an entry. The content of the <atom:summary> element in the entry is recorded as the field value.

• <atom:thumbnail>

• The value of the URL attribute of the first thumbnail element in the entry is recorded as the field value.

• <atom:title>
  This element is a Text construct that conveys a human-readable title for an entry or feed; the title of the selected <atom:entry>.

• <atom:updated>
  This element is a Date construct indicating the most recent instant in time when the selected <atom:entry> was modified. The value of the <atom:updated> element in the entry is recorded as the field value.

The Following Fields cannot be Linked

• <atom:category>

• <atom:id>

• <atom:rights>

• Any other elements.

Elements in atom feed

Elements that should be present in the <atom:feed> for the full user experience:

• OpenSearch link:
  <atom:link rel="search" type="application/opensearchdescription+xml" href="http://example.com/opensearchdescription.xml"/>

• Optional, needed for support for server side searching.

  • The opensearchdescription xml file must contain a template node that returns search results as an atom feed:
    <opensearch:Url type="application/atom+xml" template="http://..." />

• For more details see http://www.opensearch.org/Specifications/OpenSearch/1.1

• Up link:
  <atom:link rel="up" type="application/atom+xml;type=feed" href="http://..." />

• Optional, needed for nested collections.

  • The up link should link to the parent folder feed for hierarchical feeds.

  • The up link must have a type string equal to "application/atom+xml;type=feed".

Elements in atom entry

Elements that should be present in the <atom:entry> for the full user experience:

• Self link:
  <atom:link rel="self" type="application/atom+xml;type=entry" href="http://..." />

• The self link must link to the URL that will return the <atom:entry> xml.

  • The self link must have a type value equal to "application/atom+xml;type=entry".

  • Needed for refresh/update of values from the item to work.

  • Needed in combination with the up link for remembering and showing the selected feed entry in a hierarchy of feeds (folder structure). Not needed for remembering selection in flat feeds since then the atom:id will be used.

• Up link:
  <atom:link rel="up" type="application/atom+xml;type=feed" href="http://..." />

• The up link must have a href value that is the URL of the feed the entry is in.

  • The up link must have a type value equal to "application/atom+xml;type=feed".

  • Needed in combination with the self link for remembering and showing the selected feed entry in a folder structure.

• Down link:
  <atom:link rel="down" type="application/atom+xml;type=feed" href="http://..." />

• Needed if this <atom:entry> is to be considered a subfolder instead of a normal <atom:entry>.

  • The down link must have a type value equal to "application/atom+xml;type=feed".

  • The down link must have a href value that is the URL of the feed (folder) the entry represents.

  • Link may contain thr:count attribute (RFC4685) indicating how many children there are. If the value of thr:count is 0 (zero) then the folder will not be loaded since it is empty. This is an optimization.

• Thumbnail link:
  <media:thumbnail url="http://..."/>

• Needed for thumbnail icons to display on the entries in the feed browser.

  • The URL value must reference a JPEG or PNG image resource.

  • If many thumbnails are defined the first one will be selected as the default. This is according to Media RSS Specification Version 1.5.0.

• Locator
  <vaext:locator type="application/vnd.vizrt.viz.geom">GEOM*Vizrt/Tutorials/VizPilot/...</vaext:locator>

• Needed to be able to link a tabfield to a locator. A locator is a path that is not representable with the URI href in an <atom:link>. The selected value is the text node in the locator, so it can in theory be used for any kind of text.

  • For Viz Pilot it is meant to be used to select paths to resources that are not URIs, like the resources on the Graphic Hub that is currently in use.

  • The type must match the tabfield type.

  • The value from the first locator that matches will be used.

  • If no locators matches an error message will be logged in Viz Pilot.

  • The Viz Engine types are:

• TEXT: text/plain

  • RICHTEXT: application/vnd.vizrt.viz.richtext+xml

  • MATERIAL: application/vnd.vizrt.viz.material

  • DUPLET: application/vnd.vizrt.viz.duplet

  • TRIPLET: application/vnd.vizrt.viz.triplet

  • FONT: application/vnd.vizrt.viz.font

  • CLOCK: application/vnd.vizrt.viz.clockcommands

  • GEOM: application/vnd.vizrt.viz.geom

  • IMAGE: application/vnd.vizrt.viz.image

  • AUDIO: application/vnd.vizrt.viz.audio

  • VIDEO: application/vnd.vizrt.viz.video

  • MAP: application/vnd.vizrt.curious.map

  • TRIOSCROLL: application/vnd.vizrt.trio.scrollelements+xml

• Other links:
  <link rel="..." href="http://..." type="..."/>

• Needed in order to select the URL to external resources. This can be images, videos, text, and so on.

  • Limitation 1: The atom 1.0 specs allow multiple links with the same relation, but when linking a tabfield to a link in Viz Pilot, only the first link will be selected.

  • Limitation 2: Viz Pilot can only use the href URL as the value. It cannot download the resource at the URL and use its contents as the value. The Viz Engine control plugin for the property has to be able to understand the URL and download the resource.

Script Example 1 - Mapping data

Link data (Title, Summary, ContentType) from a news feed to editbox fields in a template, including getting the link of the feed item itself using GetLinkWithRelation.

Script Example 2 - Mapping a name

Link a person’s TVname in a person feed to an editbox in the template.

Script Example 3 - Mapping Title, MediaContent and XML

Link text, images and XML from feed data to a template.