[[Describe.]]





Three senses:
   * Tk within frame of other application (written in, for example, Visual C++).  So far, only works--barely--with IE.
   * Other application within frame of Tk
   * Tk application that also invokes, say, MFC widgets.

[Jeffrey Hobbs] and [David Gravereaux] know the most about these.  None
of them really work as of January 2002 without a lot of fiddling ...

[Arjen Markus] There may be a connection with [Drawing Into Foreign Windows].

[Frame] and [toplevel] bear on this topic.

-----------------------------------------------------
placing the Tk widgets in IE has been simplified by using the TclControl activeX. Using the IE version 6.0, I have found it to be the most stable...

TclControl can be found at:
http://www.sys.uea.ac.uk/~fuzz/optcl/default.html

I have made little to no changes to many Tcl/Tk apps that can run within the IE window... Yes you still need to have a copy of Tcl/Tk installed (but so does java requires a VM to be resident)...Of coarse you need to worry about security issues by allowing the activeX to access Tcl...

James Garrison <garrison@qualcomm.com>








[[Explain tangential connections of [TclScript] and [GPS] work.]]

----

The point of TclScript is to plug in the Tcl '''language''' as an IE extension. This would mean that IE would be able to parse pages with the following type of script code:

   <script language="TclScript">
      package require base64
      proc encode_text {str} {
          return [base64::encode $str]
      }
      proc show_dialog {message} {
          toplevel .dlg
          ....
      }
   </script>
   <form ....>

This isn't quite the same as the ActiveX component which has more to do with placing a Tk toplevel widget onto the browser window and processing Tcl script within itself. 

Of course at present (Jan 2002) TclScript remains vapour-ware (or maybe liquid-ware as there is code, it's just not useable :) ) but I hope to find the time to continue at some point this year. [PT]

----