Steve,
Your tutorial is great (as far as I’ve
gone: late section 2). I almost skipped straight to downloading the code and
reviewing it… and then I thought, no, I should walk through it and see
how Squeakers work. Anybody with some knowledge of using modern windowing
systems and basic smalltalk should be able to use it, even with different
menus.
I want to emphasize that these lock-ups I
keep encountering with Squeak on
Images tried – with the exception of
Croquet, the rest were 3.10 VMs.
Squeak3.10.2-7179 – the basic
release
Pharo0.1
Croquet SDK 1.0.18 (using its vm of
course)
Cassou’s images (sp?)
--
The fact that the console can be turned on
and off (while the rest of squeak appears ‘locked up’) and that it
displays data for us is suggests two things: 1) it is not stuck in an infinite
loop in the GC, and 2) basic threading/time-slicing is working. So, is the user
(world-menu) thread being lost? Can I protect it… or add another thread
that makes certain the core user thread is always up? … Who can point me
in the right direction? Perhaps I can add controls to the same place the VM
controls (available on the outer-most window-frame menu) are controlled from.
(Tell me where to look for that please.) There are likely several band-aid
approaches that will help make it usable, even if I can’t fix the core
problem.
Ryan Zerby writes:
> I'm
doing your tutorial now, with Squeak3.10.2-7179-basic. The only
issues I've had with it when I do something wrong, like an infinite
loop in the mouse handling routines... .BAM. 7 zillion debuggers.
On which platform? I too have encountered
the 7-zillion debuggers problem… just browsing. Or clicking terminate on
the debugger.
I would like help to make Squeak usable. Yesterday
I had an image lock up after less than one minute of uptime, and all I did was
launch
If I want to alter the root menus on
Squeak, where do I get started?
On which forum should I take up this
matter? Release?
Thanks folks,