Unix-head needs to Windows-ize his Python script (II)
Lawrence D'Oliveiro
ldo at geek-central.gen.new_zealand
Tue Oct 26 20:46:28 EDT 2010
In message <mailman.265.1288113240.2218.python-list at python.org>, Dennis Lee
Bieber wrote:
> (The Amiga made it simple -- a shell invocation received a non-zero
> argc, with command line parameters in argv; a "clicked" invocation
> received argc of 0, and argv pointed to a structure containing the
> information from the associated .info file [Workbench only displayed
> icons from .info files, unlike Windows displaying everything]).
Why would you want both CLI and GUI functions in one program? The *nix
philosophy is that a program should do one thing, and do it well.
That means a command-line tool should concentrate on being a good command-
line tool. For users who want to access that functionality through a GUI,
you build a GUI front end which makes use of that tool, and possibly others
as well, at the back end.
That way, you end up with a minimum of complexity and duplication of
functionality, and a maximum of flexibility and power.
More information about the Python-list
mailing list