OSProcess status

On Fri, Dec 13, 2013 at 09:35:47AM -0200, Germ?n Arduino wrote:
> Hi:
>
> I remember some old threads about OSProcess. It's ported for Cuis? Where?
>

Hi Germ?n,

I just tried loading OSProcess from some change sets that I exported
from Squeak. There are a number of issues to be sorted out, but overall
I was able to get it working.

I have a question about how to support a package in Cuis. I keep OSProcess
in a Monticello repository, and I would like to keep the development
sources all in one place. I also would like to support Cuis, and keep
Cuis fully up to date with any changes that I might make. What would
be a good way to do this? I would not mind going through some extra
steps to produce the Cuis version, but I'm not sure the best way to
do it.

Consider me a newbie here, as I have not yet tried out the Cuis development
process, so I may be asking a stupid question here.

Thanks,
Dave


_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org

Hi David:

Sorry by the delay but was a busy monday yesterday....

2013/12/16 David T. Lewis <[hidden email]>

Hi,

I have updated OSProcess with some fixes for Cuis. This is not complete,
but it provides a working version that passes most tests when running on
an interpreter VM (not Cog). I have been working with fileouts from Squeak

mmm, I'm having a crash trying to use Cuis 1880 with Squeak 4.1.1 VM

 

and I am not sure how to load an mcz file into Cuis, but if anyone would
like to try it, the updated version of OSProcess is here:

  http://www.squeaksource.com/OSProcess/OSProcess-dtl.87.mcz

I usually extract the sources.st from the .mcz, but don't worry I will do it and will prepare a .pck.st. Then you can create a GitHub account and a repo for OSProcess for Cuis.

 

Before loading this, there are some changes that I made to my Cuis image
first. Here is what I did:

- Create the class Model as subclass of Object. This can just an empty class,
but the classes OSProcessAccessor, AIOEventHandler, and PseudoAioEventHandler
are subclassed from Model in Squeak. Or, if you prefer not to have a stub
Model class, you can load OSProcess, then fix the class definitions for
OSProcessAccessor, AIOEventHandler, and PseudoAioEventHandler to be subclasses
of Object (otherwise they end up under ProtoObject, which does not work).

In Cuis we have ActiveModel, to bind models and UIs, an approach designed by Juan and inspired in Visual Smalltalk. May be we should use ActiveModel or you prefer Object?

 

- Implement these methods from Squeak:
    Object>>changed             (OSProcess uses changed / update mechanism throughout)
    Object>>ifNotNilDo:         (older versions of Squeak do not handle ifNotNil: the same)
    Character class>>cr         (compatibility, used in many places in OSProcess)
    Character class>>lf         (compatibility, used in many places in OSProcess)
    StandardFileStream>>fileID  (accessor needed by AttachableFileStream)

With those methods added, OSProcess can be loaded in Cuis, and most tests
will pass.

Character #cr and #lf are already in Cuis, the other modifications I will evaluate if are better to include in the Compatibility Layer or as part of the OSProcess package for Cuis (*osprocess categories).

 

There is no class Socket in Cuis, so tests for socket operations will fail,
and there will be some undeclared references to Socket.

Yes, Socket is part of the Network Kernel package, not loaded by default in the stock Cuis image.

 

The line ending conventions are different in Cuis and Squeak (cr versus lf)
so the code that I loaded looks ugly in the browser. I am not sure how to
fix this (probably I am just loading the files in the wrong way), but the
code works so I am not too worried about this right now.

Yes, the way is (previous to load the code, for example in the FileList):

1. Cmd-a Select all
2. Cmd-U Convert line endings to LF characters (Cuis convention) in selection

3. Cmd-s Save

and then load the code.

 

It's a start :)

Sure, I will do something as soon as have a bit of free time....as produce the .pck.st package to avoid you such task. And also the installation with prereq, to install OSProcess with only a command :)

 

Dave

Germán.

Hi Juan,

On Wed, Dec 18, 2013 at 12:45:03AM -0300, Juan Vuletich wrote:
>
> With the appropriate compatibility package and / or some tweaks to Cuis
> (I described them elsewhere in this thread), it looks like you could
> support Cuis with exactly the same code as Squeak.

Yes I agree.

>
> Given that extracting the code from a MCZ file is not hard, I could
> write a simple tool to allow converting an MCZ file to .pck.st format.
> This tool would also convert newline characters (cr, crlf, lf) to Cuis
> default: lf.

I think this tool would be useful, and it would make it easier to bring
existing packages into Cuis.

>
> This means that if your code specifically requires a cr or crlf string
> or character, instead of including them in a string literal, you would
> need to use #cr, #lf or #crLf. The good part is that your code would be
> line ending agnostic. BTW, to require a default line terminator, I'd
> suggest adding #newLineString to Squeak, answering the same as #cr (in
> Cuis it answers #lf).

Yes I agree, and it would be a good thing for me to make those changes.

>
> Would all this be ok for you? If so, all we need to do is to run this
> tool when you publish a new version of OSProcess.MCZ, and publish the
> result to the Cuis GitHub repo.

Yes this is ok, I like this approach.

I should mention also that running OSProcess in Cuis helps to find bugs
in OSProcess. For example, OSProcess class>>isUnix was broken, and I did
not notice the problem until I loaded it in Cuis. So this is is a good
thing.

Dave

_______________________________________________
Cuis mailing list
[hidden email]
http://jvuletich.org/mailman/listinfo/cuis_jvuletich.org