Re: [squeak-dev] Spoon 3 beta 2 released

> Smalltalk began as a part of a vision to provide extraordinary computing power
> to creative individuals. Although computer networks grew alongside it,
> Smalltalk was released into the world while its support for collaboration was
> still rudimentary. The system uses the concept of a virtual machine, including
> a model of the machine's memory, composed entirely of objects. Besides
> providing a very portable execution model, this scheme gives the system a
> powerful continuity: everything happens as the result of sending messages to
> objects. When it comes to sharing objects with other people, however, this
> continuity is violated.
>
>     Traditionally, to share code with another Smalltalk programmer, one writes
> source code to a file, and shares the file. One is no longer sending messages
> to objects, and the behavior being shared is reduced from live objects to a
> textual form which requires compilation to reanimate. When it is in that form,
> one cannot ask it to do things, as with objects. Worse, source code is
> ambiguous; the result of compilation depends on the environment in which it
> takes place. It's easy for the target compilation environment to be different
> from the original one in very subtle ways. Even referring to a class by name
> is risky; there is no way to be sure that the class with that name in the
> target compilation environment (if there even is one) is equivalent to the one
> in the original.
>
>     With the means of code-sharing being relatively unexpressive and
> inconvenient, Smalltalk object memories develop mostly in isolation, and
> quickly diverge from one another. And within each memory, support for
> describing the component behavior of different subsystems is weak. The result,
> after over thirty years of evolution, is that it is difficult even to describe
> what behavior one wants to transfer, before subjecting it to the inaccuracies
> of the transfer itself. Object memories have grown into large knots which are
> hard to untangle manually. Smalltalk's designers pursued a system that one
> person could understand and maintain. These problems hinder that pursuit, and
> make working in teams much harder than it could be. They make the experience
> of teaching and learning the system awkward, and this is one reason why the
> Smalltalk community is small.

> On 12-10-19 4:34 PM, Craig Latta wrote:
>> Hi all--
>>
>>       I've released Spoon 3 beta 2, see [1]. This is an important one,
>> because it's the first one that opens a remote browser onto a small
>> headless memory automatically. With this one it's pretty easy to browse
>> around.
>>
>>       So now there's a memory with development tools in it, and a small
>> memory which takes the place of the old changes file (by remembering
>> changes in an object database). Next, I¹ll set up a third memory, a
>> minimal environment which can the basis of a full Smalltalk distribution
>> (e.g., Squeak 5). I¹ll write instructions for creating unit tests for
>> each package in our communities, and imprinting the code run by those
>> tests into the minimal memory, thereby creating a module. We can work
>> toward releases where all the packages anyone might want to load are
>> served by some online history memory, with package metadata searchable
>> with Google[2].
>>
>>
>>       thanks!
>>
>> -C
>>
>> [1] http://tinyurl.com/9pw4gjc (wordpress.com)
>> [2] http://netjam.org/spoon/modules
>>
>> --
>> Craig Latta
>> www.netjam.org/resume
>> +31   6 2757 7177
>> + 1 415  287 3547 (no SMS)
>>
>>
> Well that's fun to explore. I'm on OSX 10.7.5 and for some reason the
> AppleScript could not see the image, but that was easy to fix by
> dragging the script into the same/Resources directory.
> The mini image starts and is broadcasting on 8090. It sets up a web page
> to present a link to start the development image. Nifty.
> For the first time HTTPServer is publicly available. It's in the mini
> image, which I can inspect from the open browser on the development
> image world.  Going to package New and then class Welcome and method
> 'act' I can see where the web page is coming from. Cool.
>
> Chris

