Well, this should handle most all file types. What is winecfg written in? I'd be happy to work with the source, but I'm a java guy, so I might be spinning my wheels.<br><br>The URIs/URLs may be a bit tougher to wrap up.<br>
<br>As far as going in the other direction, simply using "wine start /path/to/file" in theory would launch wine's default app for that association. Should be a one-liner.<br><br>-Tres<br><br><div class="gmail_quote">
On Wed, Jan 30, 2008 at 9:56 PM, Dave M <<a href="mailto:DaveM@mich.com">DaveM@mich.com</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have been thinking that this sort of thing should be part of wineconfig.<br>
Windows allows users to define what applications should open what documents<br>
and so should wine. But wine should also have the added benefit of allowing<br>
a choice of native or windows apps to be used. It was a major pain getting<br>
my windows apps to launch native firefox when links are clicked. It would<br>
be nice if this was built into wine.<br>
<br>
Just my $.02<br>
<br>
Dave<br>
<div class="Ih2E3d"><br>
At 04:54 PM 1/30/2008 , Tres wrote:<br>
>Updates:<br>
><br>
>I renamed the shell script "winelaunch" to "winenative" to avoid confusion<br>
>with the "winelauncher" binary.<br>
><br>
>It will need some work to dynamically use switches, like "-p" for printing<br>
>etc. Any basic shell scripter could prob help me out with that one. Let<br>
>me know if you can help.<br>
><br>
>I've modified the native call to simply call on "gnome-open". It<br>
>seamlessly opens any file you want natively. I'd like to include samples<br>
>for kde, xfce, etc (or determine dynamically if that's a possibility).<br>
><br>
>I've attached two files. "word.reg" is a sample registry file. Save it<br>
>to your desktop and do an import on it. Please note, the "-p" portion<br>
>won't work until the switches are sorted out, but won't do any harm.<br>
> #> regedit /home/username/Desktop/word.reg<br>
><br>
>The second file is the "winenative" shell script. Save it to your<br>
>desktop, copy it to /usr/bin, and make it executable:<br>
> #> sudo cp /home/username/Desktop/winenative /usr/bin/<br>
> #> sudo chmod +x /usr/bin/winenative<br>
><br>
>Then try to open a word document with your windows application.<br>
><br>
>-Tres<br>
><br>
>On Wed, Jan 30, 2008 at 7:40 AM, A. Tres Finocchiaro<br>
</div><div><div></div><div class="Wj3C7c">><<mailto:<a href="mailto:tres.finocchiaro@gmail.com">tres.finocchiaro@gmail.com</a>><a href="mailto:tres.finocchiaro@gmail.com">tres.finocchiaro@gmail.com</a>> wrote:<br>
>>My first post.<br>
>><br>
>>Fun Wine Project -- Configure Some Default Registry Entries<br>
>><br>
>>I've begun working on this to import some native calls into wine. More<br>
>>specifically, OpenOffice.org. I'm trying to get Lotus Notes attachments<br>
>>to display proper icons, and open natively with OOo.<br>
>><br>
>>I've come across a dilemma. I can't seem to "easily" open a Windows path,<br>
>>i.e. "C:\Windows\temp\test.doc" with openoffice due to path issues.<br>
>><br>
>>I've implemented a very small fix called "winelaunch", but I'm afraid the<br>
>>name is too close to "winelauncher", and would probably confuse<br>
>>people. Here's it's code:<br>
>><br>
>> #!/bin/sh<br>
>> #/usr/bin/winelaunch<br>
>> $1 `winepath $2 $3`;<br>
>> exit 1;<br>
>><br>
>>And here's a sample registry entry:<br>
>><br>
>> REGEDIT4<br>
>><br>
>> [HKEY_CLASSES_ROOT\.doc]<br>
>> @="docfile"<br>
>> "Content Type"="application/ooowriter"<br>
>><br>
>> [HKEY_CLASSES_ROOT\docfile]<br>
>><br>
>> [HKEY_CLASSES_ROOT\docfile\shell]<br>
>><br>
>> [HKEY_CLASSES_ROOT\docfile\shell\open]<br>
>><br>
>> [HKEY_CLASSES_ROOT\docfile\shell\open\command]<br>
>> @="/usr/bin/winelaunch /usr/bin/openoffice %1"<br>
>><br>
>>Although icons don't display properly, it does open the attachment in<br>
>>Lotus Notes.<br>
>><br>
>>Cheers.<br>
>><br>
>>-Tres<br>
>>--<br>
</div></div>>>- <mailto:<a href="mailto:Tres.Finocchiaro@gmail.com">Tres.Finocchiaro@gmail.com</a>><a href="mailto:Tres.Finocchiaro@gmail.com">Tres.Finocchiaro@gmail.com</a><br>
><br>
><br>
><br>
>--<br>
>- <mailto:<a href="mailto:Tres.Finocchiaro@gmail.com">Tres.Finocchiaro@gmail.com</a>><a href="mailto:Tres.Finocchiaro@gmail.com">Tres.Finocchiaro@gmail.com</a><br>
>Content-Type: application/octet-stream; name=winenative<br>
>X-Attachment-Id: f_fc34i45k0<br>
>Content-Disposition: attachment; filename=winenative<br>
><br>
>Content-Type: application/octet-stream; name=word.reg<br>
>X-Attachment-Id: f_fc34iilb1<br>
>Content-Disposition: attachment; filename=word.reg<br>
><br>
>_______________________________________________<br>
>wine-users mailing list<br>
><a href="mailto:wine-users@winehq.org">wine-users@winehq.org</a><br>
><a href="http://www.winehq.org/mailman/listinfo/wine-users" target="_blank">http://www.winehq.org/mailman/listinfo/wine-users</a><br>
<br>
-------------------------------<br>
Dave M<br>
Davem (at) Mich (dot) Com<br>
Ann Arbor, Mich. USA<br>
<br>
First Sale doctrine under attack, libraries at risk:<br>
<br>
<a href="http://www.eff.org/deeplinks/archives/005400.php" target="_blank">http://www.eff.org/deeplinks/archives/005400.php</a><br>
<br>
<br>
_______________________________________________<br>
wine-users mailing list<br>
<a href="mailto:wine-users@winehq.org">wine-users@winehq.org</a><br>
<a href="http://www.winehq.org/mailman/listinfo/wine-users" target="_blank">http://www.winehq.org/mailman/listinfo/wine-users</a><br>
</blockquote></div><br><br clear="all"><br>-- <br>- <a href="mailto:Tres.Finocchiaro@gmail.com">Tres.Finocchiaro@gmail.com</a>