[winemenubuilder] shell:SHELL32_DllCanUnloadNow (void): stub, WinMain failed

Luca Capello luca at pca.it
Wed Jun 9 07:58:20 CDT 2004

Hash: SHA1

Hi again, Mike!

on 06/09/2004 01:02 PM, Mike Hearn wrote:
> Current Gnome implements an older version of the spec. They are moving to
> the latest version. The older version really did not work too well for
> Wines needs - in fact, this is one of the reasons the new version was
> developed. You'll see fgouget at codeweavers.com on the credits for the spec.
Yep, I saw ;-)

Ok, now the first step: Wine application can't be divided into single
categories, as you can't know from the application what does. I mean,
when you launch 'wine ./setup.exe' you can't know if this 'setup.exe' is
for an image editor or a wordprocessor and so on. So, we need to choose
for a general category which will be applied to all 'Wine' applications.
- From the given categories [1], IMHO the only suitable could be:
	--- Emulator ---
	Emulator of another platform, such as a DOS emulator

But, setting 'Adobe Photoshop 7.0' menu entry as an 'Emulator', it seems
so strange at my eyes. So, IMHO, the best solution will be a totally new
categories (called 'win32' or whatever we choose) in order to identify
'Wine' applications.

Before writing to the XDG mailing-list in order to have their opinion,
I'd like to know the WINE developers one, please.

> Well, Wine will run wineshelllink, AFAIK, which you can put anything you
> like in.
Wait, I didn't understand: ATM (so in the latest CVS) 'wine' doesn't
call 'winemenubuilder'. right? But it could be implemented if
'winemenubuilder' (which includes 'wineshelllink') works...

Thx, bye,
Gismo / Luca

Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org


More information about the wine-devel mailing list