Jeff Waugh (jeff.waugh_at_ubuntu.com) wrote:
The PowerPC version of the packages, however, is another issue.
Obviously, we can't make Wine work with i386-compiled apps on PPC,
(There's an awesome opportunity for qemu integration there...)
Yeah, that's something the folks at
http://darwine.opendarwi
> 1) Create a new Menu entry in the .menu file
> at /usr/share/gnome-app-install/applications.menu
/etc/xdg/menus/applications.menu, rather.
> This one will be named "Windows Applications" and will need to point to
> two locations for .desktop files: system-wide ones, and user-specific
> ones.
On Sat, 12 Mar 2005 18:09:52 -0800, Scott Ritchie wrote:
> We've talked about it on the Wine lists before, but there have been some
> difficulties. The first is that we don't yet understand how to read
> Windows shortcut files and interpret them: this can probably be overcome
> with some work.
R
One of the most commonly requested features for Wine is for Wine to be
aware of applications that put themselves into the Windows Start menu.
We've talked about it on the Wine lists before, but there have been some
difficulties. The first is that we don't yet understand how to read
Windows shortc
>I dont know if the "Desktop"
>option still exists in WINE but it would be nice to have ros-explorer
>when running WINE in desktop mode under Linux. The I could just run all
>of my Win32 apps from one place.
Yes, this is possible, just set explorer.exe to desktop mode in your config file
and run th
--- "Gregory M. Turner" <[EMAIL PROTECTED]> wrote:
> There is a certain logic to this arrangement imo... who wants some
> wacky
> "explorer.exe" if they are simply thumbing through the kde or gnome
> menus?
> Not that I disapprove of ros explorer, quite the contrary! ros
> explorer
> approxima
menus is already
merged into Wine. We just have a more extensive wineshelllink script
that deals with more corner cases.
Mike
Robert van Herk wrote:
Hi all,
As some of you might know I am working on a Wine Start menu, for Linux.
I have heard different things on this list about the way Wi
On Monday 13 October 2003 04:56 pm, Ivan Leo Murray-Smith wrote:
> There already is an app that can do the menus, the ros explorer. If it was
> compiled as a winelib app, it would solve the menu problem, at least for
> who likes desktop mode (And the ros explorer makes wine look like a "real"
> emu
Codeweavers has done a lot of work with shortcuts & menuitems, to make
them work with different distros... so they might know what some of
the nitty-gritty details are (Unfortunately, I do not).
Do you know if it is possible to recycle code from them? Since there
product seems to be commercial.
Robert van Herk <[EMAIL PROTECTED]> wrote:
>As some of you might know I am working on a Wine Start menu, for Linux.
>
>I have heard different things on this list about the way Windows treats
>the start menu.
>
>Some told me that it would be better to make a Windows (wine)
There already is an app that can do the menus, the ros explorer. If it was
compiled as a winelib app, it would solve the menu problem, at least for who
likes desktop mode (And the ros explorer makes wine look like a "real" emulator)
That is not to say that a rational cost/bene analysis will not ultimately
favor a pure-linux implementation, depending on where your code is going
but my bias would be towards a wine/winelib implementation. Do you forsee
this code going into wine or into kde/gnome, or remaining as a separa
On Monday 13 October 2003 01:46 pm, Robert van Herk wrote:
> So, my question is: would it be enough to create just a Linux program
> that synchronizes with this directory? Can anyone give me an example of
> a lnk file that IS actually missing in a Start Menu directory, but is
> there in his Program
Hi all,
As some of you might know I am working on a Wine Start menu, for Linux.
I have heard different things on this list about the way Windows treats
the start menu.
Some told me that it would be better to make a Windows (wine) client
that reads the actual start menu by querying a Wine dll
14 matches
Mail list logo
