>From: [EMAIL PROTECTED] on behalf of Vincent Povirk
>On 8/9/07, Misha Koshelev <[EMAIL PROTECTED]> wrote:
>
>> still be able to start both). Using this approach would also solve any
>> problems with wine's start not necessarily having the appropriate
>> command line parameter support. I am startin
On 8/9/07, Misha Koshelev <[EMAIL PROTECTED]> wrote:
> still be able to start both). Using this approach would also solve any
> problems with wine's start not necessarily having the appropriate
> command line parameter support. I am starting to like/favor the
> install-time association approach.
On Thu, 2007-08-09 at 13:24 +0200, Stefan Dösinger wrote:
> Another drawback of using a general "wine start" to call the windows apps is
> that we sacrifice a bit of desktop integration. It would be cool if the Linux
> mime type generated from the wine registry contained the application's name
>
> You will have to forgive my ignorance but I guess my other concern would
> be is there even a way for GNOME to handle such verbs at the moment? I
> was looking at
> http://www.freedesktop.org/wiki/Specifications/mime-actions-spec
> and it seems like there is plans for this but, at least according
On Wed, 2007-08-08 at 21:59 -0400, Vincent Povirk wrote:
> Wine start is not quite what I had in mind. Each file type can have
> multiple "verbs" (such as open, edit, print..), and I'd like GNOME to
> give me the option to use any of the verbs that are available. Wine
> start is apparently hard-cod
Wine start is not quite what I had in mind. Each file type can have
multiple "verbs" (such as open, edit, print..), and I'd like GNOME to
give me the option to use any of the verbs that are available. Wine
start is apparently hard-coded to use the "open" verb.
That may mean it's simple to modify i
> To register those verbs for Linux desktops, some sort of command-line
> wrapper around ShellExecute would be needed. I think this is a good
> idea anyway. Does Windows have anything like that? Is it worth it for
> me to try writing something like that based on winelib?
Well this is exactly the st
On 8/8/07, Vincent Povirk <[EMAIL PROTECTED]> wrote:
> As it is right now, we have a filetype/association system in Wine's
> registry, and we have a completely separate one in most Linux
> desktops. They do not talk to each other. Wine's system relies
> primarily on extensions because that's what W
This was something I thought we wanted for wine for a long time, but I
can't find any literature suggesting that's the case. So I'll just
explain it here.
As it is right now, we have a filetype/association system in Wine's
registry, and we have a completely separate one in most Linux
desktops. The
