Miniature/Development/Architecture - Revision history

amigadave: remove custom category

2010-06-14T13:29:08Z

remove custom category

← Older revision		Revision as of 13:29, 14 June 2010
Line 1:		Line 1:
	[[Category:Miniature]]		[[Category:Miniature]]
-	~~[[Category:MiniatureOutdated]]~~	+	{{out of date}}
-		+
-	~~* The information on this page is outdated *~~	+

	== GUI ==		== GUI ==

mikhas at 21:19, 10 May 2010

2010-05-10T21:19:38Z

← Older revision		Revision as of 21:19, 10 May 2010
Line 2:		Line 2:
	[[Category:MiniatureOutdated]]		[[Category:MiniatureOutdated]]

-	* The information on this page is outdated *	+	* The information on this page is outdated *

	== GUI ==		== GUI ==

mikhas at 21:19, 10 May 2010

2010-05-10T21:19:24Z

← Older revision		Revision as of 21:19, 10 May 2010
Line 1:		Line 1:
-	[[Category:Miniature~~\|Development~~]]	+	[[Category:Miniature]]
		+	[[Category:MiniatureOutdated]]
		+
		+	* The information on this page is outdated *
		+
	== GUI ==		== GUI ==
	* Board		* Board

jukey at 15:24, 21 December 2009

2009-12-21T15:24:06Z

← Older revision		Revision as of 15:24, 21 December 2009
Line 1:		Line 1:
-	[[Category:Miniature]]	+	[[Category:Miniature\|Development]]
	== GUI ==		== GUI ==
	* Board		* Board

mikhas: /* Current design in master branch */

2009-12-08T23:48:21Z

Current design in master branch

← Older revision		Revision as of 23:48, 8 December 2009
Line 63:		Line 63:
	== Current design in master branch ==		== Current design in master branch ==
	The diagram shows classes and their associations. Furthermore, it shows signals and slots. The naming conventions should make clear which slot responds to which signal during runtime. The remaining public API has been left out, because it's all in a flux right now.		The diagram shows classes and their associations. Furthermore, it shows signals and slots. The naming conventions should make clear which slot responds to which signal during runtime. The remaining public API has been left out, because it's all in a flux right now.
-	[[Image:MiniatureArchClassDiagram.png]]	+	[[Image:MiniatureArchClassDiagram.png\|thumb]]

mikhas: /* Current design in master branch */

2009-11-17T08:44:33Z

Current design in master branch

← Older revision		Revision as of 08:44, 17 November 2009
Line 62:		Line 62:

	== Current design in master branch ==		== Current design in master branch ==
		+	The diagram shows classes and their associations. Furthermore, it shows signals and slots. The naming conventions should make clear which slot responds to which signal during runtime. The remaining public API has been left out, because it's all in a flux right now.
	[[Image:MiniatureArchClassDiagram.png]]		[[Image:MiniatureArchClassDiagram.png]]

mikhas: /* Domain */

2009-11-15T11:45:17Z

Domain

← Older revision		Revision as of 11:45, 15 November 2009
Line 16:		Line 16:
	** How it works: Each piece is a QGraphicsSvgItem. This is useful since it allows fingertouchability. The board draws its position, meaning it hides all its piece children. It then asks the pieces pool manager for new pieces (the pool manager of course caches the QGraphicsSvgItems). The pieces are moved to the correct board position, and are made visible (again).		** How it works: Each piece is a QGraphicsSvgItem. This is useful since it allows fingertouchability. The board draws its position, meaning it hides all its piece children. It then asks the pieces pool manager for new pieces (the pool manager of course caches the QGraphicsSvgItems). The pieces are moved to the correct board position, and are made visible (again).
	* Player - information about the other player, like online status, skill level		* Player - information about the other player, like online status, skill level
-	** Player "cards" would be part of this. ~~Currently, they only exist as some HTML-formatted text in~~ the ~~scene view~~.	+	** Player "cards" would be part of this. The player info section on top of the board is fully editable with the Qt Designer, and we could need a good clock ...

	== Communication ==		== Communication ==

mikhas: /* Domain */

2009-11-15T11:32:28Z

Domain

