<div><div dir="auto">so i am not a developer i guess so i guess that means i can be ignored</div><div dir="auto"> if i understand the way this works correctly</div><div dir="auto">but this is an announcement so i take a chance at annoying devs</div><div dir="auto"> respectfully </div><div dir="auto">i may be clueless about these things</div><div dir="auto"> totally to boot royally </div><div dir="auto"> so i have to assk maybe to find out more about these rules of morality</div><div dir="auto"> if anyone happens to step into this pile of plurality by accidental duality</div><div dir="auto"> hopefully it’s not too smelly nor needs no scraping off of the foot ok enough</div><div dir="auto"><br></div><div dir="auto">So how do i connect from MoosePharo to Squeak to make use of this Actors for Squeak?</div><div dir="auto">I have an Actors for Pharo Package loaded into Moose. Any overlap?</div><div dir="auto"><br></div><div dir="auto"><div dir="auto">I am interested in connecting different languages or images together</div><div dir="auto"> anything spring to mind? it seems like there are a lot of ways to do this</div></div><div dir="auto"> Are there any Packages that spring to mind? </div><div dir="auto">Oh i guess Actors for Squeak doesn’t do multi images. But maybe Raven can help.</div><div dir="auto">The idea seems to be to show Actors interacting graphically.</div><div dir="auto">Could this be used to show ErLang Actors interacting graphically?</div><div dir="auto">Is this something ErLangers would want? or do they already have something</div><div dir="auto"> And if so then how to connect ErLang to Squeak</div><div dir="auto">if there was is or i made a patchwork of interlingua connectors then</div><div dir="auto"> having a graphical way of looking at it seems like a good thing</div><div dir="auto"><br></div><div dir="auto">( i am using Moose because when i try to load Roassal into Pharo it fails ( i think i tried twice once recently ) also i like the Moose thing although i don’t seem to be able to really make it work for me and i guess it’s big )</div></div><div><div dir="auto"><br></div><div><br><div class="gmail_quote"><div>On Mon, Feb 19, 2018 at 07:23 Tony Garnock-Jones <<a href="mailto:tonyg@leastfixedpoint.com" target="_blank">tonyg@leastfixedpoint.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi all,<br>
<br>
About a year ago I accidentally a small Erlang-style Actors<br>
implementation for Squeak, based on subclassing Process, using Message<br>
for, er, messages, and using Promise for RPC.<br>
<br>
It draws on my experience of Erlang programming in a few ways: it has<br>
links and monitors for between-actor failure signalling; it has library<br>
actors representing sockets; it has a simple tracing facility. There's<br>
crude and no doubt heavily problematic support for basic Morphic<br>
interaction.<br>
<br>
Over the past couple of weeks I've been dusting it off, fleshing it out,<br>
and documenting it. (Hence some of the stuff I've been trying out wrt<br>
Promises.)<br>
<br>
It's available at <a href="http://squeaksource.com/Actors.html" rel="noreferrer" target="_blank">http://squeaksource.com/Actors.html</a>.<br>
<br>
Installation instructions, documentation and tutorials can be found at<br>
<br>
<a href="https://tonyg.github.io/squeak-actors/" rel="noreferrer" target="_blank">https://tonyg.github.io/squeak-actors/</a><br>
<br>
(I spent rather too much time writing documentation.)<br>
<br>
It's by no means as ambitious as Squeak-E or Henry's Raven - it only<br>
deals with single-image in-image messaging between actors, and doesn't<br>
have the E-style ability to refer to objects within a vat. Instead it<br>
follows Erlang in having references denote actors (i.e. vats, roughly),<br>
rather than anything more fine-grained.<br>
<br>
Next steps could be:<br>
<br>
- a Workspace that was actor aware, i.e. each Workspace an actor.<br>
- better Supervisors.<br>
- tools for visualizing the current constellation of actors,<br>
perhaps based on Ned Konz's Connectors?<br>
- an ActorEventTrace subclass that is able to draw message interaction<br>
diagrams as a Morph.<br>
- a screencast of building an IRC client maybe?<br>
<br>
Cheers,<br>
Tony<br>
<br>
PS. I did try to port it to Pharo. The first obstacle was lack of class<br>
Promise - fairly easily overcome. The second, worse obstacle was weird<br>
failures and incompatibilities in Socket support. I gave up at that point.<br>
<br>
PPS. I'd love to see it running on Cuis.<br>
<br>
</blockquote></div></div></div>