Message-ID:	<009a01be86b6$f7e80360$88003bd4@default>
From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
To:	<djgpp-workers AT delorie DOT com>
Cc:	"Salvador Eduardo Tropea (SET)" <salvador AT inti DOT gov DOT ar>,
	"DJGPP Workers" <djgpp-workers AT delorie DOT com>
Subject:	Re: LBInstDJ
Date:	Wed, 14 Apr 1999 22:20:34 +0200
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-Mailer:	Microsoft Outlook Express 4.72.3612.1700
X-MimeOLE:	Produced By Microsoft MimeOLE V4.72.3612.1700
Reply-To:	djgpp-workers AT delorie DOT com

>> BTW, about user's interface: how about porting it to turbo vision?
>
>I think the installer should be as non-demanding on system hardware
>and software as it can.  A simple ASCII interface would be the best
>approach for the first approximation.  Once you have the basics
>working, you can add bells and whistles.  There's nothing as
>frustrating as a runaway installer with a cute display...
>

Yes, anyway I will strive to develop good working code at first and then
add bells and whistles. But: TVision is not demanding on system
hardware, DJGPP is more demanding by itself. (I've run turbo vision
prgs made with tp 7.0 on my old 286 with CGA display (wow...) w/o
problems. Could I run DJGPP on that?) Second reason which makes
this way attractive is that it is much better, safer way to update
autoexec.bat
because user can review all changes to autoexec.bat, modify them, discard
them, accept them. I understand that it does not let me to write bad update
code and just rely on user's ability to put it in proper place. I will have
to
pick the best suggestion for user.

Laurynas Biveinis

- Raw text -