Neil: Text replacement - "" to "
"
2016-10-27T20:03:43Z
Text replacement - "<table border="0" cellspacing="0">" to "<table border="0" cellspacing="0" width="100%">"

← Older revision Revision as of 20:03, 27 October 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0">
+
<table border="0" cellspacing="0" width="100%">

<tr>

<tr>

<td width="20%">[[A WatchKit openParentApplication Example Project|Previous]]<td align="center">[[WatchKit App Development Essentials|Table of Contents]]<td width="20%" align="right">[[Sharing Data Between a WatchKit App and the Containing iOS App|Next]]</td>

<td width="20%">[[A WatchKit openParentApplication Example Project|Previous]]<td align="center">[[WatchKit App Development Essentials|Table of Contents]]<td width="20%" align="right">[[Sharing Data Between a WatchKit App and the Containing iOS App|Next]]</td>

Neil: Text replacement - "" to "
"
2016-05-05T14:31:31Z
Text replacement - "<table border="0" cellspacing="0" width="100%">" to "<table border="0" cellspacing="0">"

← Older revision Revision as of 14:31, 5 May 2016
Line 1: Line 1:

−
<table border="0" cellspacing="0" width="100%">
+
<table border="0" cellspacing="0">

<tr>

<tr>

<td width="20%">[[A WatchKit openParentApplication Example Project|Previous]]<td align="center">[[WatchKit App Development Essentials|Table of Contents]]<td width="20%" align="right">[[Sharing Data Between a WatchKit App and the Containing iOS App|Next]]</td>

<td width="20%">[[A WatchKit openParentApplication Example Project|Previous]]<td align="center">[[WatchKit App Development Essentials|Table of Contents]]<td width="20%" align="right">[[Sharing Data Between a WatchKit App and the Containing iOS App|Next]]</td>

Neil: Text replacement - "BUY_WATCHKIT" to "watchos2_upgrade"

2016-02-01T21:00:53Z

Text replacement - "<google>BUY_WATCHKIT</google>" to "<htmlet>watchos2_upgrade</htmlet>"

Neil at 20:09, 27 May 2015

2015-05-27T20:09:39Z

Neil at 20:01, 7 May 2015

2015-05-07T20:01:31Z

Neil: New page:

