From owner-freebsd-hackers Mon Aug 21 06:49:28 1995 Return-Path: hackers-owner Received: (from majordom@localhost) by freefall.FreeBSD.org (8.6.11/8.6.6) id GAA20219 for hackers-outgoing; Mon, 21 Aug 1995 06:49:28 -0700 Received: from time.cdrom.com (time.cdrom.com [192.216.222.226]) by freefall.FreeBSD.org (8.6.11/8.6.6) with ESMTP id GAA20211 for ; Mon, 21 Aug 1995 06:49:25 -0700 Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.6.11/8.6.9) with SMTP id GAA10938; Mon, 21 Aug 1995 06:49:11 -0700 To: Peter da Silva cc: hackers@freebsd.org Subject: Re: Any reason we can't enable the bus mouse by default? In-reply-to: Your message of "Mon, 21 Aug 1995 07:38:15 CDT." <199508211238.HAA11059@bonkers.taronga.com> Date: Mon, 21 Aug 1995 06:49:11 -0700 Message-ID: <10935.809012951@time.cdrom.com> From: "Jordan K. Hubbard" Sender: hackers-owner@freebsd.org Precedence: bulk > You obviously have experience with a lot more APIs than I, but I don't > see the Tk API being that convoluted compared with others that people > are apparently entirely happy to use. It's simpler than any other X-based > API I've ever used, for example. I think you misunderstood me. I have no particular bone to pick with Tk per-se (though it could no doubt be improved and John himself has said that if he could do it over, he would do many things differently), what I have a problem with is the "Tk philosophy" extended to cover other imaging models! It just wasn't designed with that in mind! Sure, write X apps in Tk to your heart's content - you'll have plenty of good company and freely available add-on frobs to use. But the minute you're forced to support multiple models with one API, then that's the moment it's time to go up a level to something that sits on top of Tk and curses alike. Tell ya what. Let's wait and see. :-) Jordan