<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/110992/">http://git.reviewboard.kde.org/r/110992/</a>
</td>
</tr>
</table>
<br />
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<p style="margin-top: 0;">On June 13th, 2013, 11:44 a.m. UTC, <b>Aleix Pol Gonzalez</b> wrote:</p>
<blockquote style="margin-left: 1em; border-left: 2px solid #d0d0d0; padding-left: 10px;">
<table width="100%" border="0" bgcolor="white" style="border: 1px solid #C0C0C0; border-collapse: collapse; margin: 2px padding: 2px;">
<thead>
<tr>
<th colspan="4" bgcolor="#F0F0F0" style="border-bottom: 1px solid #C0C0C0; font-size: 9pt; padding: 4px 8px; text-align: left;">
<a href="http://git.reviewboard.kde.org/r/110992/diff/2/?file=149817#file149817line51" style="color: black; font-weight: bold; text-decoration: underline;">analitzaplot/plotsdictionarymodel.cpp</a>
<span style="font-weight: normal;">
(Diff revision 2)
</span>
</th>
</tr>
</thead>
<tbody style="background-color: #e4d9cb; padding: 4px 8px; text-align: center;">
<tr>
<td colspan="4"><pre style="font-size: 8pt; line-height: 140%; margin: 0; ">using namespace Analitza;</pre></td>
</tr>
</tbody>
<tbody>
<tr>
<th bgcolor="#b1ebb0" style="border-right: 1px solid #C0C0C0;" align="right"><font size="2"></font></th>
<td bgcolor="#c5ffc4" width="50%"><pre style="font-size: 8pt; line-height: 140%; margin: 0; "></pre></td>
<th bgcolor="#b1ebb0" style="border-left: 1px solid #C0C0C0; border-right: 1px solid #C0C0C0;" align="right"><font size="2">46</font></th>
<td bgcolor="#c5ffc4" width="50%"><pre style="font-size: 8pt; line-height: 140%; margin: 0; "> <span class="n">QString</span> <span class="n">dimString</span><span class="o">=</span><span class="n">stream</span><span class="p">.</span><span class="n">readLine</span><span class="p">();</span></pre></td>
</tr>
</tbody>
</table>
<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 don't think I like to specify the dimension here. We can get the (available) dimensions for a said expression, why do we need to enforce a dictionary dimension when we can decide it on runtime.
If we want to specify it for the dictionary, I'd suggest to create separate .desktop files that describe the dictionaries, but having the metadata there is not good. Especially if you're suggesting to put a line such as dimension := 2 and then you only check for contains("2")</pre>
</blockquote>
<p>On June 13th, 2013, 12:51 p.m. UTC, <b>Punit Mehta</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 don't think I like to specify the dimension here. We can get the (available) dimensions for a said expression, why do we need to enforce a dictionary dimension when we can decide it on runtime.
-> Yes.. we can decide it on run-time ( As you have also suggested, using Analitza::PlotsFactory::self()->requestPlot(exp, Analitza::Dim2D).canDraw() ) .. but I think this may slow down the process of plotting in the application because , we need to keep checking about the dimension and request for the plots whenever the user switches in different plot-names and accordingly change the model for the views ( from PlotsView2D to PlotsView3D and vice versa ).
-> Where as , it is very likely that each plot file will contain the plots of the same dimension.
If we don't want to have the dimension for the dictionary still , then I can even change the code :) and can find an alternate way , but as I said , it might slow down the execution :) </pre>
</blockquote>
</blockquote>
<pre style="margin-left: 1em; white-space: pre-wrap; white-space: -moz-pre-wrap; white-space: -pre-wrap; white-space: -o-pre-wrap; word-wrap: break-word;">We won't know if it slows down until we try it :)</pre>
<br />
<p>- Aleix</p>
<br />
<p>On June 13th, 2013, 12:51 p.m. UTC, Punit Mehta wrote:</p>
<table bgcolor="#fefadf" width="100%" cellspacing="0" cellpadding="8" style="background-image: url('http://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, Aleix Pol Gonzalez and Percy Camilo Triveño Aucahuasi.</div>
<div>By Punit Mehta.</div>
<p style="color: grey;"><i>Updated June 13, 2013, 12:51 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;">Improvement in the code of plotsdictionarymodel class in analitzaplot.
1) Initially , the constructor itself creates the dictionary. Now , the constructor just initializes the object and user/programmer can create the dictionary according to the wish and the flow of the program.
2) Also , I have added some improvements to support plotting from the dictionary for both the dimensions ( dim2D and dim3D ). For that , the assumption is that the dictionary file ( .plots file ) will contain the dimension in the first line as a comment ( e.g. [// dimension :=2 //] code in the first line in .plot file).
3) I have also added some other dictionary files ( for dim2D and dim3D ) so that other application based on Analitza ( in my case Khipu ) can use the dictionary support very well. These dictionary files are just for testing purpose. I am still looking forward in creating a rich collection of dictionary files.
Here, the dictionary files will be installed in the directory whose path will be like : [ default-kde-path / libanalitza /plots ].
-> Once , the change will be merged in analitzaplot , khipu can also work very well as far as the dictionary support is concerned. :) </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;">Done.. works in khipu .. but I am not sure if other part of analitza uses plotsdictionarymodel. If that is the case , then we need to change the code for that class also . but as fas as I know , there is not any other class which depends on plotsdictionarymodel in analitza.</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>analitzaplot/data/plots/3Ds.plots <span style="color: grey">(PRE-CREATION)</span></li>
<li>analitzaplot/data/plots/basic_curves.plots <span style="color: grey">(42d8ec7)</span></li>
<li>analitzaplot/data/plots/conics.plots <span style="color: grey">(PRE-CREATION)</span></li>
<li>analitzaplot/data/plots/polar.plots <span style="color: grey">(PRE-CREATION)</span></li>
<li>analitzaplot/plotsdictionarymodel.h <span style="color: grey">(a308cdc)</span></li>
<li>analitzaplot/plotsdictionarymodel.cpp <span style="color: grey">(3e99167)</span></li>
</ul>
<p><a href="http://git.reviewboard.kde.org/r/110992/diff/" style="margin-left: 3em;">View Diff</a></p>
</td>
</tr>
</table>
</div>
</body>
</html>