Re: reusing "code entities" without oop

Aric Bills wrote:
There are ways to do this in pure Tcl. However, if your primary purpose
is to create re-useable Tk components, then I'd recommend using Snit
(http://wiki.tcl.tk/snit). It is itself pure Tcl code, and is very well
polished for this kind of work.

-- Neil

I second this suggestion. Snit is all of 376K (compare to the size of
Python + Tkinter - Tcl/Tk itself), and was designed with Tk GUI
components in mind. It also feels very "tcl-ish" (rather than C+
+ish), which I consider to be a strength.

Here's an example of a (useless) component coded in Snit. It's an
entry widget with a history feature. Hopefully it gives you a feel
for what it's like to write Tk code with Snit.

And I have heard that once the OO support makes it into the core that Snit will be lighting fast.

--
+--------------------------------+---------------------------------------+
| Gerald W. Lester |
|"The man who fights for his ideals is the man who is alive." - Cervantes|
+------------------------------------------------------------------------+
.

Relevant Pages

  • Re: Installed Hard Disk In Dell Vista Machine Today
    ... Earth to snit - john claimed to have read the information in a _specific ... Stupid fuck Tim Adams: He just can't understand the topic has been PROVEN ... Too bad none of your references _recommend_ one method ...
    (comp.sys.mac.advocacy)
  • Re: XP: Cool feature with a weakness
    ... Snit wrote: ... And they still fail to support your claims, and I recommend people ...
    (comp.sys.mac.advocacy)