From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Lincoln Peters <sampln@sbcglobal.net>
Cc: Xconq list <xconq7@sources.redhat.com>
Subject: Re: Three thoughts
Date: Tue, 24 Aug 2004 02:09:00 -0000 [thread overview]
Message-ID: <412A9D1E.4000907@phy.cmich.edu> (raw)
In-Reply-To: <1093308446.2792.30246.camel@localhost>
Lincoln Peters wrote:
>>Also, the "widget styles" of the two toolkits are a bit different
>>and so the resulting UI would end up looking like Frankenstein, I
>>think.
>
> I'm not familiar with TclTk's (Tk's?) "widget style".
You're reading too much into what I meant by "widget style" (which was
in parentheses for a reason). Perhaps another way to put it is simply,
look-n-feel.
> Over the long term, it might be worthwhile to try to develop a common UI
> based on SDL and GTK+/GNOME, since SDL could provide a more game-like
> (i.e. less Office-app-like) interface and GTK+ could provide a bunch of
> features where it doesn't particularly matter if they look like they
> belong in an Office app.
Well, it was not too long ago that I revived this suggestion (having
first made it during the Great Flame War of November 2003), and some of
those who read it infused assumptions into its implications, such as
that I would recommend using GTK components without "redecorating" them
to fit their environment. It took a while to untangle that thread, and I
would rather not go there again any time soon.
> There might be a few hardcore strategy gamers who would appreciate being
> able to use Mono to link Xconq to a spreadsheet application and do some
> intensive data analysis on games like advances.g (e.g. track production,
> technology, offensive/defensive power, over time).
These are some of the benefits that crossed my mind as well when we last
discussed this (last year).
> Perhaps it would be possible to avoid the "hackish" aspect of using
> TclTk and GTK+ simultaneously by completely switching from TclTk to GTK+
> in one fell swoop, but that idea is probably even more scary for most
> developers. The closest I'd expect us to reasonably come to that
> scenario would be to implement GTK+ as a separate interface and then
> label the TclTk interface as a "legacy" interface.
I have thought about this on and off in the past few weeks. After
reviewing the SDL API and GTK API, and looking at the existing SDL code,
I think that I am going to give SDL a try first. (After reading portions
of both API's yesterday, I actually did sit down and fix some bugs in
the SDL app.)
>>The closup view window that you propose is an interesting idea,
>>but I agree that we should try to avoid extra work to fish out an
>>unit, if possible (as someone mentioned in a later message in
>>this thread). One idea that I thought of would be magnify the
>>icon of an unit if the cursor passes over it in a manner similar
>>to that little bar of icons at the bottom of the MacOS X
>>interface (IIRC). Or maybe that magnification should only happen
>>when a modifier key is being pressed when the mouse passes over
>>the unit, so that the magnified view does not normally get in the
>>way of other units in the same hex (and possibly surrounding
>>hexes).
>
>
> Unless you have an intuitive way for the user to indicate
> when to zoom and when not to zoom,
See my suggestion above about pressing a modifier key.
>the user might be rather surprised
> when the mouse hovers over a cell and one unit suddenly gets bigger
> while the others get smaller.
Well, I never suggested that other get smaller....
Does the MacOS X icon bar have that property?
I was just thinking in terms of making one image larger than the others,
and then partially or totally obscuring its neighbors for the duration
of the magnification.
> In conclusion, this kind of zooming is probably more work than you had
> in mind.
I didn't have any amount of work in mind. It was just a suggestion. But,
now that you mention it, I am not sure that it would be so much work.
> Another possibility might be to make the close-up dialog be a separate
> window that displays each unit in the same arrangement as on the main
> screen, but it draws every unit in the cell at the same size.
I think that is what Elijah and Matthew were suggesting (or something
similar), and it is certainly what I had in mind until the "icon
magnification" idea occurred to me.
> http://homepage.mac.com/lmpeters/cell_closeup2.png
404.
Eric
next prev parent reply other threads:[~2004-08-24 1:43 UTC|newest]
Thread overview: 43+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-20 16:22 mskala
2004-08-20 18:34 ` Eric McDonald
2004-08-20 21:17 ` Andreas Bringedal
2004-08-20 21:28 ` Eric McDonald
2004-08-20 23:57 ` Andreas Bringedal
2004-08-21 1:21 ` Eric McDonald
2004-08-21 4:35 ` Jim Kingdon
2004-08-21 20:38 ` Jim Kingdon
2004-08-20 22:03 ` Elijah Meeks
2004-08-20 23:27 ` Eric McDonald
2004-08-21 1:17 ` mskala
2004-08-21 2:31 ` Eric McDonald
2004-08-21 4:33 ` mskala
2004-08-22 3:09 ` Hans Ronne
2004-08-22 6:38 ` Item Units Elijah Meeks
2004-08-22 9:37 ` Eric McDonald
2004-08-24 1:43 ` Lincoln Peters
2004-08-24 2:38 ` Eric McDonald
2004-08-24 2:51 ` Lincoln Peters
2004-08-24 3:32 ` Eric McDonald
2004-08-22 14:00 ` Three thoughts mskala
2004-08-22 18:56 ` Hans Ronne
2004-08-22 19:16 ` Lincoln Peters
2004-08-23 4:31 ` Jim Kingdon
2004-08-23 13:04 ` Elijah Meeks
2004-08-24 18:07 ` Eric McDonald
2004-08-24 20:59 ` Elijah Meeks
2004-08-25 0:54 ` Unit-Image Bug Elijah Meeks
2004-08-25 4:58 ` Eric McDonald
2004-08-23 16:48 ` Three thoughts Eric McDonald
2004-08-24 0:55 ` Lincoln Peters
2004-08-24 2:09 ` Eric McDonald [this message]
2004-08-24 3:02 ` Lincoln Peters
2004-08-24 18:12 ` Eric McDonald
2004-08-25 5:34 ` Jim Kingdon
2004-08-25 17:16 ` Lincoln Peters
2004-08-25 22:09 ` Jim Kingdon
2004-08-26 2:15 ` Eric McDonald
2004-08-26 6:17 ` Jim Kingdon
2004-08-26 19:12 ` Eric McDonald
2004-08-26 22:08 ` CXP??? Elijah Meeks
2004-08-27 1:50 ` CXP??? Lincoln Peters
2004-08-27 5:10 ` CXP??? Eric McDonald
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=412A9D1E.4000907@phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=sampln@sbcglobal.net \
--cc=xconq7@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).