Practical debugging - Revizyon geçmişi

Ricardorix: /* Debugging my Javascript game interface logic */

2019-04-05T10:41:28Z

Debugging my Javascript game interface logic

← Önceki sürüm		12.41, 5 Nisan 2019 tarihindeki hâli
98. satır:		98. satır:
	* You can even modify directly some CSS properties and see how it looks immediately in the game interface.		* You can even modify directly some CSS properties and see how it looks immediately in the game interface.

	== Debugging my Javascript game interface logic ==		=== Debugging my Javascript game interface logic ===

	Compared to PHP debugging, Javascript debugging can sometimes be painful.		Compared to PHP debugging, Javascript debugging can sometimes be painful.
138. satır:		138. satır:
	Refresh the page F5, and make sure you have the Developer tools window open, press F12.		Refresh the page F5, and make sure you have the Developer tools window open, press F12.
	When the break-point is hit you can then step through your code and visualise variables, etc.		When the break-point is hit you can then step through your code and visualise variables, etc.


	== Online format checkers ==		== Online format checkers ==

Ricardorix: /* Online format checkers */

2019-04-05T10:40:27Z

Online format checkers

← Önceki sürüm		12.40, 5 Nisan 2019 tarihindeki hâli
141. satır:		141. satır:

	== Online format checkers ==		== Online format checkers ==
			Copy and paste code for a quick code sanity check like the right number of brackets.

	PHP: [https://phpcodechecker.com/ https://phpcodechecker.com/]		PHP: [https://phpcodechecker.com/ https://phpcodechecker.com/]

Ricardorix: /* Online format checkers */

2019-04-05T10:39:20Z

Online format checkers

← Önceki sürüm		12.39, 5 Nisan 2019 tarihindeki hâli
142. satır:		142. satır:
	== Online format checkers ==		== Online format checkers ==
	PHP: [https://phpcodechecker.com/ https://phpcodechecker.com/]		PHP: [https://phpcodechecker.com/ https://phpcodechecker.com/]

	JS: [http://esprima.org/demo/validate.html http://esprima.org/demo/validate.html]		JS: [http://esprima.org/demo/validate.html http://esprima.org/demo/validate.html]

Ricardorix: /* Online format checkers */

2019-04-05T10:38:41Z

Online format checkers

← Önceki sürüm		12.38, 5 Nisan 2019 tarihindeki hâli
141. satır:		141. satır:

	== Online format checkers ==		== Online format checkers ==
	PHP: [https://phpcodechecker.com/]		PHP: [https://phpcodechecker.com/ https://phpcodechecker.com/]
	JS: [http://esprima.org/demo/validate.html]		JS: [http://esprima.org/demo/validate.html http://esprima.org/demo/validate.html]

	== Some frequent errors ==		== Some frequent errors ==

Ricardorix 10.37, 5 Nisan 2019 tarihinde

2019-04-05T10:37:27Z

← Önceki sürüm		12.37, 5 Nisan 2019 tarihindeki hâli
138. satır:		138. satır:
	Refresh the page F5, and make sure you have the Developer tools window open, press F12.		Refresh the page F5, and make sure you have the Developer tools window open, press F12.
	When the break-point is hit you can then step through your code and visualise variables, etc.		When the break-point is hit you can then step through your code and visualise variables, etc.


			== Online format checkers ==
			PHP: [https://phpcodechecker.com/]
			JS: [http://esprima.org/demo/validate.html]

	== Some frequent errors ==		== Some frequent errors ==

Ricardorix: /* Use Debugger */

2019-04-05T10:34:20Z

Use Debugger

← Önceki sürüm		12.34, 5 Nisan 2019 tarihindeki hâli
132. satır:		132. satır:
	This will stop code execution on that line and will launch the JavaScript debugger.		This will stop code execution on that line and will launch the JavaScript debugger.

	In Chrome, to add a breakpoint: add line to your .js file		In Chrome, to add a breakpoint: add a line to your .js file

	debugger;		debugger;

Ricardorix: /* Use Debugger */

2019-04-05T10:33:40Z

Use Debugger

← Önceki sürüm		12.33, 5 Nisan 2019 tarihindeki hâli
130. satır:		130. satır:
	Modern browsers also allow you to put breakpoints in your js code.		Modern browsers also allow you to put breakpoints in your js code.

	This will stop code execution on that line and will launch the JavaScript debugger		This will stop code execution on that line and will launch the JavaScript debugger.

			In Chrome, to add a breakpoint: add line to your .js file

			debugger;

			Refresh the page F5, and make sure you have the Developer tools window open, press F12.
			When the break-point is hit you can then step through your code and visualise variables, etc.

	== Some frequent errors ==		== Some frequent errors ==

Een: /* Get the database matching a bug report */ Tip for ended games

2018-10-31T15:09:20Z

Get the database matching a bug report: Tip for ended games

← Önceki sürüm		17.09, 31 Ekim 2018 tarihindeki hâli
154. satır:		154. satır:
	* If your changes to player_ids are not taken into account, it may be a cache problem: use the "Clear PHP cache" button on your "Manage game" page.		* If your changes to player_ids are not taken into account, it may be a cache problem: use the "Clear PHP cache" button on your "Manage game" page.
	* Then you should be able to play with the same state of the game as when the report was created in production.		* Then you should be able to play with the same state of the game as when the report was created in production.
			* If the game has ended, you can place it again in the game state you want to debug by setting the value with ID 1 in the global table to the appropriate state value, and the value with ID 2 to the player you want active).

Amadannabriona 19.42, 15 Eylül 2018 tarihinde

2018-09-15T19:42:50Z

← Önceki sürüm		21.42, 15 Eylül 2018 tarihindeki hâli
1. satır:		1. satır:

	This page gives you practical tips to debug your game during ~~the~~ development. Don't hesitate to share with us ~~your difficulties in order~~ we can improve this section.		This page gives you practical tips to debug your game during development. Don't hesitate to share your difficulties with us so that we can improve this section.

	== Tools ==		== Tools ==

	To work on BGA Studio, we recommend you to use [http://www.google.com/chrome Google Chrome] as it's the ~~current~~ fastest browser for BGA platform, and it's available in all OS.		To work on BGA Studio, we recommend that you use [http://www.google.com/chrome Google Chrome] as it's currently the fastest browser for the BGA platform, and it's available for all OSes.

	Another reason to use Chrome is that it ~~embed~~ all tools you need to work on BGA Studio. You can see them by pressing "F12" or from the menu ("Tools > Development tools").		Another reason to use Chrome is that it embeds all the tools you need to work on BGA Studio. You can see them by pressing "F12" or from the menu ("Tools > Development tools").

	A good practice is to use a second browser to develop the game, in order to ~~check~~ that your game is working fine on this browser too.		A good practice is to use a second browser to develop the game, in order to verify that your game is working fine on this browser too.

	To debug with Firefox browser, we advise you to use these 2 extensions:		To debug with Firefox browser, we advise you to use these 2 extensions:
	* [https://addons.mozilla.org/firefox/addon/firebug/ Firebug]		* [https://addons.mozilla.org/firefox/addon/firebug/ Firebug]
	* [https://addons.mozilla.org/firefox/addon/web-developer/ Web ~~developper~~]		* [https://addons.mozilla.org/firefox/addon/web-developer/ Web developer]

	To debug with other browsers (IE, Edge, Opera), we advise you to use one of the most recent versions. Latest versions of the browser will likely have better development tools than the previous ones...		To debug with other browsers (IE, Edge, Opera), we advise you to use one of the most recent versions. Latest versions of the browser will likely have better development tools than the previous ones...
24. satır:		24. satır:
	== Debugging my game when it cannot start ==		== Debugging my game when it cannot start ==

	If your game ~~don~~'t start because of an error, you are probably in one of these situations:		If your game won't start because of an error, you are probably in one of these situations:
	* There is a SQL error in your dbmodel.sql file.		* There is a SQL error in your dbmodel.sql file.
	* You have a syntax error in your PHP file.		* You have a syntax error in your PHP file.
30. satır:		30. satır:

	If the error is not explicitly displayed when you click on "Express start", you should check the "Gameserver error log" as per [[Studio logs]].		If the error is not explicitly displayed when you click on "Express start", you should check the "Gameserver error log" as per [[Studio logs]].
	More cases of why game can't start described in [[Troubleshooting]] page.		More cases of why game can't start are described on the [[Troubleshooting]] page.

	== Debugging my PHP game logic (or my view) ==		== Debugging my PHP game logic (or my view) ==
36. satır:		36. satır:
	Most of the time, debugging PHP is quite easy. Here's what I do when I want to develop/debug some game logic that is triggered by some game action:		Most of the time, debugging PHP is quite easy. Here's what I do when I want to develop/debug some game logic that is triggered by some game action:

	* At first, I make sure that I can reproduce the needed game situation in one click. To do this, I use the "[[Tools_and_tips_of_BGA_Studio#Save_.26_restore_state\|save & restore]]" function.		* At first, I make sure that I can reproduce the needed game situation with one click. To do this, I use the "[[Tools_and_tips_of_BGA_Studio#Save_.26_restore_state\|save & restore]]" function.
	* Another possibility for this is to place a '''die('ok');''' PHP statement right after the PHP I am developing/debugging. This way, I make sure that every request will fail and then nothing will be ~~commited~~ to the database~~, anyway~~.		* Another possibility for this is to place a '''die('ok');''' PHP statement right after the PHP I am developing/debugging. This way, I make sure that every request will fail and then nothing will be committed to the database.
	* Then, I use '''var_dump''' function to dump PHP variables and check what's wrong, until it works.		* Then, I use the '''var_dump''' function to dump PHP variables and check what's wrong, until it works.

	Example:		Example:
75. satır:		75. satır:
	== Debugging my HTML/CSS layout ==		== Debugging my HTML/CSS layout ==

	~~Situation examples:~~		Example situations
	* why my game element doesn't show up in the interface?
	* why my CSS property hasn't been applied to this element?
	* why this game element is displayed at this position?

	A ~~first~~ useful tip when an element does not show up in the interface is to give it a red background:		* Why doesn't my game element show up in the interface?
			* Why hasn't my CSS property been applied to this element?
			* Why is this game element displayed at this position?

			A useful tip when an element does not show up in the interface is to give it a red background:
	<pre>		<pre>
	#my_element {		#my_element {
88. satır:		89. satır:
	</pre>		</pre>

	This way, you know if the element is not visible because of some ~~of its~~ CSS property or because of ~~anything~~ else.		This way, you know if the element is not visible because of some CSS property or because of something else.

	Another tip: sometimes, ~~you change~~ a CSS property ~~with~~ no visible effect on your interface. In that case, add a "display:none" property. If your element does not disappear, the bug probably comes from your CSS selector and not from your CSS property.		Another tip: sometimes, changing a CSS property has no visible effect on your interface. In that case, add a "display:none" property. If your element does not disappear, the bug probably comes from your CSS selector and not from your CSS property.

	Using Chrome "Elements" tab (~~thre~~ first one), you can:		Using Chrome "Elements" tab (the first one), you can:
	* See the CURRENT HTML of your page. Remember that the classical "show page source" is inefficient with BGA as you are modifying the page source with your Javascript code.		* See the CURRENT HTML of your page. Remember that the classical "show page source" is inefficient with BGA as you are modifying the page source with your Javascript code.
	* Using the "magnifying glass", you can click on any part of your game interface and check ~~it's~~ HTML code and associated CSS styles.		* Using the "magnifying glass", you can click on any part of your game interface and check its HTML code and associated CSS styles.
	* You can even modify directly some CSS ~~property~~ and see if how it looks immediately on the game interface.		* You can even modify directly some CSS properties and see how it looks immediately in the game interface.

	== Debugging my Javascript game interface logic ==		== Debugging my Javascript game interface logic ==

	~~Compare~~ to PHP debugging, Javascript debugging can sometimes be painful.		Compared to PHP debugging, Javascript debugging can sometimes be painful.

	Here's are some tips to make your life easier while developing and debugging Javascript:		Here are some tips to make your life easier while developing and debugging Javascript:

	=== Do complex things on PHP side ===		=== Do complex things on the PHP side ===

	The most frequent case is the following: you want to compute possible moves in a game situation. Doing it in Javascript is a nightmare. ~~Then, do~~ it on PHP, and transfer the ~~result~~ to your client interface using the "args" game state property.		The most frequent case is the following: you want to compute possible moves in a game situation. Doing it in Javascript is a nightmare. Do it in PHP, and transfer the results to your client interface using the "args" game state property.

	Note: ~~check~~ Reversi example ~~for this~~.		Note: See the Reversi tutorial for an example.

	=== Add traces in your code ===		=== Add traces in your code ===
123. satır:		124. satır:
	It will popup what you wish and pause the execution until you click ok.		It will popup what you wish and pause the execution until you click ok.

	This won't be useful for complex structures, only native types will ~~get~~ plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.		This won't be useful for complex structures; only native types will be plainly displayed. But this is sometimes useful just with messages to make sure which way the execution goes.

	=== Use Debugger ===		=== Use Debugger ===

	Modern browsers also allow to put breakpoints in your js code.		Modern browsers also allow you to put breakpoints in your js code.

	~~That~~ will stop code execution on that line and will launch the JavaScript debugger		This will stop code execution on that line and will launch the JavaScript debugger

	== Some frequent errors ==		== Some frequent errors ==
138. satır:		139. satır:

	When a player creates a bug report in production, a snapshot of the game database is taken. You can get access to this snapshot from the studio by following the steps below:		When a player creates a bug report in production, a snapshot of the game database is taken. You can get access to this snapshot from the studio by following the steps below:
	* Create a table on the studio with the same game and number of players as the table for which the report has been written. Launch this table.		* Create a table in the studio with the same game and number of players as the table for which the report has been written. Launch this table.
	* Open another tab on the studio and go to "Manage game" page for your project (you have to be admin for this project)		* Open another tab on the studio and go to "Manage game" page for your project (you have to be admin for this project)
	* In the "Errors in production" section, fill up the fields "Bug report ID" (this is the ID of the bug report in production) and "Studio table ID" (this is the ID of the table you created above) then click the "⇨ Load bug report state into this table save slot #1" button.		* In the "Errors in production" section, fill up the fields "Bug report ID" (this is the ID of the bug report in production) and "Studio table ID" (this is the ID of the table you created above) then click the "⇨ Load bug report state into this table save slot #1" button.

Een: /* Get the database matching a bug report */

2018-08-02T15:28:05Z

Get the database matching a bug report

← Önceki sürüm		17.28, 2 Ağustos 2018 tarihindeki hâli
139. satır:		139. satır:
	When a player creates a bug report in production, a snapshot of the game database is taken. You can get access to this snapshot from the studio by following the steps below:		When a player creates a bug report in production, a snapshot of the game database is taken. You can get access to this snapshot from the studio by following the steps below:
	* Create a table on the studio with the same game and number of players as the table for which the report has been written. Launch this table.		* Create a table on the studio with the same game and number of players as the table for which the report has been written. Launch this table.
	* Open another tab on the studio and go to "Manage ~~your project~~" page for ~~this game~~ (you have to be admin for this project)		* Open another tab on the studio and go to "Manage game" page for your project (you have to be admin for this project)
	* In the "Errors in production" section, fill up the fields "Bug report ID" (this is the ID of the bug report in production) and "Studio table ID" (this is the ID of the table you created above) then click the "⇨ Load bug report state into this table save slot #1" button.		* In the "Errors in production" section, fill up the fields "Bug report ID" (this is the ID of the bug report in production) and "Studio table ID" (this is the ID of the table you created above) then click the "⇨ Load bug report state into this table save slot #1" button.
	* If the snapshot is correctly retrieved, you see a "Done!" message.		* If the snapshot is correctly retrieved, you see a "Done!" message.
	* Go back to the tab with your studio table and click "Load 1".		* Go back to the tab with your studio table and click "Load 1".
	* The page refreshes automatically and is broken. This is normal, as the player ids from the snapshot are the player ids of the production, not those of the studio. We'll need to update them.		* The page refreshes automatically and is broken. This is normal, as the player ids from the snapshot are the player ids of the production, not those of the studio. We'll need to update them.
	* Click on the "Go to game database button"		* Click on the "Go to game database" button
	* For each table using player_ids, you'll need to update the player_ids from the production to use the player_ids from the studio. You can see the player_ids from the table page before entering the game by hovering over the player names.		* For each table using player_ids, you'll need to update the player_ids from the production to use the player_ids from the studio. You can see the player_ids from the table page before entering the game by hovering over the player names.
	* Tables to update:		* Tables to update:
151. satır:		151. satır:
	** stats		** stats
	** tables specific to your schema that use player_ids		** tables specific to your schema that use player_ids
			* If your changes to player_ids are not taken into account, it may be a cache problem: use the "Clear PHP cache" button on your "Manage game" page.
	* Then you should be able to play with the same state of the game as when the report was created in production.		* Then you should be able to play with the same state of the game as when the report was created in production.