<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="https://git.reviewboard.kde.org/r/117730/">https://git.reviewboard.kde.org/r/117730/</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;">Looks good to me, I wonder though how interval is used. It represents seconds until it should be shown again, but seconds since when? Do we already record the last time each word was shown?</pre>
<br />
<p>- Jeremy Whiting</p>
<br />
<p>On April 24th, 2014, 3:14 a.m. MDT, Inge Wallin wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('https://git.reviewboard.kde.org/static/rb/images/review_request_box_top_bg.ab6f3b1072c9.png'); background-position: left top; background-repeat: repeat-x; border: 1px black solid;">
<tr>
<td>
<div>Review request for KDE Edu, Amarvir Singh and Andreas Cord-Landwehr.</div>
<div>By Inge Wallin.</div>
<p style="color: grey;"><i>Updated April 24, 2014, 3:14 a.m.</i></p>
<div style="margin-top: 1.5em;">
<b style="color: #575012; font-size: 10pt;">Repository: </b>
libkdeedu
</div>
<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;">This patch implements two new fields in a kvtml file:
- pregrade, which is equal to grade but used in the interval 0-1 days as opposed to grade which is used for intervals 1 day and up.
- interval, which is used to indicate how long since a word was last trained it is due for training again.
This is prerequisite to the implementation in Parley of the initial training. The reason for implementing these two fields instead of changing old ones is that it will still be backward compatible. I think this is important, especially in the light of the ktouch issue that we saw on the mailing list a few days ago.</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;">Not much testing is done, that will happen when I implement it in parley. This review is mostly to get an ok on the new data fields in general. The testing that I have done so far is to guarantee that keduvocdocument still works as before for code not using the new API.</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>keduvocdocument/keduvoctext.h <span style="color: grey">(1d196c2)</span></li>
<li>keduvocdocument/keduvoctext.cpp <span style="color: grey">(41d44d0)</span></li>
<li>keduvocdocument/kvtml2defs.h <span style="color: grey">(d2903ed)</span></li>
</ul>
<p><a href="https://git.reviewboard.kde.org/r/117730/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>