Synergy Messaging Plugins - Revision history

Invalidopcode at 22:45, 21 April 2012

2012-04-21T22:45:43Z

Invalidopcode at 22:44, 21 April 2012

2012-04-21T22:44:16Z

Invalidopcode at 22:42, 21 April 2012

2012-04-21T22:42:01Z

Invalidopcode at 22:23, 21 April 2012

2012-04-21T22:23:02Z

Invalidopcode: Created page with "== How Synergy Messaging Plugins Work == Basics of how a Synergy connector works: A service must be registered to handle an account, then an account must be created. When the ac..."

2012-04-21T22:17:48Z

Created page with "== How Synergy Messaging Plugins Work == Basics of how a Synergy connector works: A service must be registered to handle an account, then an account must be created. When the ac..."

New page

== How Synergy Messaging Plugins Work ==

Basics of how a Synergy connector works: A service must be registered to handle an account, then an account must be created. When the account is enabled in the Accounts app, then it will be available for the Messaging app to use. When the Messaging app wants to send a message, it will insert an object into the system database, which the service will then query and then handle the sending of the message. Similarly, when a message is received, the service will place an object into the system database, where the Messaging app will handle the notification and displaying of the message.

← Older revision		Revision as of 22:45, 21 April 2012
Line 33:		Line 33:
	}		}
	</source>		</source>
		+
		+	Description of the properties:
		+
		+	'''id''': The a

← Older revision		Revision as of 22:44, 21 April 2012
Line 31:		Line 31:
	"imloginstate": "com.example.service.loginstate:1",		"imloginstate": "com.example.service.loginstate:1",
	"imcommand": "com.example.service.imcommand:1"		"imcommand": "com.example.service.imcommand:1"
−	}	+	}
	</source>		</source>

← Older revision		Revision as of 22:42, 21 April 2012
Line 4:		Line 4:

	Basics of how a Synergy connector works: A service must be registered to handle an account, then an account must be created. When the account is enabled in the Accounts app, then it will be available for the Messaging app to use. When the Messaging app wants to send a message, it will insert an object into the system database, which the service will then query and then handle the sending of the message. Similarly, when a message is received, the service will place an object into the system database, where the Messaging app will handle the notification and displaying of the message.		Basics of how a Synergy connector works: A service must be registered to handle an account, then an account must be created. When the account is enabled in the Accounts app, then it will be available for the Messaging app to use. When the Messaging app wants to send a message, it will insert an object into the system database, which the service will then query and then handle the sending of the message. Similarly, when a message is received, the service will place an object into the system database, where the Messaging app will handle the notification and displaying of the message.
		+
		+	== Registering the Service ==
		+
		+	Every Synergy connector needs to specify a capability provider with the MESSAGING capability in an account-template.json file. The following is an example of an account-template.json file:
		+
		+	<source lang="javascript">
		+	{
		+	"id":"com.example.account.im",
		+	"loc_name": "Example",
		+	"loc_shortName": "Example",
		+	"capability":"MESSAGING",
		+	"capabilitySubtype": "IM",
		+	"serviceName":"type_example",
		+	"supportsInvisibleStatus": false,
		+	"implementation": "palm://com.example.service/",
		+	"onEnabled": "palm://com.example.service/onEnabled",
		+	"onCredentialsChanged": "palm://com.example.service/onCredentialsChanged",
		+	"loginStateChanged": "palm://com.example.service/loginStateChanged",
		+	"sendIM": "palm://com.example.service/sendIM",
		+	"sendCommand": "palm://com.example.service/sendCommand",
		+	"chatWithNonBuddies": true,
		+	"readOnlyData": false,
		+	"icon": { "loc_32x32": "images/example32.png", "loc_48x48": "images/example48.png", "splitter": "images/example32.png" },
		+	"dbkinds": {
		+	"immessage": "com.example.service.immessage:1",
		+	"imloginstate": "com.example.service.loginstate:1",
		+	"imcommand": "com.example.service.imcommand:1"
		+	}
		+	</source>

← Older revision		Revision as of 22:23, 21 April 2012
Line 1:		Line 1:
		+	{{warning\|This page is a work-in-progress!}}
		+
	== How Synergy Messaging Plugins Work ==		== How Synergy Messaging Plugins Work ==

	Basics of how a Synergy connector works: A service must be registered to handle an account, then an account must be created. When the account is enabled in the Accounts app, then it will be available for the Messaging app to use. When the Messaging app wants to send a message, it will insert an object into the system database, which the service will then query and then handle the sending of the message. Similarly, when a message is received, the service will place an object into the system database, where the Messaging app will handle the notification and displaying of the message.		Basics of how a Synergy connector works: A service must be registered to handle an account, then an account must be created. When the account is enabled in the Accounts app, then it will be available for the Messaging app to use. When the Messaging app wants to send a message, it will insert an object into the system database, which the service will then query and then handle the sending of the message. Similarly, when a message is received, the service will place an object into the system database, where the Messaging app will handle the notification and displaying of the message.