EventServer - Revision history

Karellen at 23:51, 29 August 2020

2020-08-29T23:51:31Z

← Older revision		Revision as of 23:51, 29 August 2020
Line 98:		Line 98:

	=== J2ME (Java Phone Application) (no longer supported) ===		=== J2ME (Java Phone Application) (no longer supported) ===
	~~{{future note\|17\|~~Support for J2ME client was removed in Kodi v17 via pull request https://github.com/xbmc/xbmc/pull/10049. If you absolutely must have it, revert the changes and follow the instructions to compile it.}}		Support for J2ME client was removed in Kodi v17 via pull request https://github.com/xbmc/xbmc/pull/10049. If you absolutely must have it, revert the changes and follow the instructions to compile it.

	The J2ME client requires the following:		The J2ME client requires the following:

Xhaggi: /* Kodi for Linux */

2018-08-29T07:12:58Z

Kodi for Linux

← Older revision		Revision as of 07:12, 29 August 2018
Line 120:		Line 120:
	* Wii Remote		* Wii Remote
	* J2ME (CellPhone)		* J2ME (CellPhone)
	* [~~http~~://~~trac~~.~~kodi.tv~~/~~ticket~~/~~8827 HAMA~~ MCE Remote]		* [https://github.com/xhaggi/kodi-eventclient-hama-mce Hama MCE Remote Control]

	=== Kodi for Mac OS X ===		=== Kodi for Mac OS X ===

Gamester17: /* J2ME (Java Phone Application) (no longer supported) */

2017-02-02T20:38:55Z

J2ME (Java Phone Application) (no longer supported)

← Older revision		Revision as of 20:38, 2 February 2017
Line 98:		Line 98:

	=== J2ME (Java Phone Application) (no longer supported) ===		=== J2ME (Java Phone Application) (no longer supported) ===
	{{future note\|17\|Support for J2ME client was removed in https://github.com/xbmc/xbmc/pull/10049. If you absolutely must have it, revert the changes and follow the instructions to compile it.}}		{{future note\|17\|Support for J2ME client was removed in Kodi v17 via pull request https://github.com/xbmc/xbmc/pull/10049. If you absolutely must have it, revert the changes and follow the instructions to compile it.}}

	The J2ME client requires the following:		The J2ME client requires the following:

Ned Scott: /* J2ME (Java Phone Application) (no longer supported) */

2016-07-04T11:11:26Z

J2ME (Java Phone Application) (no longer supported)

← Older revision		Revision as of 11:11, 4 July 2016
Line 98:		Line 98:

	=== J2ME (Java Phone Application) (no longer supported) ===		=== J2ME (Java Phone Application) (no longer supported) ===
	Support for J2ME client was removed in https://github.com/xbmc/xbmc/pull/10049. If you absolutely must have it, revert the changes and follow the instructions to compile it.		{{future note\|17\|Support for J2ME client was removed in https://github.com/xbmc/xbmc/pull/10049. If you absolutely must have it, revert the changes and follow the instructions to compile it.}}

	The J2ME client requires the following:		The J2ME client requires the following:

H.udo: /* J2ME (Java Phone Application) (no longer supported) */

2016-07-04T08:14:08Z

J2ME (Java Phone Application) (no longer supported)

← Older revision		Revision as of 08:14, 4 July 2016
Line 98:		Line 98:

	=== J2ME (Java Phone Application) (no longer supported) ===		=== J2ME (Java Phone Application) (no longer supported) ===
	Support for J2ME client was removed in https://github.com/xbmc/xbmc/pull/10049. If you ~~need~~ it, revert ~~back~~ the changes and follow the instructions to compile it.		Support for J2ME client was removed in https://github.com/xbmc/xbmc/pull/10049. If you absolutely must have it, revert the changes and follow the instructions to compile it.

	The J2ME client requires the following:		The J2ME client requires the following:

H.udo: /* J2ME (Java Phone Application) */

2016-07-04T08:12:51Z

J2ME (Java Phone Application)

← Older revision		Revision as of 08:12, 4 July 2016
Line 97:		Line 97:
	The name is by default WiiRemote, but this can be changed with the --joystick-name argument.		The name is by default WiiRemote, but this can be changed with the --joystick-name argument.

	=== J2ME (Java Phone Application) ===		=== J2ME (Java Phone Application) (no longer supported) ===
			Support for J2ME client was removed in https://github.com/xbmc/xbmc/pull/10049. If you need it, revert back the changes and follow the instructions to compile it.

	The J2ME client requires the following:		The J2ME client requires the following:
	* CLDC 1.0 and MIDP 1.0		* CLDC 1.0 and MIDP 1.0

Ned Scott: /* Eden Kodi Options */

2015-05-14T02:50:29Z

Eden Kodi Options

← Older revision		Revision as of 02:50, 14 May 2015
Line 12:		Line 12:
	To change the default Event Server port on Kodi, you must modify guisettings.xml under <services>, find this line "<esport>9777<esport/>", change the port number and save. The file is here: ~/.kodi/userdata/guisettings.xml (this has worked with Openelec for the Raspberry Pi).		To change the default Event Server port on Kodi, you must modify guisettings.xml under <services>, find this line "<esport>9777<esport/>", change the port number and save. The file is here: ~/.kodi/userdata/guisettings.xml (this has worked with Openelec for the Raspberry Pi).

	== Eden ~~Kodi Options~~ ==		== v11 Eden options ==
	:In Eden, the event server is enabled through the "Allow programs on other systems to control Kodi" option. It runs by default on 9777, and can be confirmed by looking in the log at startup for "Starting UDP Event server on 0.0.0.0:9777"		:In v11 (Eden), the event server is enabled through the "Allow programs on other systems to control Kodi" option. It runs by default on 9777, and can be confirmed by looking in the log at startup for "Starting UDP Event server on 0.0.0.0:9777"
	:To change the default port, you must modify advancedsettings.xml , but the exact setting is not known at this time.		:To change the default port, you must modify advancedsettings.xml , but the exact setting is not known at this time.

Ned Scott: /* Kodi Options */

2015-05-14T02:49:56Z

Kodi Options

← Older revision		Revision as of 02:49, 14 May 2015
Line 11:		Line 11:

	To change the default Event Server port on Kodi, you must modify guisettings.xml under <services>, find this line "<esport>9777<esport/>", change the port number and save. The file is here: ~/.kodi/userdata/guisettings.xml (this has worked with Openelec for the Raspberry Pi).		To change the default Event Server port on Kodi, you must modify guisettings.xml under <services>, find this line "<esport>9777<esport/>", change the port number and save. The file is here: ~/.kodi/userdata/guisettings.xml (this has worked with Openelec for the Raspberry Pi).

	~~== Kodi Options ==~~
	~~[[File:Settings.network.remoteeveents.jpg\|right\|600px]]~~
	~~;Enable Remote Events~~
	~~:Check to enable the EventServer.~~
	~~;Remote Events Port~~
	~~:The starting port for the range of ports that EventServer will listen on.~~
	~~;Remote Events Port Range~~
	~~:The number of ports to listen on. Directly determines the port range.~~
	~~;Maximum Number of Clients~~
	~~:The maximum number of simultaneous connections.~~
	~~----~~

	~~;Receive events from other computers~~
	~~:Check to listen on the network, not just on the local machine.~~
	~~----~~

	~~;Initial Repeat Delay (ms)~~
	~~:Delay, in milliseconds, before a continuously pressed button will begin registering as multiple, repeated presses.~~
	~~;Continuous Repeat Delay (ms)~~
	~~:The speed at which the above repeated presses will be entered.~~

	== Eden Kodi Options ==		== Eden Kodi Options ==

Ned Scott: /* Pros and Cons */

2015-05-14T02:49:30Z

Pros and Cons

← Older revision		Revision as of 02:49, 14 May 2015
Line 11:		Line 11:

	To change the default Event Server port on Kodi, you must modify guisettings.xml under <services>, find this line "<esport>9777<esport/>", change the port number and save. The file is here: ~/.kodi/userdata/guisettings.xml (this has worked with Openelec for the Raspberry Pi).		To change the default Event Server port on Kodi, you must modify guisettings.xml under <services>, find this line "<esport>9777<esport/>", change the port number and save. The file is here: ~/.kodi/userdata/guisettings.xml (this has worked with Openelec for the Raspberry Pi).

	~~== Pros and Cons ==~~
	EventServer can be compared to the older web control interface, [[WebServerHTTP-API\|Web Server HTTP API (also known as "HTTPAPI")]]. Below are pros and cons of the EventServer system, compared to HTTP-API. '''NOTE: As of Dharma, the HTTP-API is depreciated - use the JSON-RPC interface instead'''

	~~=== EventServer Pros ===~~
	* is always active on localhost, which is much more stable for remotes (Not available on Kodi for Xbox.)
	* uses event-based communication instead of request-based communication.
	* is much easier to implement in programs.
	* can distinguish between different clients, and therefore have multiple distinct inputs.
	* is mappable through keymap.xml.
	* can notify the user when a connection is made.
	* is capable of displaying notifications on demand.

	~~=== EventServer Cons ===~~

	* currently cannot send any information back to clients. This is a planned feature.
	* is not designed to send built-in Kodi commands like playurl. This may change in the future.


	== Kodi Options ==		== Kodi Options ==

Ned Scott: /* Example demos of EventClients (open source code) */

2015-05-14T02:49:00Z

Example demos of EventClients (open source code)

← Older revision		Revision as of 02:49, 14 May 2015
Line 178:		Line 178:

	=== Example demos of EventClients (open source code) ===		=== Example demos of EventClients (open source code) ===
	You can find several open source EventClient examples written in C++, Python, and Java in the Kodi ~~SVN~~. Look under [https://github.com/xbmc/xbmc/tree/master/tools/EventClients EventClients]. This directory contains seven event client sample programs that demonstrate Kodi's EventServer API. The different programs are in C++, Python, and Java. Kodi must be running to receive events. Please see README.txt for more information.		You can find several open source EventClient examples written in C++, Python, and Java in the Kodi Github. Look under [https://github.com/xbmc/xbmc/tree/master/tools/EventClients EventClients]. This directory contains seven event client sample programs that demonstrate Kodi's EventServer API. The different programs are in C++, Python, and Java. Kodi must be running to receive events. Please see README.txt for more information.

	[[Category:Add-on development]]		[[Category:Add-on development]]
	[[Category:Development]]		[[Category:Development]]