<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">I think cutaxes() will be a great
extension of capabilities in Scilab.</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">/Claus<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 09-04-2021 17:19, Samuel Gougeon
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:1f72c89a-5e55-6084-f26c-cf14337e3131@free.fr">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div class="moz-cite-prefix">Hello,<br>
<br>
Le 02/04/2021 à 17:15, Samuel Gougeon a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:1f6ad60f-749f-1149-bab7-68cc8878dd6b@free.fr">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">Dear all,</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Thanks for your first feedbacks. I
am somewhat answering in the body of this message:<br>
</div>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">Le 02/04/2021 à 14:49, Antoine
Monmayrant a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:fa4bc10f-0d23-dc91-ed1c-0a794dfa34ab@laas.fr">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<div class="moz-cite-prefix">On 02/04/2021 12:16, CRETE Denis
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:125f7946caff40648d8ad2e734a91d82@thalesgroup.com">
<meta http-equiv="Content-Type" content="text/html;
charset=UTF-8">
<meta name="Generator" content="Microsoft Word 15 (filtered
medium)">
<style>@font-face
{font-family:Wingdings;
panose-1:5 0 0 0 0 0 0 0 0 0;}@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}p
{mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:12.0pt;
font-family:"Times New Roman",serif;}p.MsoListParagraph, li.MsoListParagraph, div.MsoListParagraph
{mso-style-priority:34;
margin-top:0cm;
margin-right:0cm;
margin-bottom:0cm;
margin-left:36.0pt;
margin-bottom:.0001pt;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}p.msonormal0, li.msonormal0, div.msonormal0
{mso-style-name:msonormal;
mso-style-priority:99;
mso-margin-top-alt:auto;
margin-right:0cm;
mso-margin-bottom-alt:auto;
margin-left:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;}span.EmailStyle20
{mso-style-type:personal;
font-family:"Calibri",sans-serif;
color:windowtext;}span.EmailStyle21
{mso-style-type:personal-reply;
font-family:"Calibri",sans-serif;
color:#1F497D;}.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}div.WordSection1
{page:WordSection1;}ol
{margin-bottom:0cm;}ul
{margin-bottom:0cm;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US">Hello,
<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US"
lang="EN-US"><o:p> </o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US"
lang="EN-US">I am also in favour of including this
function in Scilab, with an “improved” name. However,
as far as I know, an inset has very frequently its own
pair of axes, as opposed to a ticks-switching in (only
one of) the axes. Thus, I would not recommend a name
with “inset” and reserve it for a function more
closely implementing an inset.<o:p></o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US"
lang="EN-US">Zoom is quite appealing. <o:p></o:p></span></p>
<p class="MsoNormal"><span
style="color:#1F497D;mso-fareast-language:EN-US"
lang="EN-US">I was wondering about
“non-linear”_something…</span></p>
</div>
</blockquote>
<p>Hello Denis,</p>
<p>I'm with you here: this should be included, but the name is
not well matching the features of the function.<br>
Indeed, 'inset' is not at all what 'plot_plot' is offering.<br>
I was also thinking about "non-linear-axis" or something
like that, but I am not sure such a name will improve
discoverability of the function.<br>
But you are right: this is about having non-regular or
non-linear axis.</p>
<p>nonlinear-plot ? non-regular-plot ? All this is not
convincing for me...<br>
</p>
</blockquote>
<p>You know, i thought very hard about the plotplots() naming
before finding and choosing this one and first publishing it
;-))<br>
</p>
<p>Indeed, plotplots() is not at all about insets, although an
actually zooming inset plotting separate function could also
be useful (with the zooming box and possibly rays linking it
to the inset).<br>
</p>
<p>plotplots() is <b>not</b> about zooming or non-linear axis
either: it can be used with different and only linear scales,
without mixing log and lin ones.<br>
So why "plotplots"? Typing "plot" in <i>Google Translate</i>
(from english to french), i've got and we still get:</p>
<p><Google's screenshot><br>
</p>
<p>So <b>"plots" is very frequently used with the meanings
"parcels, pieces, patches, particles, shreds"</b>.<br>
To me, this is just the right one, close to what the function
actually addresses: plotting several parcels/pieces/patches of
some given graphics.<br>
This led me to this compact -- and i think talkative and
meaningful -- plotplots() name, that's not (only) a word game.<br>
<br>
Other names i thought about were with "multiscaled", or thinks
like "plot_multiscale". But to me, this could lead to some
confusion with multiple axes covering the same whole graphic,
as documented @ <a class="moz-txt-link-freetext"
href="https://help.scilab.org/docs/6.1.0/en_US/plot_multiscaled.html"
moz-do-not-send="true">https://help.scilab.org/docs/6.1.0/en_US/plot_multiscaled.html</a>.<br>
</p>
<p>That's (almost) the whole story about this plotplots() name.<br>
Is it more meaningful to you?<br>
</p>
</blockquote>
<p><br>
Apparently, the current plotplots() name used for 3 years is not
so bad. I agree with Denis in private mail that it could be a
bit more specific. Here are some other name suggestions:<br>
</p>
<p>cutaxes<br>
plotcutaxes<br>
plotslicedaxes<br>
slicedaxes<br>
slice_axes<br>
sliceaxes<br>
plotfractional<br>
<br>
cutaxes() would have my own preferences:</p>
<ul>
<li> the "plot" prefix is not really required, as "axes" already
clearly refers to graphics. Moreover, plotplots() works as
well on an already plotted axes, to somewhat post-process it
by cutting and presenting it in another way. Actually, that's
the main job of the function, even when data to plot are
provided instead of an already plotted axes.<br>
<br>
</li>
<li>it's short, and it clearly tells what it does and the result</li>
</ul>
<br>
<p>By the way, "cutaxes" almost means "cute axes" (with a french
accent :-) <br>
</p>
After including the function in Scilab, the current plotplots as
external ATOMS module will no longer be maintained. If plotplots()
is renamed into cutaxes(), current plotplots() users will have to
rename it in their existing codes. This should not be a big deal,
since a find/replace will be able to detect occurrences and
replace them.<br>
<br>
Final comments, suggestions and other feedbacks are still welcome!<br>
<p>Samuel<br>
<br>
</p>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:users@lists.scilab.org">users@lists.scilab.org</a>
<a class="moz-txt-link-freetext" href="http://lists.scilab.org/mailman/listinfo/users">http://lists.scilab.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<p><br>
</p>
</body>
</html>