Hi, (crosspost vm-dev, squeak-dev, pharo-dev)
with more and more Metacello configurations for various well known Squeak and Pharo packages appearing in the metacello repository [1] I thought it would be a good idea to have one for VMMaker. It is based on a description by David (see [2]) and maybe he is able to help me keeping it maintained.
Since Metacello is Smalltalk independent and therefore able to handle differences between the deployment systems the new 'ConfigurationOfVMMaker' includes two platform spec's - one for #pharo and one #squeak. (Pharo has FreeType preinstalled, and Squeak not).
Unfortunately the Balloon3D stuff needs a little bit more cleaning (underscores, assigns to block args). Maybe Andreas is able to fix this. Until then one has to switch a preference in Pharo.
However: it should be easy now to load and use VMMaker in both:
In Squeak 3.11 #9236 ====================
Installer ss project: 'MetacelloRepository'; install: 'ConfigurationOfVMMaker'.
((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.0') load
In Pharo (core or dev) evaluate: ================================
Preferences setPreference: #allowBlockArgumentAssignment toValue: true.
Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfVMMaker'; load.
((Smalltalk at: #ConfigurationOfVMMaker) project version: '1.0') load
Feel free to have a look or use it to build shiny new VM's for the next interesting devices. For more infos on Metacello see [3] and [4].
Bye T.
------------------------------------------------------------------------------------
[1] http://squeaksource.com/MetacelloRepository.html [2] http://n4.nabble.com/Package-name-SharedPool-Speech-SharedPool-FFI-etc-td129... [3] http://code.google.com/p/metacello/ [4] http://gemstonesoup.wordpress.com/2010/01/25/metacello-1-0-beta22-launches/
On Fri, Feb 05, 2010 at 04:55:34PM +0100, Torsten Bergmann wrote:
Hi, (crosspost vm-dev, squeak-dev, pharo-dev)
with more and more Metacello configurations for various well known Squeak and Pharo packages appearing in the metacello repository [1] I thought it would be a good idea to have one for VMMaker. It is based on a description by David (see [2]) and maybe he is able to help me keeping it maintained.
Since Metacello is Smalltalk independent and therefore able to handle differences between the deployment systems the new 'ConfigurationOfVMMaker' includes two platform spec's - one for #pharo and one #squeak. (Pharo has FreeType preinstalled, and Squeak not).
Wonderful! Thank you so much for doing this.
I guess this means it's time for me to learn how to use Metacello ;-)
Dave
Hi David -
Let's be a bit careful before jumping heads-on into the Metacello frenzy. I don't mind if people choose to use Metacello to load VMMaker but it shouldn't be the only option. Myself for example, I use customarily a variety of images, none of which support or are supported by Metacello. It would not be good if we require Metacello to load VMMaker.
Cheers, - Andreas
David T. Lewis wrote:
On Fri, Feb 05, 2010 at 04:55:34PM +0100, Torsten Bergmann wrote:
Hi, (crosspost vm-dev, squeak-dev, pharo-dev)
with more and more Metacello configurations for various well known Squeak and Pharo packages appearing in the metacello repository [1] I thought it would be a good idea to have one for VMMaker. It is based on a description by David (see [2]) and maybe he is able to help me keeping it maintained.
Since Metacello is Smalltalk independent and therefore able to handle differences between the deployment systems the new 'ConfigurationOfVMMaker' includes two platform spec's - one for #pharo and one #squeak. (Pharo has FreeType preinstalled, and Squeak not).
Wonderful! Thank you so much for doing this.
I guess this means it's time for me to learn how to use Metacello ;-)
Dave
On Fri, Feb 05, 2010 at 09:57:30AM -0800, Andreas Raab wrote:
Hi David -
Let's be a bit careful before jumping heads-on into the Metacello frenzy. I don't mind if people choose to use Metacello to load VMMaker but it shouldn't be the only option. Myself for example, I use customarily a variety of images, none of which support or are supported by Metacello. It would not be good if we require Metacello to load VMMaker.
I understand and fully agree.
Personally I use a 3.8 image for most VMMaker work for exactly this reason. If it works in Squeak 3.8 it usually works everywhere, modulo a few annoyances like SmalltalkImage current, and with the recently noted exception of Scratch ;)
I'm also happy to see the Metacello support, because it will make VMMaker more accessible from images that do use Metacello.
Dave
vm-dev@lists.squeakfoundation.org