Practical debugging - ประวัติรุ่นแก้ไข

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

2019-04-05T10:41:28Z

Debugging my Javascript game interface logic

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 12:41, 5 เมษายน 2562
บรรทัดที่ 98:		บรรทัดที่ 98:
	* 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:		บรรทัดที่ 138:
	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

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 12:40, 5 เมษายน 2562
บรรทัดที่ 141:		บรรทัดที่ 141:

	== 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

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 12:39, 5 เมษายน 2562
บรรทัดที่ 142:		บรรทัดที่ 142:
	== 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

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 12:38, 5 เมษายน 2562
บรรทัดที่ 141:		บรรทัดที่ 141:

	== 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 เมษายน 2562

2019-04-05T10:37:27Z

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 12:37, 5 เมษายน 2562
บรรทัดที่ 138:		บรรทัดที่ 138:
	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

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 12:34, 5 เมษายน 2562
บรรทัดที่ 132:		บรรทัดที่ 132:
	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

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 12:33, 5 เมษายน 2562
บรรทัดที่ 130:		บรรทัดที่ 130:
	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

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 17:09, 31 ตุลาคม 2561
บรรทัดที่ 154:		บรรทัดที่ 154:
	* 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 กันยายน 2561

2018-09-15T19:42:50Z

แสดงการเปลี่ยนแปลง

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

2018-08-02T15:28:05Z

Get the database matching a bug report

←รุ่นแก้ไขก่อนหน้า		รุ่นแก้ไขเมื่อ 17:28, 2 สิงหาคม 2561
บรรทัดที่ 139:		บรรทัดที่ 139:
	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:		บรรทัดที่ 151:
	** 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.