Howdy,
I was looking at http://bugs.winehq.org/show_bug.cgi?id=23421, and
wanted to add a stub for it. Using winedump on a Windows 7 shlwapi.dll
gives different exports than Windows XP SP3 shlwapi.dll. Which dll
should the spec file be updated to match? I'm assuming the latest and
greatest, since eventually applications will head that direction.
An additional related question. Some of the functions that are
ordinals in previous Windows versions are now exported (e.g.,
ParseUrlA/W seems to have been documented/exported since Vista).
Should the spec file be adjusted to match the newer behavior?
I'm assuming this will have to wait until after 1.2 to be applied...
Thanks!
Austin
On 7/1/2010 02:20, Scott Ritchie wrote:
> Translation by Sven Augustin
> @@ -20,7 +21,12 @@ Name[sr]=Wine - аДаИаЗаАб� Windows аПб�аОаГб�аАаМаА
> Name[sr@latin]=Wine - diza� Windows programa
> Name[hr]=Wine - diza� Windows programa
> Exec=wine start /unix %f
> +<<<<<<< HEAD
> MimeType=application/x-ms-dos-executable;application/x-msi;application/x-win-lnk;application/x-ms-shortcut
> +=======
> +MimeType=application/x-ms-dos-executable;application/x-msi;application/x-win-lnk;
> +>>>>>>> tools/wine.desktop: add Icon=wine to support systems with an icon theme
> Icon=wine
> NoDisplay=true
> StartupNotify=true
> +
Conflicts?
Erich Hoover <ehoover(a)mines.edu> wrote:
>Sent: Jun 30, 2010 12:43 PM
>To: James Mckenzie <jjmckenzie51(a)earthlink.net>
>Cc: Alexandre Julliard <julliard(a)winehq.org>, Max TenEyck Woodbury <max(a)mtew.isa-geek.net>, wine-devel(a)winehq.org
>Subject: Re: (Resent) Documentation - Reference to MSDN?
>
>On Wed, Jun 30, 2010 at 1:36 PM, James Mckenzie
><jjmckenzie51(a)earthlink.net> wrote:
>> ...
>> How about some place on the Wiki along with an implementation status. That way we can also annotate items that are missing in MSDN (I just re-stumbled across something in my latest Richedit tests) as well. This would help greatly in our progress towards current and future implementations of the Windows API.
>>
>> And I agree, adding all of this to the source would make it unwieldy.
>>
>
>So something like "http://wiki.winehq.org/WineAPI/<DLL>/<Function>" ?
>If that's acceptable I would not mind a system like that, especially
>if the links of documented functions are provided in the source.
>Documenting these things is a lot of work, so I'm not about to run off
>and do all that work if no-one is ever going to take advantage of it.
>
+1
Acceptable variables should be listed in an order other than the one on MSDN. We don't want a direct copy, but rather OUR findings using the old 'black box' method.
James McKenzie
André Hentschel <nerv(a)dawncrow.de> wrote:
> This fixes bug 22862 which blocks bug 12804 (1.2)
> We already do a similar recursion in DEFDLG_FindDefButton and GetNextDlgGroupItem
>
> I didnt found any other changes in the tests... i expected some more "Test succeeded inside todo block"
You need to add explicit tests for GetDlgItem() inside of user32/tests.
--
Dmitry.
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=3023
Your paranoid android.
=== W7PRO (32 bit msg) ===
msg.c:9516: Test failed: wrong qstatus 00110011
msg.c:9523: Test failed: wrong qstatus 00190008
msg.c:9529: Test failed: wrong qstatus 00390020
msg.c:9538: Test failed: wrong qstatus 00790040
msg.c:9559: Test failed: wrong qstatus 00390000
msg.c:9567: Test failed: wrong qstatus 00790040
msg.c:9578: Test failed: wrong qstatus 00390000
msg.c:9589: Test failed: wrong qstatus 00310000
msg.c:9594: Test failed: PeekMessageA should have returned FALSE instead of msg 0113
=== W7PROX64 (64 bit msg) ===
Timeout
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=3020
Your paranoid android.
=== W98SE (32 bit internet) ===
internet.c:440: Test failed: A=B present
internet.c:442: Test failed: E=F present
internet.c:444: Test failed: I=J present
internet.c:445: Test failed: K=L present
internet.c:452: Test failed: A=B present
internet.c:454: Test failed: E=F present
internet.c:456: Test failed: I=J present
internet.c:457: Test failed: K=L present
internet.c:1158: Test failed: Retrieved proxy server should've been L"proxy.example", was: L"\0001\a000\2684X\0fb4h\0200"
internet.c:1164: Test failed: Expected regtype to be REG_DWORD, was: 3
internet.c:1192: Test failed: Retrieved flags should've been PROXY_TYPE_DIRECT, was: 5767180
internet.c:1195: Test failed: Expected regtype to be REG_DWORD, was: 3
internet.c:1222: Test failed: Retrieved flags should've been PROXY_TYPE_PROXY | PROXY_TYPE_DIRECT, was: 5767180
internet.c:1225: Test failed: Expected regtype to be REG_DWORD, was: 3
=== W2KPROSP4 (32 bit internet) ===
internet.c:440: Test failed: A=B present
internet.c:442: Test failed: E=F present
internet.c:444: Test failed: I=J present
internet.c:445: Test failed: K=L present
internet.c:452: Test failed: A=B present
internet.c:454: Test failed: E=F present
internet.c:456: Test failed: I=J present
internet.c:457: Test failed: K=L present
=== WXPPROSP3 (32 bit internet) ===
internet.c:517: Test failed: bad last error {error = 122}
internet.c:545: Test failed: the function failed
internet.c:546: Test failed: bad last error {error = 122}
=== WVISTAADM (32 bit internet) ===
internet.c:517: Test failed: bad last error {error = 122}
internet.c:545: Test failed: the function failed
internet.c:546: Test failed: bad last error {error = 122}
=== W2K8SE (32 bit internet) ===
internet.c:517: Test failed: bad last error {error = 122}
internet.c:545: Test failed: the function failed
internet.c:546: Test failed: bad last error {error = 122}
=== W7PRO (32 bit internet) ===
internet.c:474: Test failed: bad last error {error = 5023}
internet.c:502: Test failed: bad last error {error = 5023}
internet.c:517: Test failed: bad last error {error = 5023}
internet.c:545: Test failed: the function failed
internet.c:546: Test failed: bad last error {error = 122}
=== W7PROX64 (32 bit internet) ===
internet.c:474: Test failed: bad last error {error = 5023}
internet.c:502: Test failed: bad last error {error = 5023}
internet.c:517: Test failed: bad last error {error = 5023}
internet.c:545: Test failed: the function failed
internet.c:546: Test failed: bad last error {error = 122}
=== W7PROX64 (64 bit internet) ===
internet.c:474: Test failed: bad last error {error = 5023}
internet.c:502: Test failed: bad last error {error = 5023}
internet.c:517: Test failed: bad last error {error = 5023}
internet.c:545: Test failed: the function failed
internet.c:546: Test failed: bad last error {error = 122}
Hi wine developers!
I've written a conformance test (my first) for bug 17986:
BrsFolder_OnCommand make new folder not implemented. The conformance
test tests if clicking on the "Make New Folder" button in a
SHBrowseForFolder dialog box results in creation of a new folder. I
want the test to be localized and work across all newer versions of
Windows, but I'm having trouble with it.
I use the LoadString function to get the "New folder" string from
shell32.dll that is used for creating a new folder. The problem is
that the location where it is stored in shell32.dll varies between the
different versions of Windows. I can only make the test work on one
version at a time. Even the capitalization varies between the
different versions of Windows, i.e. "New Folder" vs. "New folder".
My question is how should we handle a problem like the one mentioned
above? Should we avoid using string resources in conformance test, or
should we try to handle the version issues?
One solution would be to hard code the string instead of loading it
from a resource. This would, however, mean that the test would be
skipped on all non-English versions of windows, and it would
additionally have to ignore the capitalization differences.
Another solution would be to get the string according to the version
of Windows. This would, however, pose a problem in wine because it
does not emulate any specific Windows version. The location of the
string in wine's shell32.dll does not match any version of Windows,
and we would therefore also have to detect if the test is running on
wine.
Has anyone bumped into the same problem, or does anyone know a thread
about this on wine-devel? Do you have any comments on what to do?
Thanks,
Michael Mc Donnell
Dear All:
I am a senior undergraduate applied mathematics/computer science
student and this year, I migrated from Windows 7 to Gentoo Linux on my
computers. I tried using Linux alternatives to many applications I
used on Windows, but not all software has good alternatives, so I have
been using WINE for certain things. The WINE project's accomplishments
so far have been extremely impressive, but at the same time, WINE's
implementation of the Windows API is deficient in many ways and I
think that the WINE project will need to improve its own organization
before progress toward true API parity with Windows can be made.
I can divide WINE's development resources into two groups, volunteer
and professional. The volunteer group is predominantly focused on
games.The professional group is comprised of CodeWeavers and Google.
CodeWeavers does what its customers want it to do, and as such, it has
a large focus on games. Google on the other hand, paid CodeWeavers to
make some improvements to WINE, mostly for Picasa, but also for Adobe
Photoshop CS2, the reason for which I cannot imagine. Google also has
its annual Summer of Code program. Each source of manpower has its own
special interest and I do not believe that WINE will ever obtain any
kind of API parity with Windows as long as this remains the case.
With these things in mind, I would like to propose that the WINE
project solicit grants from charitable organizations so that it could
hire professional developers to augment its existing resources,
specifically in the areas for which special interests could care less.
If the Wine project could solicit sufficient funding to hire a few
dozen developers for a period of several years, then I think that
having WINE become as good as Windows would enter the realm of
possibility. I know that many people will laugh at my suggestion
(especially when they read the organization I suggest that the WINE
project contact), but as far as I can tell, the WINE project has not
solicited grants to be able to hire professional developers and I
think that failing to solicit such grants places a handicap on the
WINE project.
There exist charitable organizations that seek to fund solutions to
"global problems that are ignored by governments and other
organizations" (as stated in Wikipedia). Because enabling Windows
programs to run on free UNIX operating systems would reduce the cost
of computing for all people, including those in third world countries,
I am certain that such organizations that would be willing to fund
WINE, provided that the WINE project inform them of its existence. The
specific organization from which I think that the WINE project should
attempt to solicit grant money is the Bill and Melinda Gates
Foundation. In consideration of their guiding principles and the fact
that they must spend $1.5 billion a year, it seems only logical to me
that they would provide funding for the WINE project if asked:
http://www.gatesfoundation.org/about/Pages/guiding-principles.aspxhttp://en.wikipedia.org/wiki/Bill_%26_Melinda_Gates_Foundation#Activities
The Bill and Melinda Gates Foundation is not the only organization for
which the WINE project could solicit funding, but I think that it is a
good place to start. Please consider the possibility of soliciting
grants so that the WINE project could hire professional developers.
Also, I am not registered on the mailing list, so please CC me any
responses made either directly or indirectly to this email, even if it
ridicules my suggestion.
Yours truly,
Richard Yao