Miniature/Wishlist/Real-time P2P Miniature - Revision history

imported_>qgil: Miniature/Development/Phase 2.0: Real-time P2P Miniature moved to Miniature/Wishlist/Real-time P2P Miniature: We don't have phases anymore

2011-08-23T18:09:43Z

Miniature/Development/Phase 2.0: Real-time P2P Miniature moved to Miniature/Wishlist/Real-time P2P Miniature: We don't have phases anymore

← Older revision		Revision as of 18:09, 23 August 2011
(No difference)

imported_>jukey: /* Protocol */

2010-04-15T09:55:32Z

Protocol

← Older revision		Revision as of 09:55, 15 April 2010
Line 29:		Line 29:

	=== Protocol ===		=== Protocol ===
			There is a [[/P2P-Protocol\|P2P-Protocol draft]] made by Michael Hasselmann. Please feel free to comment!

	It is safe to assume that each game has some own internal protocol to transfer game states. For chess engines, [http://www.gnu.org/software/xboard/engine-intf.html XBoard/WinBoard] is the standard protocol. But we also need to be able to interface with [http://www.freechess.org/Help/AllFiles.html FICS]/[ftp://ftp.chessclub.com/pub/icc/formats/formats.txt ICS].		It is safe to assume that each game has some own internal protocol to transfer game states. For chess engines, [http://www.gnu.org/software/xboard/engine-intf.html XBoard/WinBoard] is the standard protocol. But we also need to be able to interface with [http://www.freechess.org/Help/AllFiles.html FICS]/[ftp://ftp.chessclub.com/pub/icc/formats/formats.txt ICS].

imported_>amigadave: Category:Miniature

2010-02-11T12:16:33Z

Category:Miniature

← Older revision		Revision as of 12:16, 11 February 2010
Line 55:		Line 55:
	* Getting local contact list		* Getting local contact list
	* Creating tubes connection between clients to sending Miniature data's		* Creating tubes connection between clients to sending Miniature data's

			[[Category:Miniature]]

imported_>dmikulski: /* Progress */

2010-01-12T20:13:34Z

Progress

← Older revision		Revision as of 20:13, 12 January 2010
Line 14:		Line 14:

	==Progress==		==Progress==
			* 2010-01-12: Preparing tp-qt4, patches for building on maemo 5 http://bugs.freedesktop.org/show_bug.cgi?id=26002 http://bugs.freedesktop.org/show_bug.cgi?id=26004
			* 2010-01-11: Preparing scratchbox

	==Mockups==		==Mockups==

imported_>qgil: Undo revision 26356 by qgil (Talk)

2010-01-11T17:45:40Z

Undo revision 26356 by qgil (Talk)

← Older revision		Revision as of 17:45, 11 January 2010
Line 45:		Line 45:
	=== Observing games ===		=== Observing games ===
	Observing games is an important aspect in social gaming. On FICS, observers are known as kibitz. Can that be done with Telepathy, too?		Observing games is an important aspect in social gaming. On FICS, observers are known as kibitz. Can that be done with Telepathy, too?
			:A use case with a phase on its own? --[[User:qgil\|qgil]] 17:37, 11 January 2010 (UTC)
	~~=== FICS details (not strictly P2P related) ===~~
	~~The various intro~~-* help pages for FICS seem to explain everything we'd need ([http://www.freechess.org/Help/HelpFiles/intro_basics.html basics], [http://www.freechess.org/Help/HelpFiles/intro_general.html general], [http://www.freechess.org/Help/HelpFiles/intro_information.html information], [http://www.freechess.org/Help/HelpFiles/intro_moving.html moving], [http://www.freechess.org/Help/HelpFiles/intro_playing.html playing], [~~http://www.freechess.org/Help/HelpFiles/intro_analysis.html analysis],~~ [~~http~~:~~//www.freechess.org/Help/HelpFiles/intro_settings.html settings~~]~~, [http://www.freechess.org/Help/HelpFiles/intro_talking.html talking~~]).

	Playing on FICS would happen via telnet (telnet freechess.org), perhaps Telepathy could also handle the connection management for that. This would reduce the risk to maintain two different code bases in Miniature (P2P, FICS) that eventually do the same. My hope is that Miniature only needs to know about XBoard whereas P2P/FICS/ICS would all happen in the Telepathy component.

	~~On a side note~~: ~~It also seems to be common for network games to have those two protocols - one for finding games (a game servers browser of some sort~~, ~~see [http://www.qtracker.com/]) and one for the actual game. The separation into two truly distinct protocols might rarely exist~~ (~~again, see FICS~~).

	~~=== Interoperability ===~~
	~~With XBoard it would seem trivial to play chess across application boundaries.~~

	=== Telepathy tubes Details ===		=== Telepathy tubes Details ===

imported_>qgil at 17:43, 11 January 2010

2010-01-11T17:43:26Z

@@ Line 18: / Line 18: @@
 ==Backstage==
 === Session negotiation ===
@@ Line 52: / Line 45: @@
 === Observing games ===
 Observing games is an important aspect in social gaming. On FICS, observers are known as kibitz. Can that be done with Telepathy, too?
-:A use case with a phase on its own? --[[User:qgil|qgil]] 17:37, 11 January 2010 (UTC)

imported_>qgil: /* FICS details (not strictly P2P related) */

2010-01-11T17:39:25Z

FICS details (not strictly P2P related)

← Older revision		Revision as of 17:39, 11 January 2010
Line 53:		Line 53:
	Observing games is an important aspect in social gaming. On FICS, observers are known as kibitz. Can that be done with Telepathy, too?		Observing games is an important aspect in social gaming. On FICS, observers are known as kibitz. Can that be done with Telepathy, too?
	:A use case with a phase on its own? --[[User:qgil\|qgil]] 17:37, 11 January 2010 (UTC)		:A use case with a phase on its own? --[[User:qgil\|qgil]] 17:37, 11 January 2010 (UTC)

	~~=== FICS details (not strictly P2P related) ===~~
	The various intro-* help pages for FICS seem to explain everything we'd need ([http://www.freechess.org/Help/HelpFiles/intro_basics.html basics], [http://www.freechess.org/Help/HelpFiles/intro_general.html general], [http://www.freechess.org/Help/HelpFiles/intro_information.html information], [http://www.freechess.org/Help/HelpFiles/intro_moving.html moving], [http://www.freechess.org/Help/HelpFiles/intro_playing.html playing], [http://www.freechess.org/Help/HelpFiles/intro_analysis.html analysis], [http://www.freechess.org/Help/HelpFiles/intro_settings.html settings], [http://www.freechess.org/Help/HelpFiles/intro_talking.html talking]).

	Playing on FICS would happen via telnet (telnet freechess.org), perhaps Telepathy could also handle the connection management for that. This would reduce the risk to maintain two different code bases in Miniature (P2P, FICS) that eventually do the same. My hope is that Miniature only needs to know about XBoard whereas P2P/FICS/ICS would all happen in the Telepathy component.

	On a side note: It also seems to be common for network games to have those two protocols - one for finding games (a game servers browser of some sort, see [http://www.qtracker.com/]) and one for the actual game. The separation into two truly distinct protocols might rarely exist (again, see FICS).

imported_>qgil: Comment on the use case of observing games.

2010-01-11T17:37:24Z

Comment on the use case of observing games.

← Older revision		Revision as of 17:37, 11 January 2010
Line 52:		Line 52:
	=== Observing games ===		=== Observing games ===
	Observing games is an important aspect in social gaming. On FICS, observers are known as kibitz. Can that be done with Telepathy, too?		Observing games is an important aspect in social gaming. On FICS, observers are known as kibitz. Can that be done with Telepathy, too?
			:A use case with a phase on its own? --[[User:qgil\|qgil]] 17:37, 11 January 2010 (UTC)

	=== FICS details (not strictly P2P related) ===		=== FICS details (not strictly P2P related) ===
Line 59:		Line 60:

	On a side note: It also seems to be common for network games to have those two protocols - one for finding games (a game servers browser of some sort, see [http://www.qtracker.com/]) and one for the actual game. The separation into two truly distinct protocols might rarely exist (again, see FICS).		On a side note: It also seems to be common for network games to have those two protocols - one for finding games (a game servers browser of some sort, see [http://www.qtracker.com/]) and one for the actual game. The separation into two truly distinct protocols might rarely exist (again, see FICS).

	~~=== Interoperability ===~~
	~~With XBoard it would seem trivial to play chess across application boundaries.~~

imported_>qgil: Miniature/Development/Phase 2: Real-time P2P chess moved to Miniature/Development/Phase 2.0: Real-time P2P Miniature: Page for a specific phase

2010-01-11T17:31:02Z

Miniature/Development/Phase 2: Real-time P2P chess moved to Miniature/Development/Phase 2.0: Real-time P2P Miniature: Page for a specific phase

← Older revision	Revision as of 17:31, 11 January 2010
(No difference)

imported_>qgil: /* Backstage */

2010-01-11T17:29:20Z

Backstage

← Older revision		Revision as of 17:29, 11 January 2010
Line 18:		Line 18:

	==Backstage==		==Backstage==

			=== Telepathy tubes Details ===
			* Compiling Miniature for maemo (it's really needed for now?)
			* Compiling telepathy-qt4 for maemo (?)
			* Creating session controller, connection server
			* Getting local contact list
			* Creating tubes connection between clients to sending Miniature data's

	=== Session negotiation ===		=== Session negotiation ===
Line 31:		Line 38:
	Interestingly enough, most chess bots that play on FICS probably don't implement the network protocol themselves but instead use XBoard. XBoard then interfaces with FICS for them.		Interestingly enough, most chess bots that play on FICS probably don't implement the network protocol themselves but instead use XBoard. XBoard then interfaces with FICS for them.

	=== ~~FICS details (not strictly P2P related)~~ ===		=== Save/resume ===
	~~The various intro-* help pages for FICS seem~~ to explain everything we'd need ([http://www.freechess.org/Help/HelpFiles/intro_basics.html basics], [http://www.freechess.org/Help/HelpFiles/intro_general.html general], [http://www.freechess.org/Help/HelpFiles/intro_information.html information], [http://www.freechess.org/Help/HelpFiles/intro_moving.html moving], [http://www.freechess.org/Help/HelpFiles/intro_playing.html playing], [http://www.freechess.org/Help/HelpFiles/intro_analysis.html analysis], [http://www.freechess.org/Help/HelpFiles/intro_settings.html settings], [http://www.freechess.org/Help/HelpFiles/intro_talking.html talking]).		Players should be able to save a game and resume it another day. Part of Session negotiation or an own item?

	~~Playing on FICS would happen via telnet (telnet freechess.org), perhaps Telepathy could also handle the~~ connection management for that. This would reduce the risk to maintain two different code bases in Miniature (P2P, FICS) that eventually do the same. My hope is that Miniature only needs to know about XBoard whereas P2P/FICS/ICS would all happen in the Telepathy component.		=== Error recovery ===
			When to abort a connection etc.

	~~On a side note: It also seems to~~ be ~~common for network games~~ to ~~have those two protocols - one for finding games (~~a game ~~servers browser of some sort,~~ see ~~[http://www.qtracker.com/]) and one for~~ the ~~actual game. The separation into two truly distinct protocols might rarely exist (again, see FICS)~~.		=== Calendar integration ===
			Players should be able to arrange a game at a certain time and see their scheduled chess games in the Maemo calendar. Part of this phase or a phase in its own?

	=== ~~Interoperability~~ ===		=== Status notification ===
	~~With XBoard it would seem trivial to play~~ chess ~~across application boundaries~~.		Tell other users in my contacts list about my chess game.

	=== Observing games ===		=== Observing games ===
	Observing games is an important aspect in social gaming. On FICS, observers are known as kibitz. Can that be done with Telepathy, too?		Observing games is an important aspect in social gaming. On FICS, observers are known as kibitz. Can that be done with Telepathy, too?

	=== ~~Status notification~~ ===		=== FICS details (not strictly P2P related) ===
	~~Tell other users~~ in ~~my contacts list~~ about ~~my chess game~~.		The various intro-* help pages for FICS seem to explain everything we'd need ([http://www.freechess.org/Help/HelpFiles/intro_basics.html basics], [http://www.freechess.org/Help/HelpFiles/intro_general.html general], [http://www.freechess.org/Help/HelpFiles/intro_information.html information], [http://www.freechess.org/Help/HelpFiles/intro_moving.html moving], [http://www.freechess.org/Help/HelpFiles/intro_playing.html playing], [http://www.freechess.org/Help/HelpFiles/intro_analysis.html analysis], [http://www.freechess.org/Help/HelpFiles/intro_settings.html settings], [http://www.freechess.org/Help/HelpFiles/intro_talking.html talking]).

			Playing on FICS would happen via telnet (telnet freechess.org), perhaps Telepathy could also handle the connection management for that. This would reduce the risk to maintain two different code bases in Miniature (P2P, FICS) that eventually do the same. My hope is that Miniature only needs to know about XBoard whereas P2P/FICS/ICS would all happen in the Telepathy component.

	~~=== Error recovery ===~~		On a side note: It also seems to be common for network games to have those two protocols - one for finding games (a game servers browser of some sort, see [http://www.qtracker.com/]) and one for the actual game. The separation into two truly distinct protocols might rarely exist (again, see FICS).
	~~When~~ to ~~abort~~ a ~~connection etc~~.

	=== ~~Telepathy tubes Details~~ ===		=== Interoperability ===
	~~- Compiling Miniature for maemo (~~it~~'s really needed for now?)~~		With XBoard it would seem trivial to play chess across application boundaries.
	~~- Compiling telepathy-qt4 for maemo (?)~~
	~~- Creating session controller, connection server~~
	~~- Getting local contact list~~
	~~- Creating tubes connection between clients~~ to ~~sending Miniature data's~~