Reply to thread

Message

<blockquote data-quote="Haravikk" data-source="post: 1042366" data-attributes="member: 51625">Okay, so I went ahead and made something myself. All you have to do is open a new Automator application workflow, throw in a shell-script task, and copy/paste the following code:[code]source ~/.profileif test $# = 0&nbsp; &nbsp; then&nbsp; &nbsp; &nbsp; &nbsp; winefile C:&nbsp; &nbsp; &nbsp; &nbsp; exitfifor f in &quot;$@&quot;do&nbsp; &nbsp; d=`dirname &quot;$f&quot;`&nbsp; &nbsp; f=`basename &quot;$f&quot;`&nbsp; &nbsp; cd &quot;$d&quot;&nbsp; &nbsp; wine &quot;$f&quot; &amp;done[/code]You can then save your app, associate .exe files with it (using Finder's get-info), and WINE should run with very little fuss as you can now just double-click .exe files, create aliases to your favourite ones etc.If you open the app without a .exe argument then you get the default file-browser. You can also go a step further and associate files in the info.plist within the .app, and provide icons and so-on as well, but I won't describe that here.</blockquote>

[QUOTE="Haravikk, post: 1042366, member: 51625"] Okay, so I went ahead and made something myself. All you have to do is open a new Automator application workflow, throw in a shell-script task, and copy/paste the following code: [code]source ~/.profile if test $# = 0 then winefile C: exit fi for f in "$@" do d=`dirname "$f"` f=`basename "$f"` cd "$d" wine "$f" & done[/code] You can then save your app, associate .exe files with it (using Finder's get-info), and WINE should run with very little fuss as you can now just double-click .exe files, create aliases to your favourite ones etc. If you open the app without a .exe argument then you get the default file-browser. You can also go a step further and associate files in the info.plist within the .app, and provide icons and so-on as well, but I won't describe that here. [/QUOTE]

Verification

Name this item. 🍎