Requires Snit. Run tclsh8.5 server.tcl and open your browser to http://localhost:9001
I've recently started putting together a Tk-over-jQuery routine I'm calling web Tk (wtk). The idea is having full Tcl running on a server, with a Tk-like layer that sends commands to code running in a browser.
For those of you who remember it, this is conceptually similar to ProxyTk (see http://www.markroseman.com/pubs/proxytk.pdf).
An important thing is that its not tied into any particular web server or other communication channel; in fact, it just assumes there is a communication channel of some sort. This might be an AJAX connection pair, WebSockets, socket.io, etc. Or it might not even be a remote communication. You could well have a desktop/iPad app whose UI is a web view, and the "communication" between "server" and "client" might be just a procedure call.
The implementation is based on Snit, and the demo uses simple Ajax communication over a generic minihttpd.tcl-derived web server. Incidentally, while I've never really used Snit before, it's a clear win for this type of thing; you'll see from the widget code that the amount of overhead needed to translate the "tk-like" commands into Javascript/jQuery calls is fairly minimal. This is important as I want to make this very easy for people to extend, wrap other jQuery widgets, etc.
It's still at what I'd consider the proof of concept stage, but it feels very promising.
Notes:
Starting the wtk app server:

|
|

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

Requires TclOO. Run tclsh8.5 server.tcl and open your browser to http://localhost:9001
I've recently started putting together a Tk-over-jQuery routine I'm calling web Tk (wtk). The idea is having full Tcl running on a server, with a Tk-like layer that sends commands to code running in a browser.
For those of you who remember it, this is conceptually similar to ProxyTk (see http://www.markroseman.com/pubs/proxytk.pdf).
An important thing is that its not tied into any particular web server or other communication channel; in fact, it just assumes there is a communication channel of some sort. This might be an AJAX connection pair, WebSockets, socket.io, etc. Or it might not even be a remote communication. You could well have a desktop/iPad app whose UI is a web view, and the "communication" between "server" and "client" might be just a procedure call.
The implementation is based on TclOO, and the demo uses simple Ajax communication over a generic minihttpd.tcl-derived web server. TclOO translates the "tk-like" commands into Javascript/jQuery calls with fairly minimal code. This is important as I want to make this very easy for people to extend, wrap other jQuery widgets, etc.
It's still at what I'd consider the proof of concept stage, but it feels very promising.
Notes:
Starting the wtk app server:

This software is copyrighted by the Sean Woods. The following terms applyto all files associated with the software unless explicitly disclaimed inindividual files.The authors hereby grant permission to use, copy, modify, distribute,and license this software and its documentation for any purpose, providedthat existing copyright notices are retained in all copies and that thisnotice is included verbatim in any distributions. No written agreement,license, or royalty fee is required for any of the authorized uses.Modifications to this software may be copyrighted by their authorsand need not follow the licensing terms described here, provided thatthe new terms are clearly indicated on the first page of each file wherethey apply.IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTYFOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGESARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANYDERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THEPOSSIBILITY OF SUCH DAMAGE.THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY,FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWAREIS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVENO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, ORMODIFICATIONS.GOVERNMENT USE: If you are acquiring this software on behalf of theU.S. government, the Government shall have only "Restricted Rights"in the software and related documentation as defined in the Federal Acquisition Regulations (FARs) in Clause 52.227.19 (c) (2). If youare acquiring the software on behalf of the Department of Defense, thesoftware shall be classified as "Commercial Computer Software" and theGovernment shall have only "Restricted Rights" as defined in Clause252.227-7013 (c) (1) of DFARs. Notwithstanding the foregoing, theauthors grant the U.S. Government and others acting in its behalfpermission to use and distribute the software in accordance with theterms specified in this license.