March 2003 - Wine-Devel - list.winehq.org

Re: Contributing page needs fixing

by Dimitrie O. Paun

On March 30, 2003 04:53 am, Francois Gouget wrote: > 'Wine is almost finished and there are few things that are missing -- > and these can't by just anyone. Really, now the last thing we need is > people comming over and messing with the source.' You can't "slightly transpose" things and expect that you get anything interesting. Look, all I'm saying is that this gives the wrong impression. Wine really needs developers in 99% of the cases. We can have the greatest website, and a nice Bugzilla, and all the organization that we'd want, but without code, it's nothing. On the other hand, any improvement in the code will get us more users, more developers, more mind share, and that will result in people helping out *automatically* without us asking for help. So let's look at the Contributing page. We ask for web people. Fine. We could use some, granted, but do we really need anyone at the moment? What would they do? I've posted a "still TODO" list a few days ago, almost nothing there can be easily done by a newcomer. Actually what we need is someone that monitors the wine-devel list like Brian so they can keep things like the Who's Who etc up to date. But for those we don't need to advertise on that page! So my problem is one of priorities. The very first thing we say is: we need help with the web site! But that's simply false. What we really need is developers, people testing apps, and customers for Wine-based companies. Period. The rest matters less than 0.000001% in the great scheme of things. So let's be truthful, I think it works better in the long run. -- Dimi.

March 30, 2003

Re: Contributing page needs fixing

by Francois Gouget

On Sat, 29 Mar 2003, Dimitrie O. Paun wrote: [...] > I think we should remove this section altogether. The page is already > way too big, and this is as bad as a not enough info. The site has been > redesigned, and there are only a few things that are missing -- I think we need a web site maintainer. Jeremy Newman has other stuff to do and will not be able to do the heavy lifting forever. Also I think he very much prefers writing PHP code rather than updating the contents of the site. So we do need a web site maintainer. AFAIK we have no-one taking care of the site besides Brian Vincent who does a great job with the Wine Weekly News btw. But if the rest of the site is not kept up to date it will quickly get outdated and useless. > and those can't be done by just anyone. > Really, now the last thing we need is > people comming over and messing with the site. Let's have a *focused* page > on where we need help, not a laundry list of just about everything. Let me transpose this just slightly: 'Wine is almost finished and there are few things that are missing -- and these can't by just anyone. Really, now the last thing we need is people comming over and messing with the source.' See how silly that sounds? It's just plain 'cathedral development' FUD. Nobody is going to be messing with the site. Jeremy (or maybe someone else) will have final say over what goes on the site, just like Alexandre does for the Wine source. In the meantime, there are a lot of opportunities to catch dead links, improve the site content here and there (and I would say this includes the documentation) and add new stuff. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ "Utilisateur" (nom commun) : Mot utilisé par les informaticiens en lieu et place d'"idiot".

March 30, 2003

SHFileOperation regression test

by Rolf Kalbermatter

While working on SHFileOperation in shell32.dll I came across the error in line 286 and 287 which happens on Win98/ME/2K/XP but not on 95/NT. Investigation showed that the copy operation of multiple files with one source file not existing in the list, has different behaviour on these two groups of OS Versions. Win 95/NT abort the copy operation at the first file not existing, and return WITHOUT any error indication whatsoever, leaving the already copied files in the target directory. Win 98/ME/2K/XP have obviously fixed this bug in a rather strict manner, in that such a copy operation is aborted with error return value 1026 (undocumented, resp. meaningless in this cicumstance other than that it is non-zero), and no file is copied at all. (There still exists a small bug, at least in 2K, in that the fAnyOperationsAborted flag in the SHFILEOPSTRUCT structure is not set at all in this case on return.) Obviously our shlfileop.c test needs fixing but I'm not sure how to proceed as I'm fairly new to the Wine regression testing. From what I gathered it is not really acceptable to create Windows version dependant tests in the regression framework, which leaves only two other options, IMO: 1) Remove this particular test altogether or 2) Test only the behaviour which is consistent on all platforms which in this case would be only the non-existence of the test2.txt file. Both options leave out possibly important regression test cases for the future. Any comments on this issue from the more seasoned guys into regression test writing? Appended is the patch which is correct for Win 98/ME/2K/XP but will cause test failure on 95/NT. Rolf Kalbermatter Index: dlls/shell32/tests/shlfileop.c =================================================================== RCS file: /home/wine/wine/dlls/shell32/tests/shlfileop.c,v retrieving revision 1.6 diff -u -r1.6 shlfileop.c --- dlls/shell32/tests/shlfileop.c 14 Jan 2003 23:43:42 -0000 1.6 +++ dlls/shell32/tests/shlfileop.c 30 Mar 2003 08:52:58 -0000 @@ -278,13 +278,15 @@ ok(file_exists(".\\testdir2\\test2.txt"), "The file is copied"); clean_after_shfo_tests(); + /* Copying multiple files with one not existing as source, fails the + entire operation in Win98/ME/2K/XP with return value 1026, but only + the files after the one not existing and without any error indication + in 95/NT, ! */ init_shfo_tests(); tmp_flags = shfo.fFlags; set_curr_dir_path(from, "test1.txt\0test10.txt\0test2.txt\0"); ok(!file_exists(".\\testdir2\\test1.txt"), "The file is not copied yet"); ok(!file_exists(".\\testdir2\\test2.txt"), "The file is not copied yet"); - ok(!SHFileOperationA(&shfo), "Files are copied to other directory "); - ok(file_exists(".\\testdir2\\test1.txt"), "The file is copied"); + ok(SHFileOperationA(&shfo), "Files are copied to other directory "); + ok(!file_exists(".\\testdir2\\test1.txt"), "The file is copied"); ok(!file_exists(".\\testdir2\\test2.txt"), "The file is copied"); shfo.fFlags = tmp_flags; }

