powelld@cs.rpi.edu said:
powelld> I have been experimenting with the tkined interface
powelld> without scotty. In the tkined documentation, the file
powelld> ined.tcl, is mentioned. The documentation indicates
powelld> that this file should be loaded to access different
powelld> ined commands. I do not see this file as part of the
powelld> tkined.1.2.2 release. Am I missing something or do I
powelld> need to manipulate objects differently without scotty.
This is an error in the documentation. I removed the file ined.tcl
because Scotty does not use it and the code in ined.tcl was based on
extensions which are not part of standard Tcl. So it was quite
unusable.
A quick solution is to include the ined.c module from the Scotty
sources in your Tcl interpreter. However, you must make some changes
to ined.c if your Tcl interpreter is not event driven.
A more general solution would first require to rework the protocol
used between Tkined and the applications. The current protocol uses a
message format from the early ined days which is horrible. I tried to
write a perl interface for Tkined a few weeks ago (well I have to
admit that I am not a perl guru) and I stopped as soon as I recognized
that the protocol needs to be changed first.
Before I start to think about solutions to this problem, I would like
to know if there is real interest in interfaces to other languages
(e.g. perl, python, plain C or whatever) to access Tkined. I would be
willing to spend some time to clean up the current interface if there
are volunteers to write interfaces for languages I am not familiar
with.
Juergen