OSProcess and SqueakMap

> On Mon, Sep 07, 2009 at 12:15:28PM -0700, Ross Boylan wrote:
> > I want to run the magma tester, which is much easier if OS Process is
> > around.  It doesn't seem to be in the image or Monticello, and I think
> > it is only available from SqueakMap.
>
> OSProcess and CommandShell (formerly part of OSProcess until I split it)
> are both on SqueakSource. For Pharo, I recommend that you load the latest
> versions from SqueakSource rather than from SqueakMap (I made a fix just
> yesterday that is important for Pharo users). Be sure to get the unit tests
> also, they are a good source of examples.

>
> I have not tested on the latest Pharo, but I did notice one test failure
> for OSProcess the last time I checked. It was something involving coordinating
> lots of (Smalltalk) processes. One of the CommandShell tests was not running
> to completion either, probably for the same reason. I'm not sure if it is
> still a problem on the latest Pharo or not (sorry, I have not had time to
> track it down yet).
>
> Also, CommandShell will not show up in the menus on Pharo, so you will
> need to evaluate "CommandShell open" to start a shell.
>
> > What's the best way to get OSProcess into the image?  Is it already
> > there?  Not compatible?
>
> It should not be necessary to add it to the image.

> On Mon, 2009-09-07 at 16:00 -0400, David T. Lewis wrote:
> > On Mon, Sep 07, 2009 at 12:15:28PM -0700, Ross Boylan wrote:
> > > I want to run the magma tester, which is much easier if OS Process is
> > > around.  It doesn't seem to be in the image or Monticello, and I think
> > > it is only available from SqueakMap.
> >
> > OSProcess and CommandShell (formerly part of OSProcess until I split it)
> > are both on SqueakSource. For Pharo, I recommend that you load the latest
> > versions from SqueakSource rather than from SqueakMap (I made a fix just
> > yesterday that is important for Pharo users). Be sure to get the unit tests
> > also, they are a good source of examples.
> OSProcess loaded fine, but CommandShell says PluggableTextController and
> PluggableTextView.

I proceeded past the error above and another warning that MVC was not

> On Mon, 2009-09-07 at 19:12 -0400, David T. Lewis wrote:
> > On Mon, Sep 07, 2009 at 01:50:14PM -0700, Ross Boylan wrote:
> > > On Mon, 2009-09-07 at 16:00 -0400, David T. Lewis wrote:
> > > > On Mon, Sep 07, 2009 at 12:15:28PM -0700, Ross Boylan wrote:
> > > > > I want to run the magma tester, which is much easier if OS Process is
> > > > > around.  It doesn't seem to be in the image or Monticello, and I think
> > > > > it is only available from SqueakMap.
> > > >
> > > > OSProcess and CommandShell (formerly part of OSProcess until I split it)
> > > > are both on SqueakSource. For Pharo, I recommend that you load the latest
> > > > versions from SqueakSource rather than from SqueakMap (I made a fix just
> > > > yesterday that is important for Pharo users). Be sure to get the unit tests
> > > > also, they are a good source of examples.
> > > OSProcess loaded fine, but CommandShell says PluggableTextController and
> > > PluggableTextView.
> >
> > Those are the MVC classes for CommandShell (which works for both Morphic
> > and MVC). MVC has been removed from Pharo. Don't worry about these error
> > messages; the rest should load fine.
> I proceeded past the error above and another warning that MVC was not
> loaded.  I've attached details on it.  The save to file doesn't seem to
> have much info, so I also put in a screen shot.  The shot also show the
> progress bar at the very start.

> On Mon, Sep 07, 2009 at 12:15:28PM -0700, Ross Boylan wrote:
>> I want to run the magma tester, which is much easier if OS Process is
>> around.  It doesn't seem to be in the image or Monticello, and I  
>> think
>> it is only available from SqueakMap.
>
> OSProcess and CommandShell (formerly part of OSProcess until I split  
> it)
> are both on SqueakSource. For Pharo, I recommend that you load the  
> latest
> versions from SqueakSource rather than from SqueakMap (I made a fix  
> just
> yesterday that is important for Pharo users). Be sure to get the  
> unit tests
> also, they are a good source of examples.
>
> I have not tested on the latest Pharo, but I did notice one test  
> failure
> for OSProcess the last time I checked. It was something involving  
> coordinating
> lots of (Smalltalk) processes. One of the CommandShell tests was not  
> running
> to completion either, probably for the same reason. I'm not sure if  
> it is
> still a problem on the latest Pharo or not (sorry, I have not had  
> time to
> track it down yet).
>
> Also, CommandShell will not show up in the menus on Pharo, so you will
> need to evaluate "CommandShell open" to start a shell.
>
>> What's the best way to get OSProcess into the image?  Is it already
>> there?  Not compatible?
>
> It should not be necessary to add it to the image. I always intended  
> for
> OSProcess to be an external package, and it should be easy enough to  
> load
> for anyone who wants to use it.
>
> Dave
>
>
> _______________________________________________
> Pharo-project mailing list
> [hidden email]
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project