Protocols/MSNP/Activities/SDK/Techref/Promo/Variables - Revision history

Animadoria at 00:26, 13 August 2022

2022-08-13T00:26:40Z

← Older revision		Revision as of 00:26, 13 August 2022
Line 6:		Line 6:
	After an Activity has been added to the Activity directory in MSN®, your application can be started from either the <span class="clsUIElement">Games</span> or <span class="clsUIElement">Activities</span> button on the MSN Messenger toolbar.<br />		After an Activity has been added to the Activity directory in MSN®, your application can be started from either the <span class="clsUIElement">Games</span> or <span class="clsUIElement">Activities</span> button on the MSN Messenger toolbar.<br />
	<br />		<br />
	If you want, you can increase usage of your Activity by directing users to your Activity directly from a Web page. You can accomplish this in either of two ways: by adding script to a Web page that calls an ActiveX® control directly, or by adding a URL link to a Web page. This URL directs the ~~user�s~~ browser to a Web site that the MSN Messenger team controls. For more information about directly starting your Activity through the ActiveX control, see [[Protocols/MSNP/Activities/SDK/~~code.htm~~\|Calling the MSN Messenger Client Directly]]. For more information about using a URL to start your Activity, see [[Protocols/MSNP/Activities/SDK/~~url.htm~~\|Calling the MSN Messenger Client from a URL]].<br />		If you want, you can increase usage of your Activity by directing users to your Activity directly from a Web page. You can accomplish this in either of two ways: by adding script to a Web page that calls an ActiveX® control directly, or by adding a URL link to a Web page. This URL directs the user's browser to a Web site that the MSN Messenger team controls. For more information about directly starting your Activity through the ActiveX control, see [[Protocols/MSNP/Activities/SDK/Techref/Promo/Code\|Calling the MSN Messenger Client Directly]]. For more information about using a URL to start your Activity, see [[Protocols/MSNP/Activities/SDK/Techref/Promo/Url\|Calling the MSN Messenger Client from a URL]].<br />
	<br />		<br />
	You can use either of the preceding two methods; however, coding a Web site to control the MSN Messenger client directly is the preferred method because this functionality is built into the client, and the URL that this method uses may change in the future.<br />		You can use either of the preceding two methods; however, coding a Web site to control the MSN Messenger client directly is the preferred method because this functionality is built into the client, and the URL that this method uses may change in the future.<br />
Line 25:		Line 25:
	The two variables, <span class="clsGlossaryTerm">AppID</span> and <span class="clsGlossaryTerm">BOT</span>, are optional, and you can alter the behavior of the called MSN Messenger client by choosing to eliminate either of these two variables. The following table illustrates the behavior observed when either of these two optional variables is passed to the MSN Messenger client (by either method):		The two variables, <span class="clsGlossaryTerm">AppID</span> and <span class="clsGlossaryTerm">BOT</span>, are optional, and you can alter the behavior of the called MSN Messenger client by choosing to eliminate either of these two variables. The following table illustrates the behavior observed when either of these two optional variables is passed to the MSN Messenger client (by either method):

	~~<div~~ class="~~clsTableStd~~">		{\| class="wikitable"
			\|-
	AppID variable passed to client?		! AppID variable passed to client? !! BOT variable passed to client? !! Observed client behavior
			\|-
	~~</div>~~		\| No \|\| No \|\| The user will be:
	BOT variable passed to client?

	Observed client behavior

	No

	No

	~~<div class="clsListStd">~~

	# Presented with the User list from which the user can choose a friend to engage in a game or activity.		# Presented with the User list from which the user can choose a friend to engage in a game or activity.
	# Presented with the Conversation window, from which the user can select which game or activity to share with the other user.		# Presented with the Conversation window, from which the user can select which game or activity to share with the other user.
	# Offered the opportunity to select the desired game or activity with the other user.		# Offered the opportunity to select the desired game or activity with the other user.
			\|-
			\| Yes \|\| No \|\| The user will be:
	~~</div>~~
	Yes

	No

	~~<div class="clsListStd">~~

	# Presented with the User list from which the user can choose a friend to engage in a game or activity.		# Presented with the User list from which the user can choose a friend to engage in a game or activity.
	# Presented with an invitation (after the Conversation window opens) for the application specified by the AppID variable.		# Presented with an invitation (after the Conversation window opens) for the application specified by the AppID variable.
	# Offered the opportunity to enjoy the game or activity with the other user (if the other user chose to play the game or participate in the activity).		# Offered the opportunity to enjoy the game or activity with the other user (if the other user chose to play the game or participate in the activity).
			\|-
			\| No \|\| Yes \|\| The user will be:
	~~</div>~~
	No

	Yes

	~~<div class="clsListStd">~~

	# Brought into the Conversation window with another user whose e-mail address was specified by the BOT parameter.		# Brought into the Conversation window with another user whose e-mail address was specified by the BOT parameter.
	# Presented with the Conversation window, from which the user can select which game or activity to share with the other user.		# Presented with the Conversation window, from which the user can select which game or activity to share with the other user.
	# Offered the opportunity to select the desired game or activity with the other user.		# Offered the opportunity to select the desired game or activity with the other user.
			\|-
			\| Yes \|\| Yes \|\| The user will be:
	~~</div>~~
	Yes

	Yes

	~~<div class="clsListStd">~~

	# Brought into the conversation window with another user whose e-mail address was specified by the BOT parameter.		# Brought into the conversation window with another user whose e-mail address was specified by the BOT parameter.
	# Presented with an invitation (after the Conversation window opens) for the application specified by the AppID variable.		# Presented with an invitation (after the Conversation window opens) for the application specified by the AppID variable.
	# Offered the opportunity to enjoy the game or activity with the other user (if the other user chose to play the game or participate in the activity).		# Offered the opportunity to enjoy the game or activity with the other user (if the other user chose to play the game or participate in the activity).
			\|}

	~~</div>~~

