From owner-freebsd-chat Mon Feb 1 15:16:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA03037 for freebsd-chat-outgoing; Mon, 1 Feb 1999 15:16:29 -0800 (PST) (envelope-from owner-freebsd-chat@FreeBSD.ORG) Received: from flood.ping.uio.no (flood.ping.uio.no [129.240.78.31]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03025 for ; Mon, 1 Feb 1999 15:16:24 -0800 (PST) (envelope-from des@flood.ping.uio.no) Received: (from des@localhost) by flood.ping.uio.no (8.9.2/8.9.1) id AAA41979; Tue, 2 Feb 1999 00:16:18 +0100 (CET) (envelope-from des) To: "Jason C. Wells" Cc: W Gerald Hicks , freebsd-chat@FreeBSD.ORG Subject: Re: Lets Endorse KDE Was: some slashdot thread References: From: Dag-Erling Smorgrav Date: 02 Feb 1999 00:16:16 +0100 In-Reply-To: "Jason C. Wells"'s message of "Mon, 1 Feb 1999 17:46:03 +0000 (GMT)" Message-ID: Lines: 46 X-Mailer: Gnus v5.5/Emacs 19.34 Sender: owner-freebsd-chat@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org "Jason C. Wells" writes: > Again, making KDE a default will help new users. Thos of us who know how > to swing our X configs to and fro don't need or necessarily like KDE. > Don't judge this issue on the fact that KDE is not a 20 year development. > Judge this issue on the help KDE will provide newbies. Put yourself in a > non-cs degreed non-programmer non-unix users shoes and then look at the > issue. I mostly agree with Jason on this point. Making KDE an easily- installable option, if not the default (remember, even XFree(& isn't installed by default), and having somebody look after KDE to make sure it works out of the box, may (will?) do wonders for FreeBSD's popularity with the "masses". I am considering switching to KDE myself (I've used twm / tvtwm so far, but it has a few annoying bugs which I haven't been able to fix; its greatest strength is simplicity). It's either that or Windowmaker; if I end up using KDE, I'll certainly be willing to help maintaining a "newbie's KDE package". These are the features I personally require of a window manager: 1) It must have virtual desktops. 2) It must allow binding viewport switching to keys 3) It must allow binding the usual window operations (delete, kill, maximize, iconify, horizontal / vertical zoom) to keys 4) it must allow binding mouse movement or at least window hopping to keys. If possible, it should allow binding mouse clicks to keys (fvwm2 can do that). tvtwm has 1, 2 and 3, and I've hacked it to do 4 (mouse movement, no clicks unfortunately; my knowledge of XLib programming is rather limited). fvwm2 has all four, but looks like shit and is untrivial to configure. I didn't include configurable root window menus in the list since practically all window managers have that. One more thing I didn't mention is: the window decorations mustn't get in the way (I like thin handle-less black borders and simple twm-style title bars) Check out http://flood.ping.uio.no/~des/snap.gif for a snapshot of my current tvtwm setup. DES -- Dag-Erling Smorgrav - des@flood.ping.uio.no To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-chat" in the body of the message