--- Troy Rollo <[EMAIL PROTECTED]> wrote: > On Fri, 6 May 2005 09:10, James Hawkins wrote: > > wine wasn't designed to accept unix paths in the apis directly or to > > display them in open file dialogs, > > Linux wasn't designed to run Windows applications either - these things are > subject to change. >
Yes, and Windows applications wasn't designed to 'see' Unix paths, whether developed on Windows (like WinZip) or on Linux (winemine). > > This just adds complexity to an already complex beast. Keep it simple. > > If it's too complex for *you* then nobody's asking *you* to implement it. > It's > needed for some uses of WINE, and we have at least one corporate developer > and one individual developer who are willing to implement it. This pretty > much guarantees something will be implemented whether it's beyond your > capabilities or not. The only real question is what is the best *way* to > implement it. > Uh... it's getting hotter here... "... one corporate developer ..." hm... ;) *If* we're at the very least worried about not having an existing z: drive (like with winecfg), I suggest we make z: a default drive for / (or is it already implemented??) So if there's already an existing z: symlink in ~/.wine/dosdevices, we use that, otherwise imply z: -> / William Poetra Yoga Hadisoeseno Discover Yahoo! Stay in touch with email, IM, photo sharing and more. Check it out! http://discover.yahoo.com/stayintouch.html