5 ms·
>you can have Tk (as long as your Cobol allows you to call C). No C required, you can just connect to the UI through a socket and often skip the FFI completely
by ofalkaed 16d ago
>you can have Tk (as long as your Cobol allows you to call C).
No C required, you can just connect to the UI through a socket and often skip the FFI completely. This is my preferred way to use Tk and I don't even consider anything else unless there is a reason. Working this way also has the nice side effect of making the application UI agnostic.
- WalterGR 16d agoBut then you have an entire front end written in Tcl or some other non-COBOL language (to continue the above example,) right? Or is there a way to run Tk as a daemon?
- ofalkaed 16d agoBelieve you have to do that anyways unless you are going to create full language bindings as tkinter and the like do. I don't know the Tk API in full but I don't believe it provides ways to create widgets, just interact with them more directly. Perhaps someone more knowledgeable will fill in the gaps here, I learned what I needed of the Tk API and called it good.
- em-bee 16d agothat sounds interesting. can you give an example please?
- ofalkaed 16d agoPureData is a good example.