<html>
<body>
<div style="font-family: Verdana, Arial, Helvetica, Sans-Serif;">
<table bgcolor="#f9f3c9" width="100%" cellpadding="8" style="border: 1px #c9c399 solid;">
<tr>
<td>
This is an automatically generated e-mail. To reply, visit:
<a href="http://git.reviewboard.kde.org/r/106772/">http://git.reviewboard.kde.org/r/106772/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On October 12th, 2012, 10:49 p.m., <b>Roney Gomes</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Hello Jaime.
I've applied your patch and did some tests, here go my conclusions:
1. A player is allowed to change the current rule at any time, which allows the player to, let's say, cheat at will. I think that this rule should be chosen before each game, and could be changed only when the current game is over.
2. In a network game, players can play under different rules. One possible way to solve this would be to add a QCheckBox in the dialog which appears when a player decides to host a new game. This way the host would decide whether the match will be given under the new rule or not.
My idea, aiming to make the user experience consistent through both game modes, is:
a) Prompt a dialog to the user before a single player match. In this dialog he/she would change his/her nickname, set the AI difficulty and the rule to player under.
b) Prompt a dialog to the user before a network match, in order to let him set his/her nickname, the port to make the connection and the game rule.
Notice that in "a" we are going to make the status bar useless, since it's only feature is to change the AI level. So, if we are really going to add this new feature, which is very likely, some redesign is required and the network issue definitely have to be solved.
These are my opinions. If you have a different approach to the issues pointed above, let me know about it.
Best regards.</pre>
</blockquote>
<p>On October 13th, 2012, 9:32 a.m., <b>Jaime Torres Amate</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">What about this idea (I just don't like the idea of pressing two buttons for every game)?
Instead of a dialog, showing/settings all this things in the presentation screen (could be over a translucent background, like in kpatience or khangman winner/looser), this way, only a button is required.
In any case, I think this could be a question for the usability team.</pre>
</blockquote>
</blockquote>
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">I understand your point. In this case we could the following: instead of prompting a dialog in the single player mode, we would let the game the way it already is, i.e. the player can allow/disallow the rule via the settings menu.
Now, regarding the network mode, we'd have to add an option in the dialog which appears before each game. This option would reflect the decision made by the player in the single player mode, it will be there for the case in which the player decides to change it.
So, if we agree about that, a few things remain to be made:
1. Only allow the player to change this rule before a new game.
2. Add a new option in the network dialog.
3. Enforce the rule in the network mode.
What you think?</pre>
<br />
<p>- Roney</p>
<br />
<p>On October 11th, 2012, 8:15 a.m., Jaime Torres Amate wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://git.reviewboard.kde.org/media/rb/images/review_request_box_top_bg.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for KDE Games.</div>
<div>By Jaime Torres Amate.</div>
<p style="color: grey;"><i>Updated Oct. 11, 2012, 8:15 a.m.</i></p>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Description </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Add the option to allow adjacent ships.
When it is not checked, the ships can not be placed adjacent.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Testing </h1>
<table width="100%" bgcolor="#ffffff" cellspacing="0" cellpadding="10" style="border: 1px solid #b8b5a0">
<tr>
<td>
<pre style="margin: 0; padding: 0; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">tested locally.</pre>
</td>
</tr>
</table>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Bugs: </b>
<a href="http://bugs.kde.org/show_bug.cgi?id=168659">168659</a>
</div>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>src/battlefield.cpp <span style="color: grey">(32aa525)</span></li>
<li>src/kbattleship.kcfg <span style="color: grey">(b615f30)</span></li>
<li>src/kbattleshipui.rc <span style="color: grey">(7c51ac6)</span></li>
<li>src/mainwindow.cpp <span style="color: grey">(a7cceeb)</span></li>
<li>src/playfield.h <span style="color: grey">(56934dc)</span></li>
<li>src/playfield.cpp <span style="color: grey">(61c0ac6)</span></li>
<li>src/ship.h <span style="color: grey">(5e35f1a)</span></li>
<li>src/ship.cpp <span style="color: grey">(86858d9)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/106772/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>