<html><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On Oct 29, 2009, at 1:00 PM, Iain Barnett wrote:</div><div><br class="Apple-interchange-newline"><blockquote type="cite"><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "> <div>On 29 Oct 2009, at 15:41, Gregory Crosswhite wrote:</div><blockquote type="cite"><div style="margin-top: 0px; margin-right: 0px; margin-bottom: 0px; margin-left: 0px; "><font face="Helvetica" size="3" style="font: normal normal normal 12px/normal Helvetica; ">You don't have to turn a program into an application in order to make the GUI work</font></div><div><br></div></blockquote><div><br class="webkit-block-placeholder"></div>This is true, but I don't think it's better to import extra code where simple packaging (folders and a plist), which is actually very convenient, can do the job.<br></div></blockquote></div><br><div><br></div><div><div>It depends on what you are doing. I completely concur that in many (and perhaps most) cases your script is ideal, especially when one is packaging a program for distribution. However, although your packaging makes it easier to run the binary from the Finder, it makes it less convenient to run it from the command line, and in cases where for whatever reason you want to easily run it from the command line (which I have run into in practice) the EnableGUI module is very helpful.</div><div><br></div><div>Cheers,</div><div>Greg</div><div><br></div><div></div></div></body></html>