Previous [[WatchKit App Development Essentials|T...
2015-04-23T17:30:50Z

New page: <table border="0" cellspacing="0" width="100%"> <tr> <td width="20%">Previous<td align="center">[[WatchKit App Development Essentials|T...

New page
<table border="0" cellspacing="0" width="100%">
<tr>
<td width="20%">[[A WatchKit openParentApplication Example Project|Previous]]<td align="center">[[WatchKit App Development Essentials|Table of Contents]]<td width="20%" align="right">[[Sharing Data Between a WatchKit App and the Containing iOS App|Next]]</td>
<tr>
<td width="20%">A WatchKit openParentApplication Example Project<td align="center"><td width="20%" align="right">Sharing Data Between a WatchKit App and the Containing iOS App</td>
</table>
<hr>

<google>BUY_WATCHKIT</google>

@@ Line 71: / Line 71: @@
+}
 </pre>
+<google>BUY_WATCHKIT</google>
 == Direct Dictation Input ==

← Older revision		Revision as of 20:01, 7 May 2015
Line 9:		Line 9:

	<google>BUY_WATCHKIT</google>		<google>BUY_WATCHKIT</google>
		+
		+
		+	Unlike the iPhone, the Apple Watch display is too small to accommodate a virtual keyboard to allow the user to input text into an app. This does not, however, mean that it is not possible to accept user input. In fact, the WatchKit framework provides a mechanism for user input in the form of selections from a list of phrases, voice dictation and emoji image selection.
		+
		+	This chapter will provide an overview of how to accept user input from within a WatchKit app before providing a brief tutorial.
		+
		+	== Getting User Input ==
		+
		+	The WatchKit framework supports three types of user input in the form of phrase selection, voice dictation and emoji image selection. All three forms of input are available via a single modal scene, an example of which is illustrated in Figure 11-1:
		+
		+
		+	[[Image:watchkit_text_input_controller.png\|The user interface of a WatchKit User Input Controller]]
		+
		+	Figure 11-1
		+
		+
		+	This screen is referred to as the text input controller and can be configured with a list of phrases to be displayed, to enable or disable support for emoji selection, or to go directly to dictation input.
		+
		+	== Displaying the Text Input Controller ==
		+
		+	The text input controller screen is displayed via a call to the presentTextInputControllerWithSuggestions method of the currently active interface controller instance. The method accepts as parameters an array of phrase suggestion strings and an input mode value indicating what forms of input are to be accepted. The method also requires a completion handler block to be called when the input session is completed. This completion block is passed an array containing the results of the input.
		+
		+	The following code, for example, invokes the text input controller with emoji support and a range of phrase suggestions. The completion handler block simply outputs the input string from the reply array to the console:
		+
		+	<pre>
		+	let phrases = ["I'm in a meeting", "I'll call you later", "Call me later"]
		+
		+	presentTextInputControllerWithSuggestions(phrases,
		+	allowedInputMode: .AllowEmoji,
		+	completion: { (result) -> Void in
		+
		+	if let choice = result[0] as? String {
		+	println(choice)
		+	}
		+	})
		+	</pre>
		+
		+	The above code used the .AllowEmoji option (or more precisely the WKTextInputMode.AllowEmoji option) to include static emoji images as selection options. The three input mode options supported by WatchKit are as follows:
		+
		+	* '''WKTextInputMode.Plain''' – Allows the user to generate input from the phrase selection list and dictation only. The emoji button is absent from the text input controller screen in this mode.
		+	* '''WKTextInputMode.AllowEmoji''' - Allows the user to generate input using the phrase list, dictation and non-animated emoji images.
		+	* '''WKTextInputMode.AllowAnimatedEmoji''' - Allows the user to generate input using the phrase list, dictation and both animated and non-animated emoji images.
		+
		+	The text input controller screen will automatically dismiss when the user has made an input selection or tapped the Cancel button. The controller may also be dismissed from within the code of the interface controller via a call to the dismissTextInputController method. When the text input controller is dismissed in this way, the code within the completion handler block is not executed.
		+
		+	When testing text input, it is important to note that emoji and dictation modes are not available from within the simulator environment.
		+
		+	== Detecting if Input is a String or NSData Object ==
		+
		+	If the input is in the form of text or a non-animated emoji, the input will be returned in the form of a Unicode string contained within a String object. If the user selects an animated emoji, however, the image will be returned in the form of an NSData object. The following code can be used to identify whether the returned result is a String or NSData object:
		+
		+	<pre>
		+	if result[0] is String {
		+	// Result is a String object
		+	// Handle as a text string
		+	}
		+
		+	if result[0] is NSData {
		+	// Result is an NSData object
		+	// Handle as an image
		+	}
		+	</pre>
		+
		+	== Direct Dictation Input ==
		+
		+	In many situations, input will be needed only through the use of dictation. To move directly to dictation based input, call the presentTextInputControllerWithSuggestions method without any suggested phrases and with the input mode set to .Plain. For example:
		+
		+	<pre>
		+	presentTextInputControllerWithSuggestions(nil,
		+	allowedInputMode: .Plain,
		+	completion: { (result) -> Void in
		+
		+	}
		+	})
		+	</pre>
		+
		+	== Creating the User Input Example Project ==
		+
		+	Start Xcode and create a new iOS project. On the template screen choose the Application option located under iOS in the left hand panel and select Single View Application. Click Next, set the product name to TextInputApp, enter your organization identifier and make sure that the Devices menu is set to Universal. Before clicking Next, change the Language menu to Swift. On the final screen, choose a location in which to store the project files and click on Create to proceed to the main Xcode project window.
		+
		+	== Adding the WatchKit App Target ==
		+
		+	The next step is to add the WatchKit app target to the project. Within Xcode, select the File -> New -> Target… menu option. In the target template dialog, select the Apple Watch option listed beneath the iOS heading. In the main panel, select the WatchKit App icon and click on Next. On the subsequent screen turn off the Include Glance Scene and Include Notification Scene options before clicking on the Finish button.
		+
		+	As soon as the extension target has been created, a new panel will appear requesting permission to activate the new scheme for the extension target. Activate this scheme now by clicking on the Activate button in the request panel.
		+
		+	== Designing the WatchKit App Main Scene ==
		+
		+	Locate and select the Interface.storyboard file so that it loads into Interface Builder. Drag and drop a Button object from the Object Library panel, double-click on it and change the text so that it reads “Get Input”.
		+
		+	Add a Label object to the scene and set both the Horizontal and Vertical position properties in the Attributes Inspector panel to Center so that the scene layout matches that of Figure 11-2. Also, increase the Lines property to 4 so that multiple lines of text input can be displayed if necessary:
		+
		+
		+	[[Image:watchkit_text_input_scene.png\|The user interface of a WatchKit User Input example app]]
		+
		+	Figure 11-2
		+
		+
		+	Display the Assistant Editor, Ctrl-click on the Label object in the storyboard scene and drag the resulting line to a position immediately beneath the class declaration line in the Assistant Editor panel. On releasing the line, establish an outlet named labelObject in the connection panel.
		+
		+	Repeat these steps on the Button object, this time establishing an action connection to a method named getUserInput.
		+
		+	== Getting the User Input ==
		+
		+	The code to get input from the user now needs to be implemented within the getUserInput action method. For the purposes of this example, input will be accepted in the form of dictation, non-animated emoji and via phrase list selection. Once obtained, the user input will be displayed on the Label object within the main scene. Locate and select the InterfaceController.swift file for the WatchKit app extension in the Project Navigator panel and modify the getUserInput method so that it reads as follows:
		+
		+	<pre>
		+	@IBAction func getUserInput() {
		+	let phrases = ["I'm in a meeting", "I'll call you later", "Call me later"]
		+
		+	presentTextInputControllerWithSuggestions(phrases,
		+	allowedInputMode: .AllowEmoji,
		+	completion: { (result) -> Void in
		+
		+	if let choice = result[0] as? String {
		+	self.labelObject.setText(choice)
		+	}
		+	})
		+	}
		+	</pre>
		+
		+	== Testing the Application ==
		+
		+	Compile and run the WatchKit app on a physical Apple Watch device, tap on the Get Input button and use dictation to enter some text. On tapping the Done button the dictated text will appear on the Label object in the main scene of the app. Repeat these steps to test the phrase selection and emoji forms of input.
		+
		+	== Summary ==
		+
		+	WatchKit provides support for user input via phrase selection, dictation and emoji images. Input is initiated using the presentTextInputControllerWithSuggestions method of the currently active interface controller instance. This chapter has covered the basics of user input in WatchKit and worked through the creation of an example WatchKit app project.

@@ Line 1: / Line 1: @@
-<table border="0" cellspacing="0">
+<table border="0" cellspacing="0" width="100%">
 <tr>
 <td width="20%">[[A WatchKit openParentApplication Example Project|Previous]]<td align="center">[[WatchKit App Development Essentials|Table of Contents]]<td width="20%" align="right">[[Sharing Data Between a WatchKit App and the Containing iOS App|Next]]</td>

Handling User Input in a WatchKit App - Revision history

Neil: Text replacement - "BUY_WATCHKIT" to "watchos2_upgrade"

Neil at 20:09, 27 May 2015

Neil at 20:01, 7 May 2015