<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/106988/">http://git.reviewboard.kde.org/r/106988/</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 26th, 2012, noon, <b>Torsten Rahn</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;">So this patch basically copies the existing code into three different places and just for the sake of KAction (which will hopefully go the way of the Dodo for KDE 5 ...) ? I fail to see the advantage.</pre>
</blockquote>
<p>On October 29th, 2012, 2:21 p.m., <b>Bernhard Beschow</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 agree with the fact that copying the code into three different places is not optimal. Still, there is the advantage of not spamming the user's console windows with technical warnings that they're not responsible for, and which might even be irritating ("Do these actions work?"). Moreover, this patch was burried locally on my computer, so I wanted to see if there is a chance to have it in master before the coding style change.
That said, I don't agree with your tone. At least I'm missing some words in your comment which respect my work. Remember that I participate in Marble on a voluntary basis, which should be fun and encuraging. However, if I keep getting complaints rather than constructive feedback for my efforts, I might have to rethink my involvement in Marble. In my opinion, this would be a real pity for both of us since I like to work on Marble, and you - as its founder - probably want to see it prosper, too.
Perhaps my response seems a bit disproportionate. This might be due to the fact that I see no serious interest in fixing IMO important bugs like (a) stalls during panning, (b) proper .gpx support, (c) energy consumption on mobile devices and (d) polishing the user interface towards defined use cases. While I've been working on all four issues, I already got discuraging feedback once I tried to fix (a). So it makes me wonder whether my dedication is worth the effort.</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;">Hello Bernhard,
I'm sorry if my comment looked like a complaint. And I'm surprised to hear that you feel a lack of appreciation for the truely awesome work that you've done for Marble. There are lots of reasons for praising the work that you have done so far for Marble. And I've done that in the past numerous times. You are one of the essential guys who keep Marble ticking and therefore you call the shots - which is great since many of your thoughts are well-reasoned. But we are both striving for excellence and therefore my comments are not meant to question your work - rather the opposite. Sometimes I also just fail to see the problem (like in this case) and therefore ask for explanations. Isn't this the job this reviewboard, doing critical reflexions?
I'm sorry if my comment looked like a complaint. It wasn't meant to be one. I was just seriously asking whether this move would be a good one given the fact that KAction might be removed altogether. Personally I'm not against this patch, so feel free to ship it.
</pre>
<br />
<p>- Torsten</p>
<br />
<p>On October 22nd, 2012, 4:24 p.m., Bernhard Beschow 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 Marble.</div>
<div>By Bernhard Beschow.</div>
<p style="color: grey;"><i>Updated Oct. 22, 2012, 4:24 p.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;">API change: remove RenderPlugin::action()
With this patch, the actions are created outside of the plugins which is more flexible.
In the KDE version, for instance, creation of KActions (rather than QActions) avoids 'marble(26988)/kdeui (kdelibs): Attempt to use QAction "" with KXMLGUIFactory!' warnings.</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>src/QtMainWindow.h <span style="color: grey">(707855f33b12a4508853dd76c8a18bc2bb06cdf6)</span></li>
<li>src/QtMainWindow.cpp <span style="color: grey">(171190097748cadffd2c7aba268fa0ec5f5a8067)</span></li>
<li>src/lib/MarbleWidgetPopupMenu.cpp <span style="color: grey">(4da64b0c84cbe66b59b51f59f3641c5f7879cb05)</span></li>
<li>src/lib/RenderPlugin.h <span style="color: grey">(63df0432bfc3ae4de851cabe92d839bf93c50662)</span></li>
<li>src/lib/RenderPlugin.cpp <span style="color: grey">(373205de5a4e1cd6016ffaf181bf55a1ecf368ba)</span></li>
<li>src/marble_part.h <span style="color: grey">(098d63793904761f997223eff166a6ccd2568389)</span></li>
<li>src/marble_part.cpp <span style="color: grey">(85269d80f1d164fa12a6b6f13f2e3b8ab0172ca1)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/106988/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>