Re: Wine FAQ edits
On Thu, Feb 3, 2011 at 18:17, Albert Lee tr...@forkgnu.org wrote:
The instructions were intended to give some context for users who
might not be familiar with the ~ expansion.
Using {$HOME} would be more portable. The Bourne shell (/bin/sh) on
Solaris (9/10 - OpenSolaris defaulted to ksh) doesn't support ~
(although csh, zsh, bash, tcsh, ksh and just about all the other
bundled shells does, it sh is the default shell)
(Checkin proper quoting in case it contains spaces might be necessary..)
Gert
Re: Wine FAQ edits
Correction:
${HOME}
Re: Wine FAQ edits
On Sat, Feb 5, 2011 at 10:05, Gert van den Berg wine-de...@mohag.net wrote:
On Thu, Feb 3, 2011 at 18:17, Albert Lee tr...@forkgnu.org wrote:
The instructions were intended to give some context for users who
might not be familiar with the ~ expansion.
Using {$HOME} would be more portable.
And using ${WINEPREFIX:-${HOME}/.wine}/dosdevices/c:/Program Files
should work correctly in any Wine setup (on a Bourne-compatible
shell), including one using a custom WINEPREFIX. (But might be
somewhat hard to follow for someone not familiar with the
technicalities of the Bourne shell)
Re: Pulling Patch
On 02/04/2011 07:13 PM, James McKenzie wrote: Since my Mac is dying I have decided to return to the Windows world. It's your choice so I can't comment it but I bet you know what I think. Please remember what you wrote to me (May, 2010) : Don't give up on it, just take a break away from it, please. The solution might just come to you while you are working on something else. I've been working on a patch for two years and the implementation was completely wrong. I will go back to it in about a month, and actually fix two missing functions rather than one. This was the benefit of a mandatory break insisted upon by Alexandre. He does not want me to touch it until early October. That's fine. Just don't let this get you into a negative spirial. Alexandre and others have very good advice. Please pull any and all patches. I have envoked the right to copyright and none of my code can or will be used in Wine. Life's hard, unfair and never goes as we thought. Does it worth the fight ? Yeah, of course ! Just as you told me, don't give up and have a break, have a K*t K*t. Every mail and patch you sent is now archived and may be referred when relevant. I'm sure you did great things and whatever you think, you're part of Wine. We don't often say good job ! because it often imply something in return (mostly money) but we should. It's always pleasant to see our work useful and that makes us proud. So Good job !, have a nice day and take care.
Re: Killing WineAPI project on SourceForge.
Am 05.02.2011 06:36, schrieb Max TenEyck Woodbury: No feedback and apparently no interest in the WineAPI project on SourceForge. Understandable since there is now a WineAPI on the regular Wine Wiki. Unless someone objects, I'm going to ask that it be shutdown on SourceForge. Which WineAPI on the regular Wine Wiki??? URL? -- Best Regards, André Hentschel
Re: user32: Don't try to move mouse to (-1,0).
Hi, While running your changed tests on Windows, I think I found new failures. Being a bot and all I'm not very good at pattern recognition, so I might be wrong, but could you please double-check? Full results can be found at http://testbot.winehq.org/JobDetails.pl?Key=8925 Your paranoid android. === W7PROX64 (64 bit msg) === Timeout
Re: Killing WineAPI project on SourceForge.
On 02/05/2011 06:36 AM, Max TenEyck Woodbury wrote: No feedback and apparently no interest in the WineAPI project on SourceForge. The subject has been debated before you launched the WineAPI project on SF. Some questions may help to understand why does nobody is interested : + Why a WineAPI should be needed ? + Who would use it ? + What can people using it expect to see ? Understandable since there is now a WineAPI on the regular Wine Wiki. On 02/05/2011 02:59 PM, André Hentschel wrote: Which WineAPI on the regular Wine Wiki??? URL? I guess he's talking about this http://source.winehq.org/WineAPI/ It says generated automatically but where is the script ? Max, if you want, you can still improve the script and make it more useful. For instance, instead of Statistics which give simple numbers, I think a link to each function in the wine source code should be great. I have some ideas like adding a search feature, a link to the test that implement the selected function ..etc It may be useful when you want modify a function but you don't know where it is. For instance, wine_dbgstr_w() is used everywhere. But where is it defined ? It should be a usage of the WineAPI but that's only my point of view. Hope that helps !
Re: Wine FAQ edits
On Sat, Feb 05, 2011 at 10:14:07AM +0200, Gert van den Berg wrote:
On Sat, Feb 5, 2011 at 10:05, Gert van den Berg wine-de...@mohag.net wrote:
On Thu, Feb 3, 2011 at 18:17, Albert Lee tr...@forkgnu.org wrote:
The instructions were intended to give some context for users who
might not be familiar with the ~ expansion.
Using {$HOME} would be more portable.
And using ${WINEPREFIX:-${HOME}/.wine}/dosdevices/c:/Program Files
should work correctly in any Wine setup (on a Bourne-compatible
shell), including one using a custom WINEPREFIX.
Better still ${WINEPREFIX:-${HOME:?}/.wine}/dosdevices/c:/Program Files
which will generate an error if HOME isn't set.
David
--
David Laight: da...@l8s.co.uk
Re: Killing WineAPI project on SourceForge.
On Sat, 5 Feb 2011, GOUJON Alexandre wrote: On 02/05/2011 02:59 PM, André Hentschel wrote: Which WineAPI on the regular Wine Wiki??? URL? I guess he's talking about this http://source.winehq.org/WineAPI/ It says generated automatically but where is the script ? Max, if you want, you can still improve the script and make it more useful. For instance, instead of Statistics which give simple numbers, I think a link to each function in the wine source code should be great. I have some ideas like adding a search feature, a link to the test that implement the selected function ..etc It may be useful when you want modify a function but you don't know where it is. For instance, wine_dbgstr_w() is used everywhere. But where is it defined ? It should be a usage of the WineAPI but that's only my point of view. I've seen this discussion come and go a few times... Would something like LXR be appropriate for generating a web front-end to searching and indexing the Wine source code? I've used the various Linux kernel sites a time or two: http://sourceforge.net/projects/lxr/ Steve Brown sbro...@umbc.edu
Re: Killing WineAPI project on SourceForge.
On 02/05/2011 08:59 AM, André Hentschel wrote: Am 05.02.2011 06:36, schrieb Max TenEyck Woodbury: No feedback and apparently no interest in the WineAPI project on SourceForge. Understandable since there is now a WineAPI on the regular Wine Wiki. Unless someone objects, I'm going to ask that it be shutdown on SourceForge. Which WineAPI on the regular Wine Wiki??? URL? Sorry, not Wiki. http://source.winehq.org/WineAPI/ Max
Re: Pulling Patch
On 05/02/11 00:24, James McKenzie wrote: Actually, the latest patch is what I don't want reused. And no, you don't put it in the LGPL until it is committed, which I don't expect AJ to do anyway. However, I'm moving in a different direction since my Mac needs more repairs than I'm willing to spend money on. Besides, I've been a big enough pain that my existence here is unwarranted and unneeded. As anyone who attended the last WineConf probably already knows, you have my complete sympathies in that regard. I also doubt very much anyone would use your uncommitted patches against your will, so in that respect, you probably have nothing to worry about. That said, I believe your claim to the right to demand no use is wrong. It is my understanding that by submitting your patches to wine-patches, you have placed them under the LGPL, which is a non-revocable license. Again, in all likely hood, this is a purely hypothetical question. Shachar -- Shachar Shemesh Lingnu Open Source Consulting Ltd. http://www.lingnu.com
Re: Killing WineAPI project on SourceForge.
On 02/05/2011 10:38 AM, Steve Brown wrote: On Sat, 5 Feb 2011, GOUJON Alexandre wrote: On 02/05/2011 02:59 PM, André Hentschel wrote: Which WineAPI on the regular Wine Wiki??? URL? I guess he's talking about this http://source.winehq.org/WineAPI/ It says generated automatically but where is the script ? Max, if you want, you can still improve the script and make it more useful. For instance, instead of Statistics which give simple numbers, I think a link to each function in the wine source code should be great. I have some ideas like adding a search feature, a link to the test that implement the selected function ..etc It may be useful when you want modify a function but you don't know where it is. For instance, wine_dbgstr_w() is used everywhere. But where is it defined ? It should be a usage of the WineAPI but that's only my point of view. I've seen this discussion come and go a few times... Would something like LXR be appropriate for generating a web front-end to searching and indexing the Wine source code? I've used the various Linux kernel sites a time or two: http://sourceforge.net/projects/lxr/ Steve Brown sbro...@umbc.edu Script is 'tools/c2man.pl'. There are several things in it that need improvement. See my other thread from yesterday. Max
RE: shell32/tests: Clean make new folder test (Valgrind)
Hi! What is the reason this patch by Nikolay Sivov was not included in the latest version of wine? It fixes a clean-up bug on some Windows XP machines, and tidies up the code nicely. Wine-patches archive link: http://www.winehq.org/pipermail/wine-patches/2011-January/098342.html Regards, Michael Mc Donnell P.S. Thanks Nikolay for fixing my first win32 test.
Re: Wine FAQ edits
On Sat, Feb 5, 2011 at 3:05 AM, Gert van den Berg wine-de...@mohag.net wrote:
On Thu, Feb 3, 2011 at 18:17, Albert Lee tr...@forkgnu.org wrote:
The instructions were intended to give some context for users who
might not be familiar with the ~ expansion.
Using {$HOME} would be more portable. The Bourne shell (/bin/sh) on
Solaris (9/10 - OpenSolaris defaulted to ksh) doesn't support ~
(although csh, zsh, bash, tcsh, ksh and just about all the other
bundled shells does, it sh is the default shell)
Anyone using the original Bourne sh *interactively* is in for a world
of pain anyway (speaking as someone who often had to before the ksh93
replacement). I think relying on tilde expansion can can be considered
good practice for the interactive use case.
-Albert
Re: Wine FAQ edits
On Thu, Feb 3, 2011 at 9:49 PM, Vitaliy Margolen wine-de...@kievinfo.com wrote: On 02/03/2011 09:17 AM, Albert Lee wrote: The instructions were intended to give some context for users who might not be familiar with the ~ expansion. Then mention that if you must. ~ is used in number of other places in FAQ, and all over the net. Please keep it simple. I will add that, since we're not properly explaining it currently. It's a fairly trivial one-liner as it is Which will blow away most windows users who have no concept of expansions and redirections. You not writing developer's guide, you writing FAQ for clueless windows users who want Wine do what they need. The existing implementation is not exactly transparent to new users either, and we're not attempting to explain in detail how it works. Instead, I am suggesting reducing the complexity of the solution, which also reduces the work for the user. -Albert
Re: Wine FAQ edits
On 02/05/2011 07:54 PM, Albert Lee wrote: Instead, I am suggesting reducing the complexity of the solution, Multiple expansions, redirections and use of xargs is hardly a simplification of a script with 2 parameters. Again, we are not talking about advanced skills here. We talking about users who do not understand what expansion, redirection are. Let alone xargs. In either case please don't add such complex scripts into FAQ. Keep it simple. Vitaliy.
Re: user32: Don't try to move mouse to (-1,0).
On 02/05/2011 07:10 AM, Jacek Caban wrote: This trigers screen edge action on KDE, which is 'Present Windows' in default configuration. mouse_event() generates relative mouse movement events unless MOUSEEVENTF_ABSOLUTE is specified. If you don't want a pointer to get near the edge then you should use SetCursorPos() instead. Vitaliy.
