Folks -
I've built a new Windows VM for the upcoming release (mostly to fix the SqueakMap problem). Good thing I tried it first - it turns out that my earlier fix for SqueakMap had fixed one particular version of the problem, but there was another variant that it hadn't addressed (now it does). With this VM I can use SqueakMap successfully.
However, since this was a major version switch I've also changed two more issues that came up in the past:
1) The VM will now default to pass the window close event to the image instead of handling it directly. You can see that in a current trunk image by clicking on the close button (you'll now get a Squeak notifier instead of the previous VM notifier). The old behavior is still available if you SHIFT-Click on the close button. This is very useful if your image hangs.
2) The VM name now reflects the version. In other words, this VM is called Squeak4.0.1.exe to make it easier to distinguish between versions. Unfortunately this also means you'll heave to create a new association if you want to use this VM (hopefully, the installer will take care of that later).
As always the VM is available here:
http://squeakvm.org/win32/release/SqueakVM-Win32-4.0.1-bin.zip http://squeakvm.org/win32/release/SqueakVM-Win32-4.0.1-src.zip
Cheers, - Andreas
Wow, thanks a lot for getting SqueakMap going..!
On Sun, Mar 28, 2010 at 3:59 PM, Andreas Raab andreas.raab@gmx.de wrote:
Folks -
I've built a new Windows VM for the upcoming release (mostly to fix the SqueakMap problem). Good thing I tried it first - it turns out that my earlier fix for SqueakMap had fixed one particular version of the problem, but there was another variant that it hadn't addressed (now it does). With this VM I can use SqueakMap successfully.
However, since this was a major version switch I've also changed two more issues that came up in the past:
- The VM will now default to pass the window close event to the image
instead of handling it directly. You can see that in a current trunk image by clicking on the close button (you'll now get a Squeak notifier instead of the previous VM notifier). The old behavior is still available if you SHIFT-Click on the close button. This is very useful if your image hangs.
- The VM name now reflects the version. In other words, this VM is called
Squeak4.0.1.exe to make it easier to distinguish between versions. Unfortunately this also means you'll heave to create a new association if you want to use this VM (hopefully, the installer will take care of that later).
As always the VM is available here:
http://squeakvm.org/win32/release/SqueakVM-Win32-4.0.1-bin.zip http://squeakvm.org/win32/release/SqueakVM-Win32-4.0.1-src.zip
Cheers, - Andreas
On Sun, 2010-03-28 at 13:59 -0700, Andreas Raab wrote:
Folks -
I've built a new Windows VM for the upcoming release (mostly to fix the SqueakMap problem).
Any guess when a new Unix VM will be available for testing with 4.1?
With the current 3.11.3-2135 on FreeBSD 8.0 STABLE I get two errors on the command line:
$ squeak Squeak4.1-9863-alpha.image pulseaudio: not found + exec /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8 -encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 Squeak4.1-9863-alpha.image /usr/local/lib/squeak/3.11.3-2135/so.ImmX11Plugin: Undefined symbol "setNEncoding"
A ps -x shows pulseaudio running: 1403 ?? Is 0:00.16 /usr/local/bin/pulseaudio --start --log-target=syslog
Can't say how bad the setNEncoding error is.
(please remember to change the subject if you change the subject)
On 31.03.2010, at 09:59, Gary Dunn wrote:
On Sun, 2010-03-28 at 13:59 -0700, Andreas Raab wrote:
Folks -
I've built a new Windows VM for the upcoming release (mostly to fix the SqueakMap problem).
Any guess when a new Unix VM will be available for testing with 4.1?
With the current 3.11.3-2135 on FreeBSD 8.0 STABLE I get two errors on the command line:
$ squeak Squeak4.1-9863-alpha.image pulseaudio: not found
- exec /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8
-encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 Squeak4.1-9863-alpha.image /usr/local/lib/squeak/3.11.3-2135/so.ImmX11Plugin: Undefined symbol "setNEncoding"
A ps -x shows pulseaudio running: 1403 ?? Is 0:00.16/usr/local/bin/pulseaudio --start --log-target=syslog
Can't say how bad the setNEncoding error is.
So I guess these are just warnings, apart from them it works?
In the FreeBSD version of the "squeak" script, what is "useoss" set to?
And "pulseaudio --check 2>/dev/null" should actually be silent if not found, or does that work only in bash?
Besides, why can't it execute "pulseaudio" if it's in /usr/local/bin ?
- Bert -
On Wed, 2010-03-31 at 17:22 +0200, Bert Freudenberg wrote:
(please remember to change the subject if you change the subject)
On 31.03.2010, at 09:59, Gary Dunn wrote:
On Sun, 2010-03-28 at 13:59 -0700, Andreas Raab wrote:
Folks -
I've built a new Windows VM for the upcoming release (mostly to fix the SqueakMap problem).
Any guess when a new Unix VM will be available for testing with 4.1?
With the current 3.11.3-2135 on FreeBSD 8.0 STABLE I get two errors on the command line:
$ squeak Squeak4.1-9863-alpha.image pulseaudio: not found
- exec /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8
-encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 Squeak4.1-9863-alpha.image /usr/local/lib/squeak/3.11.3-2135/so.ImmX11Plugin: Undefined symbol "setNEncoding"
A ps -x shows pulseaudio running: 1403 ?? Is 0:00.16/usr/local/bin/pulseaudio --start --log-target=syslog
Can't say how bad the setNEncoding error is.
So I guess these are just warnings, apart from them it works?
In the FreeBSD version of the "squeak" script, what is "useoss" set to?
And "pulseaudio --check 2>/dev/null" should actually be silent if not found, or does that work only in bash?
Besides, why can't it execute "pulseaudio" if it's in /usr/local/bin ?
- Bert -
Progress, sort of. The pulseaudio test fails because the shell script has
PATH=/usr/bin:/bin
and FreeBSD has
$ which pulseaudio /usr/local/bin/pulseaudio
But fixing the path results in a core dump (stuff in CAPS are my debug echos)
$ squeak Squeak4.1-9863-alpha.image HAVE PULSEAUDIO HAVE PADSP MOVE ON + exec padsp /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8 -encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 -vm-sound-oss Squeak4.1-9863-alpha.image could not find module vm-sound-OSS Abort trap (core dumped)
And the lib folder contains
$ ls /usr/local/lib/squeak/3.11.3-2135 SqueakV39.sources so.PseudoTTYPlugin so.AioPlugin so.RomePlugin so.B3DAcceleratorPlugin so.Squeak3D so.ClipboardExtendedPlugin so.SqueakFFIPrims so.DBusPlugin so.UUIDPlugin so.FileCopyPlugin so.UnixOSProcessPlugin so.GStreamerPlugin so.XDisplayControlPlugin so.HostWindowPlugin so.vm-display-X11 so.ImmX11Plugin so.vm-display-custom so.KedamaPlugin so.vm-display-null so.KedamaPlugin2 so.vm-sound-NAS so.MIDIPlugin so.vm-sound-custom so.Mpeg3Plugin so.vm-sound-null so.OggPlugin squeakvm
My VM is from
and not the FreeBSD port.
I hope this is useful.
On 01.04.2010, at 13:44, Gary Dunn wrote:
On Wed, 2010-03-31 at 17:22 +0200, Bert Freudenberg wrote:
(please remember to change the subject if you change the subject)
On 31.03.2010, at 09:59, Gary Dunn wrote:
On Sun, 2010-03-28 at 13:59 -0700, Andreas Raab wrote:
Folks -
I've built a new Windows VM for the upcoming release (mostly to fix the SqueakMap problem).
Any guess when a new Unix VM will be available for testing with 4.1?
With the current 3.11.3-2135 on FreeBSD 8.0 STABLE I get two errors on the command line:
$ squeak Squeak4.1-9863-alpha.image pulseaudio: not found
- exec /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8
-encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 Squeak4.1-9863-alpha.image /usr/local/lib/squeak/3.11.3-2135/so.ImmX11Plugin: Undefined symbol "setNEncoding"
A ps -x shows pulseaudio running: 1403 ?? Is 0:00.16/usr/local/bin/pulseaudio --start --log-target=syslog
Can't say how bad the setNEncoding error is.
So I guess these are just warnings, apart from them it works?
In the FreeBSD version of the "squeak" script, what is "useoss" set to?
And "pulseaudio --check 2>/dev/null" should actually be silent if not found, or does that work only in bash?
Besides, why can't it execute "pulseaudio" if it's in /usr/local/bin ?
- Bert -
Progress, sort of. The pulseaudio test fails because the shell script has
PATH=/usr/bin:/bin
and FreeBSD has
$ which pulseaudio /usr/local/bin/pulseaudio
But fixing the path results in a core dump (stuff in CAPS are my debug echos)
$ squeak Squeak4.1-9863-alpha.image HAVE PULSEAUDIO HAVE PADSP MOVE ON
- exec padsp /usr/local/lib/squeak/3.11.3-2135/squeakvm -pathenc UTF-8
-encoding UTF-8 -plugins /usr/local/lib/squeak/3.11.3-2135 -vm-sound-oss Squeak4.1-9863-alpha.image could not find module vm-sound-OSS Abort trap (core dumped)
And the lib folder contains
$ ls /usr/local/lib/squeak/3.11.3-2135 SqueakV39.sources so.PseudoTTYPlugin so.AioPlugin so.RomePlugin so.B3DAcceleratorPlugin so.Squeak3D so.ClipboardExtendedPlugin so.SqueakFFIPrims so.DBusPlugin so.UUIDPlugin so.FileCopyPlugin so.UnixOSProcessPlugin so.GStreamerPlugin so.XDisplayControlPlugin so.HostWindowPlugin so.vm-display-X11 so.ImmX11Plugin so.vm-display-custom so.KedamaPlugin so.vm-display-null so.KedamaPlugin2 so.vm-sound-NAS so.MIDIPlugin so.vm-sound-custom so.Mpeg3Plugin so.vm-sound-null so.OggPlugin squeakvm
My VM is from
and not the FreeBSD port.
I hope this is useful.
Interesting. Where is vm-sound-OSS? And who is modifying the PATH?
I have no experience with running Linux binaries on BSD so I can't really help ...
- Bert -
On 28.03.2010, at 22:59, Andreas Raab wrote:
- The VM will now default to pass the window close event to the image instead of handling it directly. You can see that in a current trunk image by clicking on the close button (you'll now get a Squeak notifier instead of the previous VM notifier). The old behavior is still available if you SHIFT-Click on the close button. This is very useful if your image hangs.
John,
could you change the default for the Mac VM too? Both Linux and Windows VMs now deliver the window event rather than killing the image.
For Etoys we use
SqueakWindowAttribute <8200001f>
in the VM's Info.plist. That at least enables the red window close button (though "Quit" from the dock menu does not work).
- Bert -
For scratch on the macintosh I had added a SqueakQuitOnQuitAppleEvent info.plist entry (in current VM). So that if we see a quit application apple event which is the result of doing 'quit' via the dock, or shutdown, or logout. The we just blow the VM away.
This was acceptable for the scratch folks... Obviously a Squeak developer thinks he should get a chance to say yes/no save my image...
I could look into making it a close window type of event and see what happens if there is interest?
On 2010-04-06, at 3:35 AM, Bert Freudenberg wrote:
On 28.03.2010, at 22:59, Andreas Raab wrote:
- The VM will now default to pass the window close event to the image instead of handling it directly. You can see that in a current trunk image by clicking on the close button (you'll now get a Squeak notifier instead of the previous VM notifier). The old behavior is still available if you SHIFT-Click on the close button. This is very useful if your image hangs.
John,
could you change the default for the Mac VM too? Both Linux and Windows VMs now deliver the window event rather than killing the image.
For Etoys we use
SqueakWindowAttribute <8200001f>
in the VM's Info.plist. That at least enables the red window close button (though "Quit" from the dock menu does not work).
- Bert -
-- =========================================================================== John M. McIntosh johnmci@smalltalkconsulting.com Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
On 06.04.2010, at 19:35, John M McIntosh wrote:
For scratch on the macintosh I had added a SqueakQuitOnQuitAppleEvent info.plist entry (in current VM). So that if we see a quit application apple event which is the result of doing 'quit' via the dock, or shutdown, or logout. The we just blow the VM away.
This was acceptable for the scratch folks... Obviously a Squeak developer thinks he should get a chance to say yes/no save my image...
I could look into making it a close window type of event and see what happens if there is interest?
There is interest :)
I'd expect the "Quit" entry from the Dock or the menu bar to be equivalent to hitting the window close box.
For shutdown/logout I'd want a different event, if possible. A window-close event would be okay, too, but at least on the XO I need to respond to the "session logic" too. Or no, strike that, actually it would be fine to deliver a window-close request.
Thanks :)
- Bert -
On 2010-04-06, at 3:35 AM, Bert Freudenberg wrote:
On 28.03.2010, at 22:59, Andreas Raab wrote:
- The VM will now default to pass the window close event to the image instead of handling it directly. You can see that in a current trunk image by clicking on the close button (you'll now get a Squeak notifier instead of the previous VM notifier). The old behavior is still available if you SHIFT-Click on the close button. This is very useful if your image hangs.
John,
could you change the default for the Mac VM too? Both Linux and Windows VMs now deliver the window event rather than killing the image.
For Etoys we use
SqueakWindowAttribute <8200001f>
in the VM's Info.plist. That at least enables the red window close button (though "Quit" from the dock menu does not work).
- Bert -
--
John M. McIntosh johnmci@smalltalkconsulting.com Twitter: squeaker68882 Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com ===========================================================================
vm-dev@lists.squeakfoundation.org
-
Andreas Raab -
Bert Freudenberg -
Chris Muller -
Gary Dunn -
John M McIntosh