> **
>
>
> Amigos cercanos y lejanos, les reenvio esto para que le den la bola que
> puedan
>
> Copio del Welcome
>
> > Smalltalk began as a part of a vision to provide extraordinary computing
> power
> > to creative individuals. Although computer networks grew alongside it,
> > Smalltalk was released into the world while its support for
> collaboration was
> > still rudimentary. The system uses the concept of a virtual machine,
> including
> > a model of the machine's memory, composed entirely of objects. Besides
> > providing a very portable execution model, this scheme gives the system a
> > powerful continuity: everything happens as the result of sending
> messages to
> > objects. When it comes to sharing objects with other people, however,
> this
> > continuity is violated.
> >
> > Traditionally, to share code with another Smalltalk programmer, one
> writes
> > source code to a file, and shares the file. One is no longer sending
> messages
> > to objects, and the behavior being shared is reduced from live objects
> to a
> > textual form which requires compilation to reanimate. When it is in that
> form,
> > one cannot ask it to do things, as with objects. Worse, source code is
> > ambiguous; the result of compilation depends on the environment in which
> it
> > takes place. It's easy for the target compilation environment to be
> different
> > from the original one in very subtle ways. Even referring to a class by
> name
> > is risky; there is no way to be sure that the class with that name in the
> > target compilation environment (if there even is one) is equivalent to
> the one
> > in the original.
> >
> > With the means of code-sharing being relatively unexpressive and
> > inconvenient, Smalltalk object memories develop mostly in isolation, and
> > quickly diverge from one another. And within each memory, support for
> > describing the component behavior of different subsystems is weak. The
> result,
> > after over thirty years of evolution, is that it is difficult even to
> describe
> > what behavior one wants to transfer, before subjecting it to the
> inaccuracies
> > of the transfer itself. Object memories have grown into large knots
> which are
> > hard to untangle manually. Smalltalk's designers pursued a system that
> one
> > person could understand and maintain. These problems hinder that
> pursuit, and
> > make working in teams much harder than it could be. They make the
> experience
> > of teaching and learning the system awkward, and this is one reason why
> the
> > Smalltalk community is small.
>
> On 10/19/12 11:37 PM, "Chris Cunnington" <[hidden email]>
> wrote:
>
> > On 12-10-19 4:34 PM, Craig Latta wrote:
> >> Hi all--
> >>
> >> I've released Spoon 3 beta 2, see [1]. This is an important one,
> >> because it's the first one that opens a remote browser onto a small
> >> headless memory automatically. With this one it's pretty easy to browse
> >> around.
> >>
> >> So now there's a memory with development tools in it, and a small
> >> memory which takes the place of the old changes file (by remembering
> >> changes in an object database). Next, I¹ll set up a third memory, a
> >> minimal environment which can the basis of a full Smalltalk distribution
> >> (e.g., Squeak 5). I¹ll write instructions for creating unit tests for
> >> each package in our communities, and imprinting the code run by those
> >> tests into the minimal memory, thereby creating a module. We can work
> >> toward releases where all the packages anyone might want to load are
> >> served by some online history memory, with package metadata searchable
> >> with Google[2].
> >>
> >>
> >> thanks!
> >>
> >> -C
> >>
> >> [1] http://tinyurl.com/9pw4gjc (wordpress.com)
> >> [2] http://netjam.org/spoon/modules
> >>
> >> --
> >> Craig Latta
> >> www.netjam.org/resume
> >> +31 6 2757 7177
> >> + 1 415 287 3547 (no SMS)
> >>
> >>
> > Well that's fun to explore. I'm on OSX 10.7.5 and for some reason the
> > AppleScript could not see the image, but that was easy to fix by
> > dragging the script into the same/Resources directory.
> > The mini image starts and is broadcasting on 8090. It sets up a web page
> > to present a link to start the development image. Nifty.
> > For the first time HTTPServer is publicly available. It's in the mini
> > image, which I can inspect from the open browser on the development
> > image world. Going to package New and then class Welcome and method
> > 'act' I can see where the web page is coming from. Cool.
> >
> > Chris
>
> I'm on OS X 10.6 now and also have troubles with AppleScript .
> Solved rename the app to "Spoon3b2"
> Starting to explore, send feedback ASAP.
>
> As you know , my wish is build a more compatible version of Reduced Cuis
> ( Cuis3.1r.4f of 2.5 Mb)
> http://squeakros.org/Cuis3dot2/Cuis3.1r.4f.image
> http://squeakros.org/Cuis3dot2/Cuis3.1r.4f.changes
>
> Runs on old and new VM
>
> Edgar
>
>  
>