<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<title></title>
</head>
<body bgcolor="#ffffff" text="#000000">
On 2011-04-18 23:47, Paul A Norman wrote:<br>
<blockquote
cite="mid:BANLkTinp1270qsjkD4GpT=+R9j_eaRH4xw@mail.gmail.com"
type="cite">
<div class="gmail_quote">If it looks like a duck, walks like a
duck, quacks like a duck, its probably a duck.
<div>On Windows at least, with their Qt shading, this component
look more like a button than anything else.</div>
</div>
</blockquote>
<br>
OK, seeing them as buttons that open menus/dialogs is
understandable. I'll see what I can do.<br>
<blockquote
cite="mid:BANLkTinp1270qsjkD4GpT=+R9j_eaRH4xw@mail.gmail.com"
type="cite">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">
<div class="im">
> I was looking<br>
> through <a moz-do-not-send="true"
href="http://code.google.com/p/texworks/source/list"
target="_blank">http://code.google.com/p/texworks/source/list</a>
trying to<br>
> identify what else there was to check...<br>
><br>
> Re-compression --<br>
><br>
> I noticed <a moz-do-not-send="true"
href="http://code.google.com/p/texworks/source/detail?r=763#"
target="_blank">http://code.google.com/p/texworks/source/detail?r=763#</a><br>
> Hasnlt helped us much yet, did another check on latest
exe ...<br>
<br>
</div>
Yeah, it was just a first attempt, I didn't have time to look
into this<br>
issue in detail yet. As far as (stable) releases are
concerned, I'd<br>
prefer to go with uncompressed files, as they don't change
that often<br>
(people don't have to download too much), hard disk space is
not that<br>
limitted anymore these days (we're talking about 21MB) and
speed is nice<br>
to have.</blockquote>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
0.8ex; border-left: 1px solid rgb(204, 204, 204);
padding-left: 1ex;">For "daily" testing builds, OTOH, I agree
that size matters,<br>
and speed does not so much. Still, I'd like to investigate
this first.<br>
<br>
</blockquote>
<div><br>
</div>
<div>Its worth it, there are still considerable numbers of
people in developing countries who rely on speeds little
better, or the same as dial up modems. I know one man in the
Philipines who has been unable to guarantee a connection for
ten minutes without it going down and requires reconnection,
and have seen people in Fiji even near main nodes, have to
wait over an hour to process a small raft of plain text
emails.</div>
</div>
</blockquote>
<br>
Of course. OTOH, the installer already is quite a bit smaller than
the archive, so it would be reasonable to download that if
speed/capacity is an issue. Just to check, could you run UPX on the
installer and see if it gets (significantly) smaller? (My guess is
no, but if I'm wrong I'll look into using UPX on the installer; on
the one hand, it's smaller to begin with, and on the other it is run
only once, so any startup lag is no problem).<br>
<br>
In the meantime, I've looked a little bit into the issue with the
main TeXworks.exe. It seems that Qt stores quite a lot of
information on properties, methods, UI, ... as plain text in the
.exe. This, naturally, can be compressed efficiently, yielding the
much smaller size you reported. However, the files to download are
compressed in a .zip archive. Therefore, I'd suspect that replacing
the TeXworks.exe in the .zip file by an UPX'ed one would make only a
minor difference. The .exe is smaller, but it won't be compressed
anymore by the zip algorithm (right now, the compressed size is
about 50% smaller than the uncompressed one). So, again, I would
suspect the difference between an UPX'ed version and a non-UPX'ed
one in a zip archive to be small (though non-zero, as I expect the
UPX algorithm to give somewhat better results than zip).<br>
<br>
Regards,<br>
Stefan<br>
</body>
</html>