[gopher] Re: 32-bit Windows Gopher Client desperately needed

[JumpJet Mailbox <jumpjetinfo@xxxxxxxxx>]

I would suggest the Windows 2000 look-and-feel.  
 
Microsoft spent many man-hours in the lab watching users eye / hand movements 
as well polling their desires in color schemes, frame sizes and shapes, etc., 
when they developed the Windows 2000 interface.  The look-and-feel of 
Windows 2000 was once applauded by industry experts (I'm not kidding) as well 
researched.  Why they tossed it away for the "fat and rounded" Windows XP 
look-and-feel I will never know, but it was probably market driven (we need to 
look "fresh") rather than scientifically chosen.
 
Stick to "expected" object actions, keyboard shortcuts, pulldown menu items 
(including names and placement), mouse menus, etc., and KEEP THE 
DEFAULTS LEAN (everything "turned off"), and you will go a long way 
towards user acceptance of your Gopher Client.

--- On Thu, 6/5/08, Michael Casadevall <sonicmctails@xxxxxxx> wrote:

From: Michael Casadevall <sonicmctails@xxxxxxx>
Subject: [gopher] Re: 32-bit Windows Gopher Client desperately needed
To: gopher@xxxxxxxxxxxx
Date: Thursday, June 5, 2008, 5:35 PM

The Qt library provides a cross-platform UI for Windows, Mac OS X
(although I find it doesn't feel "right"), and Linux. I'm
hoping to
write my client using Qt, and failing that, well ... I think I still
remember raw Win32 API ;-).

What I'm more worried about is the functional design of the client then
actually coding it. I'll start working that out after I finish
doxyifying libgopher.
Michael

On Thu, 2008-06-05 at 14:25 -0700, Cameron Kaiser wrote:
> The problem is I'm not very experienced
> with Windows development, and I don't use it regularly except at the
> office. There is definitely room for someone wanting to write a modern
> Windows gopher client.