Hello,
William Poetra Yoga H wrote:
That's the beauty of it! wineprefixcreate sets z: to point to /
automatically. Of course the user can always change what z: points
to, but / is the default location.
What I mean is, z: -> / is implied in the source. So even without a z:
symlink,
the z: drive w
James Hawkins wrote:
On 5/5/05, Troy Rollo <[EMAIL PROTECTED]> wrote:
Precisely. WINE is not just for running apps compiled for Windows - it's also
for making the Windows API available under UNIX. For this second application,
users need to (at a minimum) be seeing UNIX paths (and not Windows paths
--- "Dimitrie O. Paun" <[EMAIL PROTECTED]> wrote:
> James, if an application informs us somehow (TBD) that they
> can handle Unix paths, there's no reason to force the silly
> drive letters on Unix users. Ideally we would even hide the
> drive letter combo box in the file dialogs.
>
Well, maybe
On Fri, May 06, 2005 at 02:12:22AM -0500, James Hawkins wrote:
> That's the beauty of it! wineprefixcreate sets z: to point to /
> automatically. Of course the user can always change what z: points
> to, but / is the default location.
James, if an application informs us somehow (TBD) that they
c
Troy Rollo wrote:
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 whe
--- James Hawkins <[EMAIL PROTECTED]> wrote:
> On 5/6/05, William Poetra Yoga H <[EMAIL PROTECTED]> wrote:
> >
> > *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
On 5/6/05, William Poetra Yoga H <[EMAIL PROTECTED]> wrote:
>
> --- 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 desi
--- 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
On 5/5/05, Troy Rollo <[EMAIL PROTECTED]> wrote:
>
> Linux wasn't designed to run Windows applications either - these things are
> subject to change.
>
By this argument we should have changed linux itself to run windows
programs. If things are subject to change, like creating wine on top
of linu
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.
> and that's why we have virtual
> drives.
N
On 5/5/05, Troy Rollo <[EMAIL PROTECTED]> wrote:
>
> Precisely. WINE is not just for running apps compiled for Windows - it's also
> for making the Windows API available under UNIX. For this second application,
> users need to (at a minimum) be seeing UNIX paths (and not Windows paths at
> all) in
On Thu, 5 May 2005 19:42, Francois Gouget wrote:
> I believe the rationale is to provide a better integration with the Unix
> environment> Some ISV, e.g. Borland, ports their popular
> application, e.g. Kylix, to
> Linux using Wine and/or Winelib. With Wine as it stands, their 'Unix'
> applica
On Thu, 05 May 2005 08:51:44 +0200, Paul van Schayck <[EMAIL PROTECTED]>
wrote:
This extension will become even more valuable because we want winecfg
(or wine in particular) to start without having any virtual drive.
People might have removed all drives (with winecfg).
Isnt that like trying to s
Hi Michael,
On Thursday 05 May 2005 03:06, Michael Lin wrote:
> I know you are working on this area as well, so maybe we should coordinate
> our effort so that there is no duplicate work.
I do have a couple of patches, which are not yet ready to be send to
wine-patches. I will finish them up and
Hi,
The stuff, which is implemented in shell32/shfldr_unixfs.c is what Microsoft
calls a "shell namespace extension". This is used quite often on Windows, for
example to access some non USB-mass-storage based digital cameras via the
shell. We use this extension in winecfg to map drive letters t
On Thu, 5 May 2005, James Hawkins wrote:
[...]
You can't type in a unix file path in
windows, so I don't see why we should allow it in wine. That is what
the virtual drives are for.
I believe the rationale is to provide a better integration with the Unix
environment. Here's the scenario where I s
--- Paul van Schayck <[EMAIL PROTECTED]> wrote:
> We do need this for winecfg. If you want to setup virtual drive you do
> want to see the full unix fs. Winecfg needs to have to unix paths.
> Putting conversion code in winecfg was not really acceptable, an
> extension to was.
>
> This extension w
On 5/5/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> I agree. I would have thought the over-riding principal is to keep
> functionalily as close as possible to windows behaviour to provide the
> closest compatability possible, not to start adding "extentions".
>
> If we need to regularly acce
On Thu, 05 May 2005 08:06:40 +0200, James Hawkins <[EMAIL PROTECTED]>
wrote:
You can't type in a unix file path in
windows, so I don't see why we should allow it in wine. That is what
the virtual drives are for.
I agree. I would have thought the over-riding principal is to keep
functionalily
On 5/4/05, Michael Lin <[EMAIL PROTECTED]> wrote:
>
> I know there will be issues of Windows APIs won't accept unix file path.
> But at this point, I just want to extend open file dialog optionally accept
> and
> return a unix file path.
>
> The flag to turn unix path on or off can be in the regi
Hi Michael, > Oops, as you see I'm undecided ;) (Anyway, this probably
should be GNU ;)
However, in the final version I would like this to appear not at all in the
shell namespace, anyway. I think it would be nice if the '/' appears beside
the wine drive letters under 'My Computer'.
I have be
On Wednesday 27 April 2005 10:01, Andreas Mohr wrote:
> Now what? Is it UNIX or Unix?
Oops, as you see I'm undecided ;) (Anyway, this probably should be GNU ;)
However, in the final version I would like this to appear not at all in the
shell namespace, anyway. I think it would be nice if the '/'
Hi,
nice!
> [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Explorer\Desktop\Namespace\{CC702EB2-7DC5-11D9-C687-0004238A01CD}]
> @="My Unix Filesystem"
>
> [HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\ShellExtensions]
>
> [HKEY_LOCAL_MACHINE\Software\Microsoft\Win
If you apply the attached patch and import the attached registry file (which
registers a junction point for the unixfs shell namespace extension), you can
select and open files from the unix filesystem in notepad (The file has to be
accessible by a drive letter based wine path though).
In retr
24 matches
Mail list logo
