Well, the tools available are still relatively primitive, but bugs
aside, the current version of Spoon has the capability of creating and
editing methods in a "remote" spoon image using a class browser living
in the main image which looks and behaves exactly like a normal
Pharo/Squeak image except that it has support for Spoon and all the
saving is done on the remote image. In principle, that remote image
could live in your local computer or anywhere on the internet.
The kind of use-cases that Craig and I have discussed include things
like taking a Pharo-compatible Spoon image and "imprinting" (importing
live versions of) the classes and objects from a Squeak-compatible Spoon
image onto the Pharo image so that two programmers running Squeak and
Pharo on their machines can collaborate on editing a specific running
application in their own favorite environment.
The tools and capabilities for this already exist, although there are no
doubt still bugs to be squashed.
A more sophisticated use-case would be to create a remote Spoon image
running somewhere in the cloud that two or more programmers could
manipulate at the same time. This is also doable using the current
Spoon image and tools, but the traditional database issues concerning
simultaneous access to the same resource apply and I don't think solving
them in the Spoon Class Browser is a top priority for Craig right now.
L
On 2/4/13 12:41 AM, Igor Stasenko wrote:
On 4 February 2013 01:23, Lawson English <lengli...@cox.net> wrote:
dare I mention Craig Latta's Spoon project which explicitly is meant to
solve this issue?
in what way?
being able to exchange data between two images ~~ being able to deal with
two different versions of same class properly. Think about proper
support for development tools.
For example, look at traits: they are integrated since 2007? (i think)
, but some tools
still have problems with them.
L
--
Squeak from the very start (introduction to Squeak and Pharo Smalltalk for the
(almost) complete and compleate beginner).
https://www.youtube.com/playlist?list=PL6601A198DF14788D&feature=view_all
"Debugging is twice as hard as writing the code in the first place. Therefore, if
you write the code as cleverly as possible, you are, by definition, not smart enough to
debug it." - Brian Kernighan
