<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/104175/">http://git.reviewboard.kde.org/r/104175/</a>
</td>
</tr>
</table>
<br />
<pre style="white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">Disclaimer: I'm not very familiar with the problem the patch tries to solve. At a first glance, though, dealing with dateline issues in the projections seems like the right approach to me.
Just by looking at the amount of qDebug() statements, I wonder if another programmer gets a clou from the tests if he (accidently) made them fail? Are the tests detailed enough to catch common mistakes even w/o looking at the debug output (and interpret it properly)?
IMO, either the tests should be more detailed to catch improper modifications automatically, or the debug statements should be removed.</pre>
<br />
<p>- Bernhard</p>
<br />
<p>On March 6th, 2012, 7:27 p.m., Thibaut Gridel 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 and Torsten Rahn.</div>
<div>By Thibaut Gridel.</div>
<p style="color: grey;"><i>Updated March 6, 2012, 7:27 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;">Try to separate concerns between Geo coordinates and screen coordinates.
IDL is supposed to be an issue for those projections which have repeatable X property.
As a first attempt, the patch brings IDL calculation into the abstract projection.
Next step is to move horizon and pole for spherical algo, and idl for flat maps.</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;">Projection test tries to handle the 3 tessellation modes across IDL functional cases onto some projections.
Tests are generic enough to catch easy to break regressions.
More tests for Horizon, pole, visibility and projection welcome!</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/lib/Projections/AbstractProjection.cpp <span style="color: grey">(edac2a7)</span></li>
<li>src/lib/Projections/AbstractProjection_p.h <span style="color: grey">(a93ab13)</span></li>
<li>src/lib/geodata/data/GeoDataLineString.cpp <span style="color: grey">(b459dd8)</span></li>
<li>tests/CMakeLists.txt <span style="color: grey">(8e80456)</span></li>
<li>tests/ProjectionTest.cpp <span style="color: grey">(PRE-CREATION)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/104175/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>