I just tried out Nebraska (I think it might be the very first time) and noticed a) for some reason the default port used is set to (9091 to: 9099) and that breaks the prim. If I fudge it to just us port 9091 I can get both server and client to work b) it looks like the event x/y values passed are not offset to match any offset of the client morph. If you have the client in the default top-left location all is well.
Has anyone been actually using Nebraska? Is it sometihng to keep alive?
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Useful Latin Phrases:- Sic faciunt omnes. = Everyone is doing it.
Hi Tim,
thanks for your note! I had tried to get Nebraska to work a few years ago but was not not successful, as it turns out due to the port bug you reported. After fixing the port it finally works for me!
I have uploaded a few patches for Nebraska to the inbox that fix your mentioned issues plus two other ones. Note that dropping a morph into the terminal does not work for me because the peer-to-peer connection is always refused. Looking forward to your feedback! :-)
Happy holidays, Christoph
--- Sent from Squeak Inbox Talk
On 2023-11-30T17:35:10-08:00, tim@rowledge.org wrote:
I just tried out Nebraska (I think it might be the very first time) and noticed a) for some reason the default port used is set to (9091 to: 9099) and that breaks the prim. If I fudge it to just us port 9091 I can get both server and client to work b) it looks like the event x/y values passed are not offset to match any offset of the client morph. If you have the client in the default top-left location all is well.
Has anyone been actually using Nebraska? Is it sometihng to keep alive?
tim
tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Useful Latin Phrases:- Sic faciunt omnes. = Everyone is doing it.
Christoph,
This is great! Thank you
Dave
On 2023-12-26 17:29, christoph.thiede@student.hpi.uni-potsdam.de wrote:
Hi Tim,
thanks for your note! I had tried to get Nebraska to work a few years ago but was not not successful, as it turns out due to the port bug you reported. After fixing the port it finally works for me!
I have uploaded a few patches for Nebraska to the inbox that fix your mentioned issues plus two other ones. Note that dropping a morph into the terminal does not work for me because the peer-to-peer connection is always refused. Looking forward to your feedback! :-)
Happy holidays, Christoph
_Sent from __Squeak Inbox Talk [1]_
On 2023-11-30T17:35:10-08:00, tim@rowledge.org wrote:
I just tried out Nebraska (I think it might be the very first time) and noticed a) for some reason the default port used is set to (9091 to: 9099) and that breaks the prim. If I fudge it to just us port 9091 I can get both server and client to work b) it looks like the event x/y values passed are not offset to match any offset of the client morph. If you have the client in the default top-left location all is well.
Has anyone been actually using Nebraska? Is it sometihng to keep alive?
tim
tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Useful Latin Phrases:- Sic faciunt omnes. = Everyone is doing it.
Links: ------ [1] https://github.com/hpi-swa-lab/squeak-inbox-talk
Nicely done; thanks.
The reason I tested it out, aside from simple curiosity, is that I really want to find a way to get the effect of a VNC connection within seaside for debugging purposes.
It just seems nuts that we have a socket connecting a web browser to the seaside website and can't use it to get access to the squeak UI when there are problems. Yes, people have made sorta-kinda workarounds that provide a way to start up a VNC server on a chosen socket, but that still leaves having to do assorted ssh magic to tunnel the vnc socket. Boring!
tim -- tim Rowledge; tim@rowledge.org; http://www.rowledge.org/tim Useful random insult:- Always responds to "Make Money Fast" postings on the Net.
On 2023-12-26T12:57:28-08:00, tim@rowledge.org wrote:
Nicely done; thanks.
The reason I tested it out, aside from simple curiosity, is that I really want to find a way to get the effect of a VNC connection within seaside for debugging purposes.
It just seems nuts that we have a socket connecting a web browser to the seaside website and can't use it to get access to the squeak UI when there are problems. Yes, people have made sorta-kinda workarounds that provide a way to start up a VNC server on a chosen socket, but that still leaves having to do assorted ssh magic to tunnel the vnc socket. Boring!
Agreed! Unfortunately at least for me, Nebraska is not really fast enough for enjoying interactive working with the remote Squeak image. I would prefer something where the "view" (e.g., the windows and widgets) run still in my local image and only the "model" (i.e., the Browser object or the Inspector object) is located at the remote. But that probably goes into the direction of Croquet (which I never explored and most likely does not work in modern Squeak anyway) ...
Best, Christoph
tim
tim Rowledge; tim(a)rowledge.org; http://www.rowledge.org/tim Useful random insult:- Always responds to "Make Money Fast" postings on the Net.
--- Sent from Squeak Inbox Talk
squeak-dev@lists.squeakfoundation.org