Marcus Denker wrote:
On Mar 20, 2010, at 12:39 AM, Mariano Martinez Peck wrote:
Hi Lawson. Nebraska was removed intentionally from Pharo. Basically, because we want a clean, tested and working core.
ANY package that we don't consider core, should be removed and loadable. I
mean, if you want to use Nebraska, perfect, no problem. But you should load it
by yourself from squeaksource or whatever. In the core (actually, we still
trying) we put ONLY core code. In the PharoDev we put mostly Core + Dev tools
or examples.
We don't believe Nebraska should be neither in PharoDev in my opinion. Of
course, if people think the opposite, we can include it.
Regardless the above said, I am not sure Nebraska is working on Pharo. I invite
you to try to load it, ask for help, and tell us the results. Then you can
create a Metacello configuration for it and make it easy to manage and install.
So of course this idea of "just load it" is very difficult (impossible) to
realize if the software in question was just hacked and put code everywere in the base
system....
I think after Nebraska was removed, we cleaned up the rendering of handmorph,
for example. Nebraska complicates a far too complex Morphic system a bit.
In general, nebraska is one of the examples (others are eToys and Genie), that
where *very cool experiments*, but where the last important step was never done:
to learn from them and than build abstractions in the base system to make these
things implementable in a nice way.
I know that it's sad. And some people I am sure will think this is the wrong
way to go. But we felt that cutting out complexity especially regarding things
that are
not used is important if we want to move forward.
Darn. I was hoping I was getting my plug and play P2P networking on
Second Life-ST-based collaboration stuff for free.
The "Cobalt on a Prim" plugin should work pretty well, but its only
going to be an oddity. Far more interesting will be to allow
Nebraska-like/Cobalt-like sharing of applications without the extra
overhead of VNC. My original plan was to somehow extract the
TeaTime/Cobalt Island functionality and make it the networking layer
between two instances of the Squeak-SL Plugin:
Second Life <=> Squeak <=> Cobalt island (sans avatars and such) <=>
Cobalt island <=> Squeak <=> Second Life
Replacing "Cobalt" with "Nebraska" looked like a much simpler way to go
(on paper) but obviously, it won't work with Pharo. Eventually, Cobalt
will be remerged with Trunk so that it can work with the latest Squeak
or Pharo. I guess I can fudge something for P2P that isn't quite so
elegant in the meantime.
OTOH, maybe Nebraska can be implemented on top of TeaTime/Cobalt once
its available in Pharo.
Lawson
_______________________________________________
Pharo-project mailing list
[email protected]
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
