Daniel Vainsencher <danielv at netvision.net.il> wrote:
> I have to try Nebraska some time, though it sounds like it has all the
> disadvantages of sitting together (one machine, sometimes hard to follow
> things as they are being done) and of being apart (cant talk, can't tell
> if partner is looking). The JabbingBrowser would be less highly coupled
> - more like exchanging code by email, only with short turn around,
> online chat, and structured data creating endless potential for tool
> support.
> 


While it's one machine, you do each get a mouse pointer.  And you can
both type in different terminals.

You cannot both develop code due to some silliness in SystemWindow. 
Maybe you can do it in MorphicWrappers.  But anyway, fixing SystemWindow
to accept keystrokes even when not "active" would be simple.

Also, you can talk, via either a telephone or through textual chat as
you choose.

Finally, it would be pretty simple to adjust Nebraska so that the shared
world is large, just like in the original Kansas, so that multiple
developers can work in different parts of the screen.  I always meant
Nebraska to be a starting point, but everyone seems to be afraid to do
anything with it.  There is some decent (IMHO) documentation on the
Swiki for anyone who wants to do a project with it.


Lex