Animadoria: Created automatically by Anima Importer

2022-08-12T22:45:45Z

Created automatically by Anima Importer

← Older revision		Revision as of 22:45, 12 August 2022
Line 1:		Line 1:
	<!-- Generated @ 08/12/2022 23:43:09 +01:00 using Anima's CHM converter based on techref/promo/variables.htm -->		<!-- Generated @ 08/12/2022 23:45:45 +01:00 using Anima's CHM converter based on techref/promo/variables.htm -->
	{{Protocols/MSNP\|section=Activities}}		{{Protocols/MSNP\|section=Activities}}
	__NOTOC__= Using the MSN Messenger Variables =		__NOTOC__= Using the MSN Messenger Variables =

Animadoria: Created automatically by Anima Importer

2022-08-12T22:43:09Z

Created automatically by Anima Importer

New page

{{Protocols/MSNP|section=Activities}}
__NOTOC__= Using the MSN Messenger Variables =

After an Activity has been added to the Activity directory in MSN®, your application can be started from either the <span class="clsUIElement">Games</span> or <span class="clsUIElement">Activities</span> button on the MSN Messenger toolbar.<br />
<br />
If you want, you can increase usage of your Activity by directing users to your Activity directly from a Web page. You can accomplish this in either of two ways: by adding script to a Web page that calls an ActiveX® control directly, or by adding a URL link to a Web page. This URL directs the user�s browser to a Web site that the MSN Messenger team controls. For more information about directly starting your Activity through the ActiveX control, see [[Protocols/MSNP/Activities/SDK/code.htm|Calling the MSN Messenger Client Directly]]. For more information about using a URL to start your Activity, see [[Protocols/MSNP/Activities/SDK/url.htm|Calling the MSN Messenger Client from a URL]].<br />
<br />
You can use either of the preceding two methods; however, coding a Web site to control the MSN Messenger client directly is the preferred method because this functionality is built into the client, and the URL that this method uses may change in the future.<br />
<br />
In order to take the user directly to your Activity, you need to supply the following two string parameters:

<div class="clsListStd">

* <span class="clsGlossaryTerm">AppID</span>
* <span class="clsGlossaryTerm">BOT</span>

</div>
The <span class="clsGlossaryTerm">AppID</span> variable is a composite of two values: the number that corresponds to your desired market or country (for example, 5129 represents New Zealand) and the number that the MSN Support team assigned to your application in the Activity directory (for example, 126). In this case, the <span class="clsGlossaryTerm">AppID</span> value for your Activity for the New Zealand market would be 5129126.<br />
<br />
The <span class="clsObject">BOT</span> variable must be in the following format: someone@example.com.<br />
<br />
The two variables, <span class="clsGlossaryTerm">AppID</span> and <span class="clsGlossaryTerm">BOT</span>, are optional, and you can alter the behavior of the called MSN Messenger client by choosing to eliminate either of these two variables. The following table illustrates the behavior observed when either of these two optional variables is passed to the MSN Messenger client (by either method):

<div class="clsTableStd">

AppID variable passed to client?

</div>
BOT variable passed to client?

Observed client behavior

No

No

<div class="clsListStd">

# Presented with the User list from which the user can choose a friend to engage in a game or activity.
# Presented with the Conversation window, from which the user can select which game or activity to share with the other user.
# Offered the opportunity to select the desired game or activity with the other user.

</div>
Yes

No

<div class="clsListStd">

# Presented with the User list from which the user can choose a friend to engage in a game or activity.
# Presented with an invitation (after the Conversation window opens) for the application specified by the AppID variable.
# Offered the opportunity to enjoy the game or activity with the other user (if the other user chose to play the game or participate in the activity).

</div>
No

Yes

<div class="clsListStd">

# Brought into the Conversation window with another user whose e-mail address was specified by the BOT parameter.
# Presented with the Conversation window, from which the user can select which game or activity to share with the other user.
# Offered the opportunity to select the desired game or activity with the other user.

</div>
Yes

Yes

<div class="clsListStd">

# Brought into the conversation window with another user whose e-mail address was specified by the BOT parameter.
# Presented with an invitation (after the Conversation window opens) for the application specified by the AppID variable.
# Offered the opportunity to enjoy the game or activity with the other user (if the other user chose to play the game or participate in the activity).

</div>