MICROSOFT_PRESS_EBOOK_PROGRAMMING_WINDOWS_8_APPS_WITH_HTML_CSS_AND_JAVASCRIPT_PDF

var dataPackageTitle = document.getElementById("titleInputBox").value;
if ( /* Check if there is appropriate data to share */ ) {
request.data.properties.title = dataPackageTitle;
// The description is optional.
var dataPackageDescription = document.getElementById("descriptionInputBox").value;
request.data.properties.description = dataPackageDescription;
}
// Call request.data.setText, setUri, setBitmap, setData, etc.
} else {
request.failWithDisplayText(/* Error message */ );
}
As we see here, the request.data.properties object (of type DataPackagePropertySet) is where
you set things like a title and description for the data package. Other properties are as follows:
• applicationListingUri The URI of your app’s page in the Windows Store, which should be set
to the return value of Windows.ApplicationModel.Store.CurrentApp.linkUri 57 )
• applicationName A string, which helps share targets gather the same kind of information that
the source can obtain from the targetApplicationChosen event
• fileTypes A string vector, where strings should come from the StandardDataFormats
enumeration but can also be custom formats
• size The number of items when the data in the package is a collection, e.g., files
• thumbnail A stream containing a thumbnail image; obtaining this image is typically why you’d
use the DataRequest.getDeferral method).
Beyond this the data.properties object also supports custom properties through its insert, remove,
and other methods. This makes is possible for the source app to pass custom properties along with
custom formats, making all of this extensible if new data formats are widely adopted in the future.
Within this code structure above, the primary job of the source app is to populate the data package
by calling the package’s various set* methods. For standard formats, which are again those described in
the StandardDataFormats enumeration, there are discrete methods: setText, setUri, setHtmlFormat,
setRtf (rich text format, a comparably ancient precursor to HTML), setBitmap, and setStorageItems (for
files and folders). All of these except for setRtf are represented in the source app sample as follows.
57 This URI along the applicationName would allow a target to indicate where the data originally came from, especially for
scenarios where the data goes to a social network, in an email message, or elsewhere off the device with the source app.
This way, recipients can be invited to acquire the source app themselves, so source apps will probably want to include it.
You always want to use the Windows.ApplicationModel.Store.CurrentApp.linkUri property to populate this field
because you won’t know your URI until your completed app is uploaded to the Store the first time.
497