SoC proposal: shell integration

Mikołaj Zalewski mikolaj at
Sun May 7 13:13:12 CDT 2006

Segin wrote:

> If this was to be done, there are a few things I suggest:
> First should be everything that has laid out, and 
> nothing more. That does into the integration code. For a lot of 
> this to work, Wine may have to be ran as a system service (is that 
> even a good idea?). 

  I don't know what you mean by a system service but there will be no 
need for a new kind of processes. The Trash code can run in the client's 
process. Checking the Start Menu and HKEY_CLASSES_ROOT needs to be done 
in a separate process/thread and but as I see the wine explorer is used 
for such tasks. No privileges are required as the code can create the 
menu items/MIME entries in the home directory (and it is probably the 
desired way as by default wine is installed in each home directory for 
the current user only).

> Each part of the integration profiles that is Wine-specific code 
> should be done like the audio drivers, a Wine or similar. 
> for Freedesktop, for KDE 3, 
> for generic KDE (stuff that works on both 3 and 4), 
> and so on.

  I was thinking about COM interfaces. Then the code would be in regular 
DLLs with no need for a special infrastructure. The shell32_unix.dll 
from my proposal was what you call, the 
shell32_kde.dll is the etc.

Mikolaj Zalewski

More information about the wine-devel mailing list