<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://svn.reviewboard.kde.org/r/5754/">http://svn.reviewboard.kde.org/r/5754/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On November 2nd, 2010, 11:32 a.m., <b>Frederik Schwarzer</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;">I think consistency is nice even at places that are not seem much.
Is it possible to keep the old options but do not show them to the user?
If so, I would prefer doing that for a while as the non-breaking way.
If not, I still think it should not be such a big problem. So I
am fine with this change.</pre>
</blockquote>
<p>On November 2nd, 2010, 1:01 p.m., <b>Parker Coates</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;">I had considered that, but as far as I can tell KCmdLineArgs/KCmdLineOptions reject any arguments that are not explicitly listed. Even if it did, I'm not convinced we'd want to clutter up the code by checking both alternatives.
Thanks.</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;">Me neither. I consider the problem of changing the options too small to justify the extra code.
(I just wanted to ask :))</pre>
<br />
<p>- Frederik</p>
<br />
<p>On November 2nd, 2010, 1:52 p.m., Parker Coates wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://svn.reviewboard.kde.orgrb/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 Parker Coates.</div>
<p style="color: grey;"><i>Updated 2010-11-02 13:52:35</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;">Tonight I noticed that Klickety was using --CamelCase for its command line options instead of KDE's "standard" --lower-case-hyphenated. When I asked Ni about it he said he just copied the formatting from KDiamond. This prompted me to take a look around the module and produce this patch. It corrects all the "non-standard" options I could find.
(Note that while lower-casing is near universal in KDE apps, hyphenation versus alloneword is not as clear cut. After an informal survey of some popular KDE applications it does seem that hyphenation is the more popular option.)
Since, Klickety is a new app, I believe its options should be fixed, but I'm not really sure about the rest. On the one hand, consistency is really nice to have. On the other, changing the options could theoretically break existing scripts and shortcuts. On the one hand, command line arguments (especially those included in this patch) are quite unlikely to be much used. On the other, if they're not heavily used, why would we care if they're consistent or not.
So I thought I'd throw up this patch as a point of conversation. What do people think.</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;">None. If we agree that this patch (or part of it) is worth doing I'll test that the renamed options work as expected.</pre>
</td>
</tr>
</table>
<h1 style="color: #575012; font-size: 10pt; margin-top: 1.5em;">Diffs</b> </h1>
<ul style="margin-left: 3em; padding-left: 0;">
<li>trunk/KDE/kdegames/doc/kajongg/index.docbook <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/doc/klickety/index.docbook <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/kajongg/src/kajongg.py <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/kajongg/src/server.py <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/katomic/main.cpp <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/kdiamond/src/main.cpp <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/kfourinline/src/main.cpp <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/klickety/ksame.desktop <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/klickety/main.cpp <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/knetwalk/src/main.cpp <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/kpat/main.cpp <span style="color: grey">(1192115)</span></li>
<li>trunk/KDE/kdegames/lskat/src/main.cpp <span style="color: grey">(1192115)</span></li>
</ul>
<p><a href="http://svn.reviewboard.kde.org/r/5754/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>