-----BEGIN PGP SIGNED MESSAGE-----
On Thu, 16 May 2002 00:10:35 -0400,
>> With repsect, why not just make a GUI frontend to md5sum ? way smaller
>> than 60K and leverages existing code. I'd recommend Python and [QT or
>> Tkinter, or WxWindows].
>> Jim Richardson
>> Anarchist, pagan and proud of it
>> Linux, from watches to supercomputers, for grandmas and geeks.
> The point you are making comes up in various forms in all software. The
> question is, do you want to count on shared resources or do you want to have
> everything "stand alone".
> For small utilities, my gut feeling is to make everything stand alone. That
> is, a small utility should not count on .DLLs or other executables on the
> system. That way, a person can just throw the utility on a floppy and use
> it on another system without worrying about whether MD5SUM is there already.
> So, for simplicity, I would tend to accomplish code re-use by having
> everything build from the same set of source files, rather than by .DLLs or
> front ends.
> There are pros and cons to this, naturally.
Obviously depends on each individual case, but in this case (md5sum) I'd
say that it's prevelent enough that any system (Linux anyway) is likely
to have it. Anyway, unless you plan on statically linking everything,
you will have some dependencies anyway (glibc and whatever your gui
library is for two)
In the case of md5sum, there are only 3 options I can see. It would
seem to be an ideal case for a gui front end.
Look at programs like Grip, XCDroast and others, they are good examples
of the code reuse feature of dynamic linking, and of seperating backend
from GUI (or TUI for that matter) frontend.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)
-----END PGP SIGNATURE-----
Anarchist, pagan and proud of it
Linux, from watches to supercomputers, for grandmas and geeks.