← Older revision		Revision as of 11:32, 15 November 2009
Line 14:		Line 14:
	* Board - Represents the data structure of the board (duh)		* Board - Represents the data structure of the board (duh)
	** Can draw a position based on a valid FEN string, say "rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1" encodes the start position.		** Can draw a position based on a valid FEN string, say "rnbqkbnr/pppppppp/8/8/8/8/PPPPPPPP/RNBQKBNR w KQkq - 0 1" encodes the start position.
-	** How it works: Each ~~figure~~ is a QGraphicsSvgItem. This is useful since it allows fingertouchability. The board draws its position, meaning it ~~removes~~ all its ~~figures~~ children ~~(by deletion) and~~ then ~~re-reads~~ the ~~SVG files into~~ new ~~QGraphicsSvgItem. Needless to say, this is inefficient. A better way would be to let the board load all figures during its construction time, put them in a vector~~ (~~using enums for~~ the ~~indices lookup, maybe) and instead~~ of ~~clearing~~ the ~~board by deletion, just unparent the figures from~~ the board~~, then reparent them into the correct~~ position~~. Or just move them around~~, and ~~hide those that were removed by game moves. Both should be easy and bring a good speed-up~~ (~~SVG loading is quite expensive I hear~~)~~. It is bascially about killing unneeded new/delete sequences~~.	+	** How it works: Each piece is a QGraphicsSvgItem. This is useful since it allows fingertouchability. The board draws its position, meaning it hides all its piece children. It then asks the pieces pool manager for new pieces (the pool manager of course caches the QGraphicsSvgItems). The pieces are moved to the correct board position, and are made visible (again).
	* Player - information about the other player, like online status, skill level		* Player - information about the other player, like online status, skill level
	** Player "cards" would be part of this. Currently, they only exist as some HTML-formatted text in the scene view.		** Player "cards" would be part of this. Currently, they only exist as some HTML-formatted text in the scene view.

mikhas: /* Current design in master branch (2009-11-14) */

2009-11-15T11:27:51Z

Current design in master branch (2009-11-14)

← Older revision		Revision as of 11:27, 15 November 2009
Line 61:		Line 61:
	--[[User:boris_r\|boris_r]] 00:57, 15 November 2009 (UTC)		--[[User:boris_r\|boris_r]] 00:57, 15 November 2009 (UTC)

-	== Current design in master branch ~~(2009-11-14)~~ ==	+	== Current design in master branch ==
	[[Image:MiniatureArchClassDiagram.png]]		[[Image:MiniatureArchClassDiagram.png]]

boris_r: /* Big Blocks Diagram */

2009-11-15T00:57:58Z

Big Blocks Diagram

← Older revision		Revision as of 00:57, 15 November 2009
Line 25:		Line 25:

	== Big Blocks Diagram ==		== Big Blocks Diagram ==
-	[[Image:~~blocks~~.png]]	+	[[Image:Miniature_modules.png]]

	1. MPosition is the centre block, represents a position on the board. Could be encoded as a FEN string or as a 8x8 array with pieces enum'ed or as something else.		1. MPosition is the centre block, represents a position on the board. Could be encoded as a FEN string or as a 8x8 array with pieces enum'ed or as something else.
Line 38:		Line 38:

	6. MExtra and MExtraView - everything else not directly related to a chess - chat, ratings, pictures etc.		6. MExtra and MExtraView - everything else not directly related to a chess - chat, ratings, pictures etc.
		+


Line 54:		Line 55:
	- If the move is not valid, the previous position is sent back to MBoardView, "Illegal move" dialog is displayed		- If the move is not valid, the previous position is sent back to MBoardView, "Illegal move" dialog is displayed

-	--[[User:boris_r\|boris_r]] 17:28, 13 November 2009 (UTC)	+
		+
		+	* Arrows at the left side depict connection to an "outside", whatever "outside" can be. Details about connections, "outside" etc will be defined later. Examples - another player, chess server, adapter to a local chess engine.
		+
		+	--[[User:boris_r\|boris_r]] 00:57, 15 November 2009 (UTC)

	== Current design in master branch (2009-11-14) ==		== Current design in master branch (2009-11-14) ==
	[[Image:MiniatureArchClassDiagram.png]]		[[Image:MiniatureArchClassDiagram.png]]