From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 19889 invoked by alias); 27 Aug 2003 18:40:53 -0000 Mailing-List: contact xconq7-help@sources.redhat.com; run by ezmlm Precedence: bulk List-Subscribe: List-Archive: List-Post: List-Help: , Sender: xconq7-owner@sources.redhat.com Received: (qmail 19866 invoked from network); 27 Aug 2003 18:40:50 -0000 Received: from unknown (HELO garm.central.cmich.local) (141.209.15.48) by sources.redhat.com with SMTP; 27 Aug 2003 18:40:50 -0000 Received: from leon.phy.cmich.edu ([141.209.165.20]) by egate1.central.cmich.local with Microsoft SMTPSVC(5.0.2195.5329); Wed, 27 Aug 2003 14:40:46 -0400 Received: from localhost (unknown [127.0.0.1]) by leon.phy.cmich.edu (Postfix) with ESMTP id 8DB4370019; Wed, 27 Aug 2003 14:40:41 -0400 (EDT) Date: Wed, 27 Aug 2003 19:53:00 -0000 From: Eric McDonald To: Hans Ronne Cc: xconq7@sources.redhat.com Subject: Re: New Xconq Windows Executable In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-OriginalArrivalTime: 27 Aug 2003 18:40:46.0330 (UTC) FILETIME=[BA6B65A0:01C36CCA] X-SW-Source: 2003/txt/msg00381.txt.bz2 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