MICROSOFT_PRESS_EBOOK_PROGRAMMING_WINDOWS_8_APPS_WITH_HTML_CSS_AND_JAVASCRIPT_PDF

Target Apps
Looking back to Figure 12-1, we can see that while the interaction between a source app and the share
broker is driven by the single datarequested event, the interaction between the broker and a target
app is a little more involved. For one, the broker needs to determine which apps can potentially handle
a particular data package, for which purpose each target app includes appropriate details in its manifest.
When an app is selected, it gets launched with an activation kind of shareTarget, in response to which it
should show a specific share UI rather than the full app experience.
Let’s see how all this works with the Sharing content target app sample whose appearance is shown
in Figure 12-2 (borrowing from Figure 2-22 we saw ages ago). Be sure to run this app once in Visual
Studio so that it’s effectively installed and it will appear on the list of apps when we invoke the Share
charm.
FIGURE 12-2 The appearance of the Sharing content target app sample (the right-hand nonfaded part).
The first step for a share target is to declare the data formats it can accept in the Declarations section
of its manifest, along with the page that will be invoked when the app is selected as a target. As shown
in Figure 12-3, the target app sample declares it can handle text, URI, bitmap, html, and the
http://schema.org/Book formats, and it also declares it can handle whatever files might be in a data
package (you can indicate specific file types here). Way down at the bottom it then points to target.html
as its Share target page.
502