If you could test that the new install features on a few live distros, that would be great!
I have all your stuff integrated but did not want to risk anything for 8.1.1. There is also a small change in newlisp-tk.tcl, which I did not want to have exposed for this release. I have had too much trouble with directory and startup issues in newlisp-tk in the past.
I just put 8.1.1 with the UDP timeout fix in the development directory and want to put this in the release directory tomorrow.
I will do a 8.1.2 development release shortly after with the new make file features for the $HOME install.
Lutz
Problem with UDP
-
- Posts: 429
- Joined: Tue Nov 11, 2003 2:11 am
- Location: Brisbane, Australia
I'll look out for it Lutz
Maybe you should consider using the even=stable odd=devel system
for the minor version number a la kernal etc
with 8.2 the next stable release and 8.2.1 etc bug fixes
and 8.3.z the devel series - or maybe that's going too far for newlisp?
It would more clearly split off the new testing stuff.
Nigel
Maybe you should consider using the even=stable odd=devel system
for the minor version number a la kernal etc
with 8.2 the next stable release and 8.2.1 etc bug fixes
and 8.3.z the devel series - or maybe that's going too far for newlisp?
It would more clearly split off the new testing stuff.
Nigel
Broadcast
Hello Lutz,
Actualy i ran into the fact that a (net-receive-udp) is the only option
under linux to receive a broadcast message. Where on windows also
a (net-listen...) (net-receive-from) works on receiving boradcasts....??
Could this be correct?
Regards, Norman/
Actualy i ran into the fact that a (net-receive-udp) is the only option
under linux to receive a broadcast message. Where on windows also
a (net-listen...) (net-receive-from) works on receiving boradcasts....??
Could this be correct?
Regards, Norman/
-- (define? (Cornflakes))
Hi all,
Just to let you know, I created a simple UDP chat using GTK. Though fully functional, it's more like an advanced demonstration. Screenshots can be found here:
http://www.gtk-server.org/apps.html
The full source can be downloaded there as well.
--------------------
Features:
- Full GTK2.x
- Using scrolled text_view widget
- Memorizes last entered configuration
- Works on Linux and Win32 with same source code
- Uses encryption of the actual chat
Bugs, remarks, comments are welcome.
Peter.
Just to let you know, I created a simple UDP chat using GTK. Though fully functional, it's more like an advanced demonstration. Screenshots can be found here:
http://www.gtk-server.org/apps.html
The full source can be downloaded there as well.
--------------------
Features:
- Full GTK2.x
- Using scrolled text_view widget
- Memorizes last entered configuration
- Works on Linux and Win32 with same source code
- Uses encryption of the actual chat
Bugs, remarks, comments are welcome.
Peter.
No, the chatprogram is server and client at the same time!
So, when somebody sends a UDP DGRAM to your IP address, it will be displayed by the chat program.
You have to specify the IP address in the upper entry, with a port. (If you do not specify a port, the default port 54000 is used.)
The IP address specifies the remote host, where you send your chat (DGRAM) to. The specified port however is BOTH the remote port AND ALSO the local port, where the chat program listens for incoming DGRAMS. So the port number should be the same on both sides, as well as the encryption string.
I hope you enjoy the chat!
So, when somebody sends a UDP DGRAM to your IP address, it will be displayed by the chat program.
You have to specify the IP address in the upper entry, with a port. (If you do not specify a port, the default port 54000 is used.)
The IP address specifies the remote host, where you send your chat (DGRAM) to. The specified port however is BOTH the remote port AND ALSO the local port, where the chat program listens for incoming DGRAMS. So the port number should be the same on both sides, as well as the encryption string.
I hope you enjoy the chat!