Xref:	news2.mv.net comp.os.msdos.djgpp:4570
From:	malcolm AT manawatu DOT gen DOT nz (Malcolm Taylor)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Windows applications in djgpp
Date:	Tue, 04 Jun 1996 05:27:20 GMT
Organization:	Grafik Software
Lines:	21
Message-ID:	<4p0l8u$u6d@news.manawatu.gen.nz>
References:	<16B71493F43 AT fs2 DOT mt DOT umist DOT ac DOT uk>
Reply-To:	malcolm AT manawatu DOT gen DOT nz
NNTP-Posting-Host:	malcolm.manawatu.gen.nz
Mime-Version:	1.0
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

"A.Appleyard" <A DOT APPLEYARD AT fs2 DOT mt DOT umist DOT ac DOT uk> wrote:

>  If I wrote a program MIAOW that had window effects, in 2 versions:-
>  MIAOW-D.EXE, running anywhere, containing the bodies of all subroutines
>needed to create Windows-like effects;
>  MIAOW-W.EXE, not needing to contain the bodies of those {subroutines needed
>to create Windows-like effects} that are in Windows as standard;
>  how much *.EXE filestore size is on average likely to be thereby saved in
>MIAOW-W.EXE?

Perhaps 100K, but then you'll have to bind resources for your dialogs
etc. to your windows exe which will take some space. It depends
entirely on the windowing library used. With TWS I find the simplest
applications to be of the order of 160K long whereas non-windowed
non-graphics app is around 70K. These are approximate figures, but do
show that it is not much. (I have other simple apps including graphics
that reach 110K). However TWS is a C++ class library that gives
Windows like features, it cannot substitute for Windows directly.

Malcolm

- Raw text -