home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.lang.tcl
- Path: sparky!uunet!eco.twg.com!twg.com!news
- From: "David Herron" <david@twg.com>
- Subject: Re: tk-style interface to other windowing systems
- Message-ID: <1992Aug31.214206.3096@twg.com>
- Sensitivity: Personal
- Encoding: 27 TEXT
- Sender: news@twg.com (USENET News System)
- Conversion: Prohibited
- Organization: The Wollongong Group, Inc., Palo Alto, CA
- Conversion-With-Loss: Prohibited
- Date: Mon, 31 Aug 1992 21:44:44 GMT
- Lines: 27
-
- [My long posting deleted ...]
-
- joe@athena.mit.edu (Joseph C Wang) writes:
-
- > Do 1), and then write a Tk initialization file so that MS-Windows
- > emulation is done in Tk instead on in C-code. The advantage is that
- > you have the functionality of 2) with only the work of 1). For one
- > thing, if you do things this way, you can grep the Tk code for the x
- > graphics primitives, and you'll know all the places that you need to
- > change.
-
- But this doesn't promote code re-use. As the MicroSoft guys improve
- and fix their code we wouldn't see the improvements unless we also
- improved and fixed our emulation of their code. This is why I preferred
- the second route (of encapsulating the MS-Windows widgets into
- tk-like commands).
-
- Don't get me wrong, you have some good points and good suggestions
- for another way of code reuse (resuing tk's code). Your route also
- gives us the problem of keeping up with tk's improvements &c, unless
- these changes were to become part of the mainstream tk source base.
- As Jon comes out with new releases we'd have to re-do the port over
- to MS-Windows (and whatever-else-Windows)...
-
- I'll spend some time this evening looking at this...
-
- David
-