March 30, 2003

Re: Compiling WINE - Hopeless situation? :)

by Dan Kegel

Sylvain wrote: > --- Michael Stefaniuc <mstefani(a)redhat.de> a écrit : > On Sun, Mar 30, > 2003 at 12:44:31AM +0100, Sylvain Petreolle wrote: >> > The code that has problem for now is C code, not C++, am I right >> here ? >> > Then it has nothing to do with C++ thing. >> Yeah, but the page you pointed to is for C++ incompatibilities, not >> C. >> And a newer 2.96 is stable for C. > If there is one, it isnt shipped with RH 8, or not by default. Red Hat 8 uses gcc3.2. If you have Red Hat 8, you don't need gcc2.96. > "Current snapshots of GCC, and any version labeled 2.96, produce object > files that are not compatible with those produced by either GCC 2.95.2 > or the forthcoming GCC 3.0." This is true only for C++. For C code, Red Hat's gcc2.96's have been just fine. - Dan -- Dan Kegel http://www.kegel.com http://counter.li.org/cgi-bin/runscript/display-person.cgi?user=78045

March 30, 2003

Re: bin2rc

by Sylvain Petreolle

doesnt it convert a .rc to a .res ?? > > I've just stupidly lost an hour or so trying to figure out > > how to convert a .bmp to a .rc script. Such a simple problem... > > That's what tools/bin2res is for... ===== Sylvain Petreolle (spetreolle at users dot sourceforge dot net) ICQ #170597259 No more War ! "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". For the Law of Oil and Fire, Im an European that lives in France. For all my Brothers and friends, Im a human living on Earth. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

March 30, 2003

Re: Contributing page needs fixing

by Dimitrie O. Paun

On March 29, 2003 09:48 pm, Francois Gouget wrote: > Wine-Develipmont</a>. > + <p>WineHQ has been redisigned recently. But there is still work to do. > + So you would feel like writing about Wine or coding in Php your > + contribution will be appreciated. You can find the current task list I think we should remove this section altogether. The page is already way too big, and this is as bad as a not enough info. The site has been redesigned, and there are only a few things that are missing -- and those can't be done by just anyone. Really, now the last thing we need is people comming over and messing with the site. Let's have a *focused* page on where we need help, not a laundry list of just about everything. -- Dimi.

March 30, 2003

Re: bin2rc

by Dimitrie O. Paun

On March 29, 2003 10:11 pm, Alexandre Julliard wrote: > That's what tools/bin2res is for... Maybe, but it doesn't work: [dimi(a)dimi test]$ ls wine.bmp [dimi(a)dimi test]$ ../wine/tools/bin2res wine.bmp [dimi(a)dimi test]$ ls wine.bmp [dimi(a)dimi test]$ Also, the code seems overly complicated. Granted, it does more than my one-line script, but still... -- Dimi.

March 30, 2003

Re: bin2rc

by Alexandre Julliard

"Dimitrie O. Paun" <dpaun(a)rogers.com> writes: > I've just stupidly lost an hour or so trying to figure out > how to convert a .bmp to a .rc script. Such a simple problem... That's what tools/bin2res is for... -- Alexandre Julliard julliard(a)winehq.com

March 30, 2003

Wine's goals

by Francois Gouget

