This is the mail archive of the
xconq7@sources.redhat.com
mailing list for the Xconq project.
Re: New Xconq Windows Executable
- From: Eric McDonald <mcdonald at phy dot cmich dot edu>
- To: Hans Ronne <hronne at telia dot com>
- Cc: xconq7 at sources dot redhat dot com
- Date: Wed, 27 Aug 2003 14:40:41 -0400 (EDT)
- Subject: Re: New Xconq Windows Executable
Hi Hans,
On Wed, 27 Aug 2003, Hans Ronne wrote:
> Anyway, getting tcltk from AS (for Windows users) is a good idea for
> several reasons. First, the AS installer makes sure that all files are put
> in the right places. Second, you always get the latest version that way.
> Third, tcltk is a huge package, much bigger than Xconq.
Not that I care too much about marketing, but I do think that this
extra step of going out and getting the AS Tcl/Tk reflects poorly
on Xconq's perceived level of "sophistication."
If we want to release our own Tcl/Tk bundle, I really only think a
few things would be necessary:
(1) The Tcl and Tk DLL's.
(2) The Tcl scripts for Tk et al.
(3) A .reg file with the appropriate registry entries. (Harcoded
paths will have to be assumed, I think. Probably something like
"C:\Program Files\Xconq\ASTcl".)
(4) A simple install.bat to create the official Xconq install
directory and populate it.
Things could be even smoother and more dynamic if we can find a
free installer program. I haven't checked the licensing of things
like InstallShield (Lite?).
But maybe it is not worth the effort....
I have not given SDL serious consideration. Are there any
bundling issues with that?
Regards,
Eric