From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: "Brandon J. Van Every" <vanevery@indiegamedesign.com>,
<xconq7@sources.redhat.com>
Subject: Re: Standardizing the Windows build
Date: Sat, 08 Nov 2003 02:33:00 -0000 [thread overview]
Message-ID: <Pine.LNX.4.44.0311072040100.10853-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <l03130300bbd1db5845f2@[212.181.162.155]>
On Sat, 8 Nov 2003, Hans Ronne wrote:
> So my guess is that you would find it easier to work on the Windows
> interface, given your stated interests and preferences. A Windows-native
> (non-Tcl) interface would be a very welcome contribution to Xconq.
Yes. If we swing to SDL as our primary interface during the next
release cycle, one might want to consider native Win32 support
for the UI elements such as menus and windows. Or using a
cross-platform library of UI elements (such as wxWindows, though
it is C++ code)....
Regards,
Eric
next prev parent reply other threads:[~2003-11-08 1:56 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-07 23:46 Brandon J. Van Every
2003-11-08 0:40 ` Eric McDonald
2003-11-08 1:29 ` Brandon J. Van Every
2003-11-08 1:34 ` Eric McDonald
2003-11-08 2:57 ` Brandon J. Van Every
2003-11-08 1:56 ` Hans Ronne
2003-11-08 2:33 ` Eric McDonald [this message]
2003-11-08 2:55 ` Hans Ronne
2003-11-08 11:38 ` Brandon J. Van Every
2003-11-08 22:27 ` Hans Ronne
2003-11-08 22:33 ` SDL and 3D Brandon J. Van Every
2003-11-08 23:29 ` Eric McDonald
2003-11-09 2:45 ` Hans Ronne
2003-11-09 3:33 ` whose Windoze build it is anyways Brandon J. Van Every
2003-11-09 12:52 ` Stan Shebs
2003-11-08 3:06 ` Windows native UIs Brandon J. Van Every
2003-11-08 13:58 ` Hans Ronne
2003-11-08 3:10 ` The gory Xconq kernel Brandon J. Van Every
2003-11-08 13:06 ` Hans Ronne
2003-11-08 22:59 ` Ease of MSVC build Brandon J. Van Every
2003-11-09 0:28 ` Eric McDonald
2003-11-09 0:42 ` Brandon J. Van Every
2003-11-09 1:54 ` Brandon J. Van Every
2003-11-09 4:41 ` easy build trees for non-Xconq gurus Brandon J. Van Every
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=Pine.LNX.4.44.0311072040100.10853-100000@leon.phy.cmich.edu \
--to=mcdonald@phy.cmich.edu \
--cc=hronne@comhem.se \
--cc=vanevery@indiegamedesign.com \
--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).