[Cuis-dev] Cuis Smalltalk Issues

Nicola Mingotti nmingotti at gmail.com
Sun Nov 14 02:45:39 PST 2021

Hi Mark,

I can answer only partially to your questions, graphics gurus will fill 
the gaps ;)

1. Cuis uses a special plugin for graphics and the new graphics part is 
under fast development so,
I would say, it is expected you find some bugs. Just tell it here.

2. About not losing you examples. The master way we have in Cuis is to 
use packages.
I prefer it over saving the image, probably because i am not a long time 
smalltalk programmer.

If you are new to packages my recent videos might be helpful:


On 11/13/21 23:17, Mark via Cuis-dev wrote:
> Hi,
> I’m new to the Cuis implementation of Smalltalk.
> I’ve dabbled with Squeak and Pharo in the past … and then life would 
> strike and distract me from it. :-)
> Now, I’m playing with Cuis — and I really like the minimalist approach.
>     System: MacBook Pro 16” (2019)
>     OS: macOS Catalina (10.15.7)
>     Cuis image: Cuis5.0-4963.image
> I’ve been working my way through “The Cuis” book 
> (https://cuis-smalltalk.github.io/TheCuisBook/), learning lots.
> It’s all been running quite stable until today and have run into two 
> issues.
> (I did DuckDuckGo around to find similar issues, but I didn’t find 
> any. If these are noted somewhere, please point me to them. Thanks! 🙂)
> ISSUE #1
> I got to the clock morph chapter 
> (https://cuis-smalltalk.github.io/TheCuisBook/A-Clock-Morph.html) and 
> got the clock running.
> Then, I started playing with the #stepTime values — just for fun. I 
> set it to values like “16” and “66.7” and then, suddenly, the whole 
> environment froze.
> The Squeak menu still responded, but it wouldn’t allow me to quit.
> I sent it a USR1 signal, and it generated a crash dump, here: 
> https://www.dropbox.com/s/1e4st9fp8xrm29p/crash-01.dmp?dl=0
> Is this a known issue? I realize a step time of 16ms (or possibly even 
> 67.7ms) is pretty short, but I didn’t expect it to freeze everything.
> (Sadly, I hadn’t saved the image, so I lost all the samples I’d added. 
> :-( )
> ISSUE #2
> After restarting Cuis, I re-added the LineExampleMorph (section 7.1.1 
> - https://cuis-smalltalk.github.io/TheCuisBook/Going-Vector.html)
> And instantiated it.
> It drew a green line.
> Then, I went to the class definition and changed its superclass from 
> Morph to MovableMorph and saved.
> Everything seems fine … but, when I clicked on the existing green 
> line, the debugger popped up
> So, I closed the debug window and went to the Workspace window and 
> executed “LineExampleMorph allInstancesDo: [:x | x delete. ]”
> The green line disappears, but a debug window popped up.
> So, I changed the class back to “Morph” … and then a “Recompiling” 
> dialog popped up … and stayed there.
> Then debug windows started popping all over — to the point where the 
> whole display is unusable.
> It looks like it may have generated a log file for each debug message 
> (there are 16 of them … 😉)
> Here’s a screen recording (.mov file) of what it looked 
> like:https://www.dropbox.com/s/ja6hynzfpka5jua/Cuis-Smalltalk-Issue02.mov?dl=0
> I guess my overall questions are:
> Should these kinds of things be happening?
> Or are these somehow n00b errors on my part?
> How can I ensure data is lost as I experiment with the environment?
> Since the whole philosophy of Smalltalk is to be able to examine the 
> whole system and try things, I’d like to do that without worrying that 
> the next thing I do could blow up the environment. 😉
> These don’t seem like things that should freeze the environment.
> Thanks, in advance, for any insights you might have.
> — Mark
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20211114/7982d3c6/attachment.htm>

More information about the Cuis-dev mailing list