Problems with OSProcess/VMMaker/Balloon3D

David T. Lewis lewis at mail.msen.com
Wed Jun 11 01:50:56 UTC 2003


On Tue, Jun 10, 2003 at 02:28:00PM -0700, Tim Rowledge wrote:
> 
> Ah, I guess this means it really is time to put the OSProcess_Plugin_
> class either in it's own package (which can be linked to VMMaker) or
> actually in the VMMaker package - your choice. Then the OSProcess
> accessing classes and methods can be loaded on their own.

I guess it's easiest to just put it in its own package. That way I can
just issue updates every once in while without coordinating with anybody.

I'm expecting that in general, the plugins are going to be maintained
independently by their respective maintainers, and that we can think
of them as the source code for various chunks of functionality that
can be plugged into a VM. They are similar to the kernel modules in
a Linux OS, except that they are written in Smalltalk (Slang) rather
than C, and they plug in to the Squeak VM rather than to the Linux
kernel.

> And of course it's time I tried to make an OSProcess for RiscOS.

Well, I would have been too polite to have mentioned it, but since
you bring it up, there must be substantial pent up demand by now...

Dave



More information about the Squeak-dev mailing list