public inbox for xconq7@sourceware.org
 help / color / mirror / Atom feed
From: Eric McDonald <mcdonald@phy.cmich.edu>
To: Hans Ronne <hronne@comhem.se>
Cc: xconq7@sources.redhat.com
Subject: Re: Windows Installer for Xconq
Date: Mon, 03 Nov 2003 18:09:00 -0000	[thread overview]
Message-ID: <Pine.LNX.4.44.0311031209111.20872-100000@leon.phy.cmich.edu> (raw)
In-Reply-To: <l03130301bbcc35a660b8@[212.181.162.155]>

On Mon, 3 Nov 2003, Hans Ronne wrote:

> This is great! Precisely what we needed.

Thanks. Glad you like it.

> on my somewhat unusal Windows setup. I saw only one minor glitch, and that
> is that the icons are drawn using 4-bit graphics,

Interesting. Which icons? The installer and uninstaller icons? 
Except for a misguided attempt to borrow an icon from Xconq.ico 
for the Xconq documents, I don't recall having any other icons.

> available. When I compile the icons into the exe file, the correct depth is
> used, so this is not just a setup problem.

Yes, this is my plan. I think that I will need to use windres, 
which is provided with Cygwin, to use the Xconq.RC file to make an 
obj file to link in.

> I just checked in the new document icons for Windows. So when you get
> around to binding icons, you could bind those to the xcq extension.

Will do. Thanks.

I also think it might be a good idea to toss up a GPL license 
screen at the beginning of the install process. I played with that 
yesterday but was experiencing some issues.

And I envision a user being able to choose between a "Minimal" 
(xconq.exe plus game library and support stuff), 
"Standard" (Minimal plus imfapp.exe), and "Full" install 
(Standard plus the sources). I have rudimentary support for 
this in the install script, but nothing that is visible yet. I 
suppose "Custom" could also become an option, __but, one thing at 
a time.

Eric

P.S. I will check in my NSIS (Nullsoft Scriptable Install System) 
script later this week. Nullsoft is the same company that makes 
Winamp, which is why the installer interface might seem familiar 
to some.

  reply	other threads:[~2003-11-03 17:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-03  8:32 Eric McDonald
2003-11-03 17:27 ` Hans Ronne
2003-11-03 18:09   ` Eric McDonald [this message]
2003-11-03 20:14     ` Hans Ronne
2003-11-03 21:21     ` Jim Kingdon
2003-11-03 21:42       ` [OFFTOPIC?] Doc Chow (was Re: Windows Installer for Xconq) Eric McDonald
2003-11-04  6:45 ` Windows Installer for Xconq Eric McDonald
2003-11-04 13:43   ` Hans Ronne
2003-11-04 16:37     ` Eric McDonald
2003-11-04 19:07       ` Hans Ronne
2003-11-04 20:03       ` Brandon J. Van Every
2003-11-04 21:25         ` Hans Ronne
2003-11-04 21:36           ` Brandon J. Van Every
2003-11-04 23:24             ` Brandon J. Van Every
2003-11-05  4:38               ` Hans Ronne
2003-11-05  8:54                 ` Brandon J. Van Every
2003-11-06  5:23                   ` Hans Ronne
2003-11-07  0:57                     ` Eric McDonald
2003-11-07 18:35 Bill Macon
2003-11-07 18:46 ` Jim Kingdon
2003-11-07 23:16   ` 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=Pine.LNX.4.44.0311031209111.20872-100000@leon.phy.cmich.edu \
    --to=mcdonald@phy.cmich.edu \
    --cc=hronne@comhem.se \
    --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).