MICROSOFT_PRESS_EBOOK_PROGRAMMING_WINDOWS_8_APPS_WITH_HTML_CSS_AND_JAVASCRIPT_PDF

FIGURE 12-16 The Save UI as displayed by the sample.
FIGURE 12-17 Application UI settings in the manifest that affect the appearance of the open and save picker UI for a
provider app. The gray bars in this image represent other fields that I’ve omitted for brevity.
When you first run this sample, you won’t see either of these pages. Instead you’ll see a page
through which you can invoke the file open or save pickers and then choose this app as a provider. You
can do this if you like, but I recommend using a different app to invoke the pickers, just so we’re clear
on which app is playing which role. For this purpose you can use the sample we used in Chapter 8, the
File picker sample (this is the consumer side). You can even use something like the Windows 8 Music
app where the Open File command on its app bar will invoke a picker wherein the provider sample will
be listed.
Whatever your choice, the important parts of the provider sample are its separate pages for servicing
its contracts, which are again fileOpenPicker.html and fileSavePicker.html. In the first case, the code is
contained in js/fileOpenPicker.js where we can see the activated event handler with the activation kind
of fileOpenPicker:
function activated(eventObject) {
if (eventObject.detail.kind ===
534