<div dir="auto">Great, thanks a lot, also for intoLocation:do: !</div><div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Thu, Jun 25, 2026 at 22:00 Juan Vuletich <<a href="mailto:juan@cuis.st">juan@cuis.st</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hi Luciano,<br>
<br>
On 2026-06-25 5:16 AM, Luciano Notarfrancesco via Cuis-dev wrote:<br>
> Hi Juan,<br>
> Thanks for the detailed explanation of the rationale behind your <br>
> design. I was considering using TTF icons, but then I thought it <br>
> was going to be annoying to have to work with arbitrary code points <br>
> instead of the actual fonts, or would require a global mapping name -> <br>
> icon/codePoint that I also didn't like much, so I followed your <br>
> suggestion of doing this instead of TTF fonts and now I see it's much <br>
> cleaner and simpler.<br>
<br>
Most important to me, using TTF forces you to use text metrics <br>
arguments, when you're actually doing graphics and text metrics are <br>
maningless here.<br>
<br>
><br>
> I'm still not sure, but at this point I feel that we don't really need <br>
> the reified PathCommands (or perhaps they just belong to the SVG <br>
> package), I'd prefer to use literal Float32Arrays directly if we added <br>
> support for the rest of the commands.<br>
<br>
Yes. We need to add support for the rest of the commands. It is in my <br>
ToDo list now.<br>
<br>
> BTW, regarding #[], I'd like to suggest to change it to create <br>
> Float32Arrays instead of Float64Arrays... apparently all the current <br>
> use cases end up converting them to Float32Array anyway, and for that <br>
> they use two syntactic suggars: #[] and the backtick, it would be <br>
> simpler if #[] produced Float32Arrays instead...<br>
<br>
You're right. Just pushed 2 updates for that. We never actually needed <br>
literal Float64Arrays anyway.<br>
<br>
><br>
> Here's an example of an IconMorph, not necessarily the best <br>
> implementation but it shows the idea, you can test it like this:<br>
> IconMorph new pathData: <br>
> 'M240-200h120v-240h240v240h120v-360L480-740 240-560v360Zm-80 <br>
> 80v-480l320-240 320 240v480H520v-240h-80v240H160Zm320-350Z'<br>
<br>
Just pushed your IconMorph as an update. Included this as a class <br>
example method.<br>
<br>
Thanks!<br>
<br>
><br>
> Cheers,<br>
> Luciano<br>
<br>
-- <br>
Juan Vuletich<br>
<a href="http://www.cuis.st" rel="noreferrer" target="_blank">www.cuis.st</a><br>
<a href="http://github.com/jvuletich" rel="noreferrer" target="_blank">github.com/jvuletich</a><br>
<a href="http://researchgate.net/profile/Juan-Vuletich" rel="noreferrer" target="_blank">researchgate.net/profile/Juan-Vuletich</a><br>
<a href="http://independent.academia.edu/JuanVuletich" rel="noreferrer" target="_blank">independent.academia.edu/JuanVuletich</a><br>
<a href="http://patents.justia.com/inventor/juan-manuel-vuletich" rel="noreferrer" target="_blank">patents.justia.com/inventor/juan-manuel-vuletich</a><br>
<br>
</blockquote></div></div>