<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hi Folks,</p>
<p>I'm sorry for being late to the party!</p>
<p>(inline)</p>
<div class="moz-cite-prefix">On 2025-11-08 4:14 PM, Luciano
Notarfrancesco via Cuis-dev wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAL5GDyptBAc5GixWzqpE7ygPvq1VCdMfc8H9coxf6AO0H4bCRw@mail.gmail.com">
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<div dir="auto">Yes Ken, that’s probably the reason, things that
we implement as morphs tend to have a clear notion of
“position”. Graph edges connecting two vertices and wires
connecting two morphs, which are actually kind of the same idea,
is the only example I’ve seen AFAIR where there’s no natural
position, because they are just line segments between two
morphs, they depend on the positions of these two morphs instead
of having their own position.</div>
</blockquote>
<p>When I designed the hierarchy, it seemed to make sense to have
morphs without their own location, that just live in the owner's
space and coordinate system. The example I thought about was a
function like sin(x). It doesn't make sense for it to do anything
but one cycle in [1..2*pi] with values in [-1..1].</p>
<p>I think your example is way more useful though.</p>
<blockquote type="cite"
cite="mid:CAL5GDyptBAc5GixWzqpE7ygPvq1VCdMfc8H9coxf6AO0H4bCRw@mail.gmail.com">
<div dir="auto"><br>
</div>
<div dir="auto">I’ve solved the issue tho, I got it working. The
drag & drop (for connecting wires) was also kind if
confusing and took me a couple of hours, until I found all the
messages that I needed to implement in order to make it work
(although I did this before, I guess forgot the details, and
morphic changed too)… but it’s finally working, and looks
fantastic with antialiased vector graphics :)</div>
</blockquote>
<p>Would you consider making these into a package of their own? It
is not only useful, but also a good example of Morphic
programming.</p>
<p>Thanks!</p>
<blockquote type="cite"
cite="mid:CAL5GDyptBAc5GixWzqpE7ygPvq1VCdMfc8H9coxf6AO0H4bCRw@mail.gmail.com">
<div><br>
<div class="gmail_quote gmail_quote_container">
<div dir="ltr" class="gmail_attr">On Sat, Nov 8, 2025 at 23:28
<<a href="mailto:ken.dickey@whidbey.com"
moz-do-not-send="true" class="moz-txt-link-freetext">ken.dickey@whidbey.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"
style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-style:solid;padding-left:1ex;border-left-color:rgb(204,204,204)">On
2025-11-08 04:04, Luciano Notarfrancesco via Cuis-dev wrote:<br>
<br>
> BTW, a few years ago, for drawing graphs I made
GraphEdgeMorph subclass <br>
> of Morph, and it works but no one seems to do that (the
only subclass <br>
> of Morph in the base image is PlacedMorph), is there a
reason for this? <br>
> Does anyone here have subclasses of Morph in their
projects?<br>
<br>
I think that most people want Morph location.<br>
<br>
Interesting to look at package use:<br>
<br>
Cuis-Smalltalk[==> grep -s "Morph subclass:" */*.<a
href="http://pck.st" rel="noreferrer" target="_blank"
moz-do-not-send="true">pck.st</a> */*/*.<a
href="http://pck.st" rel="noreferrer" target="_blank"
moz-do-not-send="true">pck.st</a> <br>
*/*/*/*.<a href="http://pck.st" rel="noreferrer"
target="_blank" moz-do-not-send="true">pck.st</a><br>
<br>
HTH,<br>
-KenD<br>
</blockquote>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
</blockquote>
<pre class="moz-signature" cols="72">--
Juan Vuletich
<a class="moz-txt-link-abbreviated" href="http://www.cuis.st">www.cuis.st</a>
github.com/jvuletich
researchgate.net/profile/Juan-Vuletich
independent.academia.edu/JuanVuletich
patents.justia.com/inventor/juan-manuel-vuletich</pre>
</body>
</html>