<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p><font face="Arial">After
<a class="moz-txt-link-freetext" href="http://mailinglists.scilab.org/Scilab-users-Atoms-Modules-tp4041157.html">http://mailinglists.scilab.org/Scilab-users-Atoms-Modules-tp4041157.html</a>
:<br>
</font></p>
<blockquote type="cite">-------- Message transféré --------
<table class="moz-email-headers-table" cellspacing="0"
cellpadding="0" border="0">
<tbody>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">Date : </th>
<td>Mon, 14 Dec 2020 12:44:24 +0800</td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">From : </th>
<td>Chin Luh Tan <a class="moz-txt-link-rfc2396E" href="mailto:tanchinluh@gmail.com"><tanchinluh@gmail.com></a></td>
</tr>
<tr>
<th valign="BASELINE" nowrap="nowrap" align="RIGHT">To : </th>
<td>Users mailing list for Scilab
<a class="moz-txt-link-rfc2396E" href="mailto:users@lists.scilab.org"><users@lists.scilab.org></a></td>
</tr>
</tbody>
</table>
<br>
<br>
Sometimes it is hard to decide whether to continue maintaining an
atoms module or not.... So I did "snapshots" of downloads on
9/11/2020 21:44 and 14/12/2020 12:20 respectively to see which
modules are in the actual top downloads.
<div><br>
</div>
<div>Still, this is not a fair result, such as IPCV having some
"patches" which will increase the download number, and some
other factors as well. </div>
<div><br>
</div>
So should IPCV continue to be maintained ...? <br>
<div><br>
</div>
<div>Here's the results. </div>
<div><br>
</div>
<table style="border-collapse:collapse;width:265pt" width="354"
cellspacing="0" cellpadding="0" border="0">
<colgroup><col style="width:217pt" width="290"> <col
style="width:48pt" width="64"> </colgroup><tbody>
<tr style="height:14.4pt" height="19">
<td
style="height:14.4pt;width:217pt;padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
width="290" height="19">Image Processing and Computer
Vision Toolbox</td>
<td
style="width:48pt;padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
width="64" align="right">4620</td>
</tr>
<tr style="height:14.4pt" height="19">
<td
style="height:14.4pt;padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
height="19">CPGE</td>
<td
style="padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
align="right">3176</td>
</tr>
<tr style="height:14.4pt" height="19">
<td
style="height:14.4pt;padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
height="19">MinGw toolbox</td>
<td
style="padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
align="right">2946</td>
</tr>
<tr style="height:14.4pt" height="19">
<td
style="height:14.4pt;padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
height="19">Arduino</td>
<td
style="padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
align="right">2936</td>
</tr>
<tr style="height:14.4pt" height="19">
<td
style="height:14.4pt;padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
height="19">CelestLab</td>
<td
style="padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
align="right">2841</td>
</tr>
<tr style="height:14.4pt" height="19">
<td
style="height:14.4pt;padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
height="19"><b>iodelay toolbox</b></td>
<td
style="padding-top:1px;padding-right:1px;padding-left:1px;color:black;font-size:11pt;font-family:Calibri,sans-serif;vertical-align:bottom;border:none;white-space:nowrap"
align="right"><b>2429</b></td>
</tr>
</tbody>
</table>
</blockquote>
<p><br>
This module is a small one, containing a single iodelay() public
function, and only functions --mainly overloads -- in Scilab
language, making the module easy to update.<br>
This module is among the ATOMS Best-of noticeably because several
other popular modules require it as a dependency. Then iodelay is
automatically installed when its "parents" are installed.<br>
<br>
This means that when iodelay is not up-to-date, this blocks other
modules depending on it to work. This is currently the case : 10
months after the publication of Scilab 6.1.0, the current iodelay
version is only for Scilab 6.0.<br>
<br>
All these aspects make me thinking that iodelay should be part of
Scilab, to be included either in the CACSD or in the
signal_processing internal Scilab modules. Then no repackaging and
re-publication tasks of the module would be needed anymore for
each new Scilab 6.x version.<br>
</p>
The iodelay module is currently published under the Cecill license.
This looks compatible with the Scilab's license.<br>
To me this inclusion could be proposed in the next Scilab 6.1.1
release. There is no reason to wait more.<br>
<br>
Any comment is welcome about this proposal, noticeably from Serge,
the iodelay author.<br>
<br>
Thanks<br>
Samuel<br>
<br>
</body>
</html>