I am playing with the simulation of swarm.
You can find it here as a file swarm.lsp:
http://www.volny.cz/fsodomka/newlisp/
Enjoy, Fanda
Swarm in newLISP
Here is a simple program to run Fanda's swarm.lsp and inversi.lsp without newlisp-tk just using the concole app newlisp and a Tcl/Tk installation: http://newlisp.org/index.cgi?page=Tk_and_newLISP
Lutz
Lutz
Unfortunately, 'peek' is only available on UNIX like operating systems =>
will not work on Windows.
Just wanted to let you know...
Fanda
Code: Select all
(while (= (peek myin) 0))
Just wanted to let you know...
Fanda
Hello!
I have been trying to make it work on Windows.
Some scripts run just fine, when I comment the line:
(while (= (peek myin) 0))
I added error checking and divided (write-line ...) into 2 lines. Inversi doesn't want to run, if I write (write-line ...) on 1 line only. (I don't know why.)
I also tried some tests for tk function:
With this tk function both Inversi and Swarm run fine on Windows.
Fanda
I have been trying to make it work on Windows.
Some scripts run just fine, when I comment the line:
(while (= (peek myin) 0))
I added error checking and divided (write-line ...) into 2 lines. Inversi doesn't want to run, if I write (write-line ...) on 1 line only. (I don't know why.)
Code: Select all
; tk function to pass commands to Tcl/Tk
(define (tk)
(write-line (append "if { [catch { puts [" (apply string (args)) "] }] } { " [text] tk_messageBox -message "$errorInfo"; exit }
[/text]) myout)
(read-line myin))
(global 'tk)
Code: Select all
; call inside the call
(tk "tk_messageBox -type ok -message {You clicked '" (tk "tk_messageBox -type yesno -message {Click on something :-)}") "'!}")
; catches error correctly:
;(tk "set x [expr {1 +}]")
; it doesn't catch bad brackets -> freezes up afterwards!
;(tk "set x {whatever here")
Fanda
You may check if the the 'read-line' on a pipe in Windows blocks or not when no data is available. On Unix 'read-line' will not block but return a 'nil'. This is why the (peek myin) comes in handy.
If 'read-line' doesn't block on Windows either, you might just put (sleep ..) statements before reading to make sure data is available. Perhaps splitting the 'write-line' changes the timing.
Or, if it blocks, make sure there is always data to read ready from the TclTk side. If no data is available and it blocks, newLISP would sit in the 'read-line' and freeze.
I will try your new (tk ..) function with error checking when I get to a Windows machine and incorporate it into nl-tcltk.
Lutz
If 'read-line' doesn't block on Windows either, you might just put (sleep ..) statements before reading to make sure data is available. Perhaps splitting the 'write-line' changes the timing.
Or, if it blocks, make sure there is always data to read ready from the TclTk side. If no data is available and it blocks, newLISP would sit in the 'read-line' and freeze.
I will try your new (tk ..) function with error checking when I get to a Windows machine and incorporate it into nl-tcltk.
Lutz
- I believe that 'read-line' on Windows blocks when no data is available. I think, we can prove it using "call inside the call" - without 'peek' on Unix it should return "You clicked 'nil'". (Could anybody try it on Unix without 'peek', please?)
On Windows it waits and says correctly 'yes' or 'no'.
- We could write 2 versions of tk function:
if OS is Unix -> tk with 'peek' - else - tk without it
- My guess when splitting the 'write-line' to 2 lines was that Tcl needs some spaces or end of line characters to correctly process the command(s).
- The 3rd tk test of catching the bad brackets freezes up because Tcl can't process the command correctly - it's missing the brackets, but will not throw an error because there is no clear beginning and the end of commands (including catch and puts).
- I would like to add a constant to nl-tcltk
It's useful when exiting the script
nelisp-tk -> deiconify '.'
wrapper -> exit wish and exit newlisp
Fanda
On Windows it waits and says correctly 'yes' or 'no'.
- We could write 2 versions of tk function:
if OS is Unix -> tk with 'peek' - else - tk without it
- My guess when splitting the 'write-line' to 2 lines was that Tcl needs some spaces or end of line characters to correctly process the command(s).
- The 3rd tk test of catching the bad brackets freezes up because Tcl can't process the command correctly - it's missing the brackets, but will not throw an error because there is no clear beginning and the end of commands (including catch and puts).
- I would like to add a constant to nl-tcltk
Code: Select all
; constant to differentiate between newlisp-tk and this wrapper
(constant (global 'NL-TCLTK) true)
nelisp-tk -> deiconify '.'
wrapper -> exit wish and exit newlisp
Fanda
There is a new version 0.07:
- it doesn't show an error when closing the window (=> it's a little bit slower than 0.06)
- window has a different size in x and y (MX MY) and can be resized!
- Tk code clean up
- can be run by both newlisp-tk and Tk wrapper (exits correctly)
Visually it's pretty much the same...
Fanda
- it doesn't show an error when closing the window (=> it's a little bit slower than 0.06)
- window has a different size in x and y (MX MY) and can be resized!
- Tk code clean up
- can be run by both newlisp-tk and Tk wrapper (exits correctly)
Visually it's pretty much the same...
Fanda