Date: Tue, 04 Mar 1997 09:43:23 +1200
From: Bill Currie <billc AT blackmagic DOT tait DOT co DOT nz>
Subject: Re: IDE for NASM
To: Robert Hoehne <Robert DOT Hoehne AT Mathematik DOT tu-chemnitz DOT de>
Cc: djgpp AT delorie DOT com
Reply-to: billc AT blackmagic DOT tait DOT co DOT nz
Message-id: <331B45FB.6BE7@blackmagic.tait.co.nz>
Organization: Tait Electronics NZ
MIME-version: 1.0
Content-type: text/plain; charset=us-ascii
Content-transfer-encoding: 7bit
References: <970303021215_278799750 AT emout17 DOT mail DOT aol DOT com>
 <331ABF14 DOT 628 AT Mathematik DOT tu-chemnitz DOT de>

Robert Hoehne wrote:
> In general RHIDE can be used as an IDE for mostly any source files.
> But to use other than the builtin known compilers you should do
> some configuration work by setting environment variables. (Read
> the doc for a describtion, how it can be done).
> 
> But the NASM builtin support is on my todo-list for the next
> version(s).

I would suggest using a list of file extension associations (kind of
like file manager/dosshell etc) that's user configerable (that's what
I'm doing in my own editor).  This would only provide the DEFAULT
'compiler' and command line options for a file type.  Each file in the
project list would inherit the properties associated with its type on
insertion, but ALL of the info needed to 'compile' the file would be
fully editable (including the 'compiler').  TC/BC came close to this
with their project files, but the use could not specify a program that
was not in the transfer list (a bit of a hassle IMO).

If this is already in RHIDE (I don't use it my self, so I wouldn't
know), or what you are planning, sorry to bother you.

Bill
-- 
Leave others their otherness.