• a bug fix for UDP broadcast mode on big-endian CPUs (MacOSX, Sparc)
• broadcast UDP mode added to 'net-connect', was previously only available on blocking UDP with net-send-udp/net-receive-udp
• big speed increase for 'replace' in larger string buffers, on 100k buffers 30x on 500k buffers 600x times speed increase
for files see and etailed change notes see here: http://newlisp.org/downloads/development
Lutz
Hello Lutz,
nice additions, I like the new tcltk.lsp sample.
It allows to build small tools together with link.lsp fast.
That start me thinking of another option:
Is it possible to use this pipe-commincation the other
way round. So instead of using TCP/IP like in newLISP-TK,
to build a small tcl-code which can be wrapped like newLISP-TK
which uses pipe-communication to a newLISP-EXE started from
the TCL-app. So at least similar demo from tcltk.lsp running from
a embedded TCL/TK for users with no installed TCL/TK.
When this way of communication is not possible it would be at least
an option to build a TCL/TK-app which contains the TCL/TK runtime as
a wrapped EXE for NON-TCL-PC.
(process "MyEmbeddedTclTkApp" tcin tcout)
Then 2 files have to be delivered:
MyLinkednewLISP.exe
MyEmbeddedTclTkApp.exe
Also this may let us get away the wish command window.
I assume one could just change the existing comunications mechanism in newlispl-tk. I chose tcp/ip to make it possible to have the Tcl/Tk frontend and newlisp.exe on a different computer. I do not think it his possible to start Tk without the toplevel '.' dot window, but you can always hide it.
Lutz
Is there a problem with the Wish command window?
As far as i know you dont have to display it, but i dont understand the
initial problem so i cant drop an example ;-)
Btw, thanks Lutz for the addons in 857
Regards, Norman.
Quote from: "Lutz"
Maybe it is worth to think about this option, because for multisession tasks you have to generate new IP-number pairs for each session-comminication via TCP/IP. Is that possible with pipe-communication?
Quote from: "Norman"
Is there a problem with the Wish command window?
The additional window is not so nice for each small tool-window.
(1) You would have the same situation with pipes.
(2) You can hide the window on start-up. The newlisp-tk maual shows you how to do this. Or even better use the '.' window in your applications, this is how the program examples/tcltk.lsp does it. The whole point is really mute, because if you are using TK it is because you want a window ;)
Lutz
Quote from: "Lutz"
I thought each session pair could have it's own pipe.
Anyway, then I could stay with tcp/ip.
Quote from: "Lutz"
...., this is how the program examples/tcltk.lsp does it. The whole point is really mute, because if you are using TK it is because you want a window ;)
I miss this point. When I start 'newlisp.exe tcltk.lsp' I get 2 windows!
(the small TK window with the 3 button and the black command shell.)
And sure I use TK, because I want my (1) window.
Of cource we can use Peter's run-wrapper:
http://www.turtle.dds.nl/run/index.html
Ok, I misunderstood, you mean the shell window popping up. Yes, Peters 'run.exe' works well to suppress that from coming up.
Lutz