> > Second point: how do I switch it off? I use KDE and many others do.
> > I may once implement writing native *.lnk files. We would need a point to
> > switch between this 3 choices.
> >
> > Third Point: since we likely going to have more code like this for window-
> > manager integration we night want to create special directorys for
> > kde and gnome.
> >
> > juergen
> >
>
> Actually, why not just write .lnk files only (exactly like Windows NT does). Have a
> "Start Menu\Programs" directory for each user (in the .wine directory would probably
> make the most sense) and also a global "Start Menu\Programs) maybe in something like
> /usr/share/wine. Of course this does mean that ~/.wine and /usr/share/wine will have
> to be available as Windows drive letters.
>
> Integration with GNOME, KDE, and [insert your desktop environment or bloated WM of
> choice here] could be provided by parsing the .lnk files. GNOME already has
> AnotherLevel, KDE, and Debian support. IIRC, KDE can read GNOME's menus. I would
> envision a "WINE programs" item.
>
> I assume we could provide a generic way of reading the .lnk files and provide it in
>an
> .so that could be used by the different desktops. The .so should be able to parse
>the
> .lnk and return the icon, the name of the menu, and the tooltip (Noticed that win2k
> has these). It should also have a function that will execute the program. It should
> simply run wine giving it the command line from the .lnk file.
>
> Questions/Comments ?
Sounds implementable without to much problems...
juergen
---
[EMAIL PROTECTED]
... from sunny Berlin