I propose the following WineHQ patch to present and clarify Wine's goals. I'm submitting this to wine-devel first to get a feel of whether that would be a good addition and whether that sounds reasonable and accurate enough. Index: templates/en/about.template =================================================================== RCS file: /home/wine/lostwages/templates/en/about.template,v retrieving revision 1.7 diff -u -r1.7 about.template --- templates/en/about.template 24 Mar 2003 22:49:03 -0000 1.7 +++ templates/en/about.template 30 Mar 2003 02:35:46 -0000 @@ -29,4 +29,70 @@ <a href="mailto:julliard(a)winehq.com">julliard(a)winehq.com</a>. For a list of current developers, see the <a href="?page=who">Wine Who's Who</a>.</p> + +<h1>Wine's Goals</h1> + +<p>As mentionned in many places, the primary goal of Wine is to make it +possible to run Windows applications on x86-based Unix systems. But there is +often confusion as to what this covers. So let's clarify things a bit: + +<ul> + <li>Wine does not try to be a better Windows than Windows. What this means + is that Wine will not try to extend, improve or 'fix' the Windows API in + an attempt to lure developpers into using it. While we think that it is + important to provide a way to reuse the legacy Windows applications that + are out there, we feel that for new developments there are better APIs + than Win32. + + <li>Wine Is Not a (CPU) Emulator. So no, we will not integrate a CPU + emulator in Wine any time soon. However we will do what we can to make it + possible to integrate Wine into a CPU emulation environment that would + provide the regular Unix services that Wine depends on. In such a scheme + both Wine and the Windows application would be run in that environment. + Two candidates that come to mind are <a + href="http://fabrice.bellard.free.fr/qemu/">QEMU</a> and + <a href="http://www.transitives.com/tech_overview.htm">Dynamite</a> from + <a href="http://www.transitives.com/">Transitives Technologies</a>. + + <li>Wine's goal is to provide replacements for just those DLLs and APIs + that are needed to run Windows applications. This means that we will not + provide replacements for DLLs that are always shipped together with an + application. This also means that implementing an API that no application + ever uses is not a priority. Similarly, until there are applications out + there that use the Win64 API, it will not be a priority. That being said, + we will certainly try to keep our options open and to improve our API + coverage as we can. + + <li>Making it possible to use Windows device drivers or VxDs on Unix is not + part of Wine's goals. Device drivers don't use the same API that Windows + applications do, and run in ring 0 instead or ring 3. To make it possible + to use them on Unix, one would have to hack the kernel, implement a + completely different API. In other words, this would be a completely + separate project. However, if you want to reuse Windows drivers on + non-Microsoft operating systems we recommend that you have a look at + <a href="http://www.reactos.com/">ReactOS</a>. + + <li>Wine is not an operating system or a desktop environment. So writing + device drivers, file or window managers that look like Windows, are not + part of Wine's goals. If you are interested in those, the best would be to + contribute to the <a href="http://www.kernel.org/">Linux</a>, + <a href="http://www.freebsd.org/">FreeBSD</a> or + <a href="http://www.reactos.com/">ReactOS</a> kernels, or to the + <a href="http://www.gnome.org/">Gnome</a> or + <a href="http://www.kde.org/">KDE</a> desktop environments. You will get + the added benefit that your contribution will then be usable by everyone, + not just by Wine users. + + <li>Wine's focus is on Unix operating systems, and to some extent Linux + because that is what most of our developpers are using. However we welcome + ports to other architectures such as + <a href="http://www.reactos.com/">ReactOS</a> or + <a href="http://bewine.beunited.org/">BeWine</a>, and will try to make + it possible for them to reuse as much of Wine as possible. After all, + reimplementing the Windows API is a big enough task that it is best if we + can all work together on it. +</ul> + + <p> </p> + -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ War doesn't determine who's right. War determines who's left.

March 30, 2003

Re: Compiling WINE - Hopeless situation? :)

by Sylvain Petreolle

--- Michael Stefaniuc <mstefani(a)redhat.de> a écrit : > On Sun, Mar 30, 2003 at 12:44:31AM +0100, Sylvain Petreolle wrote: > > The code that has problem for now is C code, not C++, am I right > here ? > > Then it has nothing to do with C++ thing. > Yeah, but the page you pointed to is for C++ incompatibilities, not > C. > And a newer 2.96 is stable for C. If there is one, it isnt shipped with RH 8, or not by default. Could you point me to where it can be downloaded ? Has it dependancies to be updated ? If it isnt newer than 2003-02-21, date at this page was modified, it says : "Current snapshots of GCC, and any version labeled 2.96, produce object files that are not compatible with those produced by either GCC 2.95.2 or the forthcoming GCC 3.0." ===== Sylvain Petreolle (spetreolle at users dot sourceforge dot net) ICQ #170597259 No more War ! "What if tomorrow the War could be over ?" Morpheus, in "Reloaded". For the Law of Oil and Fire, Im an European that lives in France. For all my Brothers and friends, Im a human living on Earth. ___________________________________________________________ Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! Yahoo! Mail : http://fr.mail.yahoo.com

March 30, 2003