February 2002 - Wine-devel - list.winehq.org

RE: Header files not present on Windows
by Patrik Stridvall 05 Feb '02

05 Feb '02

> Patrik Stridvall <ps(a)leissner.se> writes: > > > Hmm. I'm note sure I like making unistd.h > > an optional header but then few part of > > Wine should include it anyway so perhaps > > it doesn't matter. > > The question is whether you can build without it. If the needed > definitions are provided by other includes then it's fine to make it > optional; but if the code doesn't compile without it then there's no > point in having a check. Yes and in many cases it did work without unistd.h, but maybe that is because it really wasn't needed at all. In some case it might have worked because some of the functions in unistd.h is defined else where in Windows and in some case we might get it to work by including needed files. Of course in such cases we probably should fix Wine and include that other header exclusively instead of unistd.h. Anyway, I just experimented a little trying to get Wine to compile under Windows. I'm not really sure exacly what to do. Eventually I guess that the non-core DLL:s never should call any non Windows functions at all and the core DLL:s are not really useful to compile and run under Windows anyway.

1 0

Re: Header files not present on Windows
by Alexandre Julliard 05 Feb '02

05 Feb '02

Patrik Stridvall <ps(a)leissner.se> writes: > Hmm. I'm note sure I like making unistd.h > an optional header but then few part of > Wine should include it anyway so perhaps > it doesn't matter. The question is whether you can build without it. If the needed definitions are provided by other includes then it's fine to make it optional; but if the code doesn't compile without it then there's no point in having a check. -- Alexandre Julliard julliard(a)winehq.com

1 0

TSXxxx functions: die!
by Dimitrie O. Paun 05 Feb '02

05 Feb '02

Once again, Since this list is (again!) so quiet, I feel obligated to stir the spirits a little. So here it goes: we should get rid of the TSXxxx functions. Why? -- we don't keep to standard API, which is against the Wine's spirit -- they introduce yet another (useless) layer -- we reaquire the lock like crazy for no good reason -- most modern X systems are already thread safe -- we integrate Wine's locking with glic's, so we should be OK -- they are ugly How? s/TSX/X/g rm -rf tsx + misc Makefile cleanups But I hear people screaming: how about portability? What about platforms where we don't integrate with libc's locking, or when we don't have a thread safe X? Well, we can create a wrapper driver which simply aquires the lock, calls into the regular driver, then releases the lock. In fact, I am not convinced we shouldn't deal this way with the current driver, to simplify the code. It's not like we're missing a lot on performance... -- Dimi.

1 0

WineHQ cvs
by Francois Gouget 05 Feb '02

05 Feb '02

I was looking at the WineHQ CVS last week-end (trying to add a section about how to contribute to Wine and to beef up the about section) and, at least to an untrained eye, it looks like it contains many obsolete files that should be deleted. Here are some examples: * a number of files exist in both .html and .shtml form. Isn't the html form obsolete? about.html & about.shtml contrib.html & contrib.shtml search.html & search.shtml who.html & who.shtml * some files have multiple versions lying around refs.html & refs.shtml & refs2.html index.shtml & indexold.html * there is a number of file that I'm not sure are still in use threads_etc, referenced from design.html which is referenced, but commented out, from indexold.html & test003.html win_utils_test, does not appear to be referenced anywhere shots.html, referenced only from indexold.html Is there a good reason to keep the above files? Did I miss something? -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ "Lotto: A tax on people who are bad at math." -- unknown "Windows: Microsoft's tax on computer illiterates." -- WE7U

2 1

Re: Make a progress bar control behave more like a windows equivalent
by Dimitrie O. Paun 05 Feb '02

05 Feb '02

On Tue, 5 Feb 2002, Dmitry Timoshkov wrote: > Hello. > > According to my test application, progress bar control always does > InvalidateRect() if it wants to repaint itself. It is smart enough > whether or not invalidate background. Probably other comctl32 controls > need to be fixed in respect of this. That's a good point. When I wrote the Progress Bar & Up Down Controls way back when, I did the repaint thingy as other controls were doing. So I think this style simply got propagated through the controls without good reason, other than "others do it too". -- Dimi.

1 0

Re: *MEGA* bug
by lawson_whitney＠juno.com 05 Feb '02

05 Feb '02

On Tue, 28 Nov 2000, it was written: > > > On Mon, 27 Nov 2000, Andreas Mohr wrote: > > > Hi all, > > > > does no Windows program at all ever check return values !?!?!? OOPS, sorry. This and the other anachronisms are what come of using pieces of my mail system to do stress tests. Lawson Probable user head space error. - Dennis A. Moore

1 0

How long for CVS?
by Gerhard Gruber 04 Feb '02

04 Feb '02

A few days ago I sent a patch for WritePrivateProfileSection that fixed the wrong behaviour that this function should create multiple keys with the same name which will be needed for wininit.ini. Now I have seen two updates of the CVS tree but this path hasn't been applied. Does this mean I should resend it to the pathces list, or should I wait a bit longer? How long does it usually take for a patch to get submitted?

1 0

Re: Listview Unicodification (part 2)
by Alexandre Julliard 04 Feb '02

04 Feb '02

"Dimitrie O. Paun" <dimi(a)cs.toronto.edu> writes: > Alexandre, let me know if you like the patch better in this format. Yes, it's much better that way, thanks. -- Alexandre Julliard julliard(a)winehq.com

1 0

Re: API test suite
by Andriy Palamarchuk 04 Feb '02

04 Feb '02

Hi Chris, thank you for suggesting the help. Preferred method of contacting Wine developers is posting to mailing list wine-devel. In this way everybody can participate in the discussion and the conversation will be documented for later reference. See www.winehq.com how to join the list. I forward my response to the mailing list. Chris Caston wrote: > I have volunteered myself to help test Windows functions for > compatibility with WINE. I'm am not one of the WIndows programmers but I > intend to take responsibility for many of the functions to be checked > and to keep track of functions (perhaps even developers) and their > status in a database. As well a setup assocation to e-mail results to > other important people. You are welcome! You can learn Windows programming while creating the tests. Knowing answers for these questions I can better help you: What is your programming experience? Do you have any Windows develoment tools? What operation systems do you currently use (Windows, Linux)? > Could be so kind to shed some light on the API test suite. Firstly, how > well documented are these functions? > > I'm getting conflicting information in this issue. Some people say that > the Win32 API is obscured and kept closed while others say that it is > one of the most throughly documented API's in use today with many books > about programming in this environment and information on the MSDN site. On one hand there are a lot of documentation about Win32 API, on other hand the documentation is often misleading, there is a set of API which is not documented at all and some programs, especially Microsoft products (IE, Office), tend to use it. Don't warry about this. We don't have any tests. Start with writing tests for well-documented API, document the cases when Win32 API behaviour differs from the documentation. > I have found a page that lists 350+ functions: > > http://www.vbapi.com/ref/funca.html Before somebody mentioned that Windows has more than 12,000 API functions :-) MSDN (msdn.microsoft.com) is the best source of information about Windows API. You also can find a lot of information on the Net. Some references are listed on www.winehq.com. > Secondly, what mechanisms are being used for the test suite? We are going to use tests, written in C and Perl. > Have these yet been agreed on? Kind of - we already finished *very* active discussion on the topic :-) Perl and C frameworks and tests conventions are under development. If you are interested, see thread "Re: We *really* need a development model change !" and a few other threads for details. > Do you have some test functions already written that I can see? Yes, the Perl framework with sample test is already in Wine code repository in programs/winetest directory. You can browse Wine source online at: http://cvs.winehq.com/cvsweb/ I have C testing framework, but it is not in CVS yet. Alexandre, what is the status of C testing framework? Do you want me to submit the latest version I have (without using the _T macro) for including in CVS? The process of tests development, especially on Windows, is not created yet. > How can I learn the processes involved? The development process is described on www.winehq.com. Please, read the documentation presented there. Good luck. Andriy Palamarchuk __________________________________________________ Do You Yahoo!? Great stuff seeking new owners in Yahoo! Auctions! http://auctions.yahoo.com

1 0

RE: Another Potential Slave... I mean Programmer
by Joe Tennies 04 Feb '02

04 Feb '02

Okay. I'll admit I am biased toward GNOME, but my real problem is that I didn't explain myself much, and I doubt people actually went to look at the gstreamer site. I had found it before, but forgot about. Why I think KDE should adopt gstreamer as well. It is not a replacement for ALSA, OSS, ESD, or aRts... it's an add-on to it. My understanding of the gstreamer project is that it's Linux/UNIX's response to the Windows CODEC system. It is a single interface to output video and audio from various types of input file types. They have support for MP3s, DIVX (coming), Ogg Vorbis, DVD, AVI, MPEG, Video 4 Linux, etc. for input files. It also supports OSS, ALSA, esd, aRts, X11, aalib (gotta love it), SDL, etc. for outputs. This is obviously not for programs that need low latency. It is for your everyday stuff. It is more than good enough for saying "you got mail," yet it would have support for lots of files types w/o specifically writing support for the new file type. This is also good for multimedia players and web browsers due to the support for lots of file types (I could see XMMS switching to this from its plugin system). Is this the answer for recording studio programs, remakes of Rebirth (WE NEED ONE OF THESE), or people that need the audio fast, but for the typical desktop user, it will be a god send. Only downfall I could see to the KDE crowd is the need to install GLIB. It doesn't require the full GTK+, just GLIB (linked lists and other datastructures). KDE could recommend using aRts for output and write its own input plugins for implementations that depended on a library KDE didn't need installed but KDE did install another one that implemented something simiilar. HECK, I don't think anyone would mind KDE writing their own underlying/core part, required you use aRts for output, didn't require GLIB (though this may be difficult), but used those input plug-ins. I understand KDE and GNOME have very different things in their head, but we need to get some standards here. XDND was way overdue (though I hear it wasn't a great implementation, at least they agreed on how to do something), and the two groups need to make more decisions like these to help each other strive. Remember everyone. I WAS a HUGE KDE fan myself for years. I had installed GNOME a couple times and hated it. I used KDE through 2.1 (I think... definitely in the 2.X). Then I discovered I had Blackbox on my machine, and it flew. I like the QT library (though I won't use it because I am now a GNOME guy). I like the layout of KDE... simple yet sophisticated. It tailors to the geek and the 'typical home user.' I just like GNOME's CORBA interface they are adding (which is where gstreamer will fit in). Something that can be so easily updated and contain potential problems is powerful (though VERY frustrating at times). I also love Ximian, who I feel keeps pushing the things that need to get done to make Linux a full fledged desktop system -- not to mention their love of all things monkey =) I salute KDE. They did the large scale desktop environment for the masses first (CDE is NOT for the masses anymore). They are probably still doing it best (I hear lots of complaints about some of GNOME's design). The problem I see is that there's no one really pushing KDE to keep its lead (and the slow speed it had under Mandrake). -----Original Message----- From: Christopher Morgan [mailto:chmorgan(a)speakeasy.net] Sent: Saturday, February 02, 2002 11:46 PM To: Joe Tennies Subject: Re: Another Potential Slave... I mean Programmer It would be interesting to see a latency comparison between gstreamer, arts and jack. If gstreamer doesn't get very close to what jack can do then it isn't the solution for the future. We need low latency or tons of audio apps will continue to find it through direct alsa or jack interfaces. Ideally we should pick the best solution and much of it is based on the latency issue, features should come after and should be designed such that they don't increase latency by any more than they have to. It sounds a little like you want to go with a gnome solution because you use gnome. I think more work needs to be done to come up with a linux(open source or whatever as well) wide solution to the problem. Chris On 2 Feb 2002, Joe Tennies wrote: > On Sat, 2002-02-02 at 05:42, Hetz Ben Hamo wrote: > > > I'm not trying to start a Gnome/KDE flame war, but as far as I know, esd is > > > unmaintained and the Gnome developpers are thinking about switching to > > > aRtsd. Wouldn't it be more useful to write an aRts driver ? > > > > Actually if I'm not mistaken - GNOME people are moving to gstreamer, if I'm > > not mistaken. I'm not sure since I work with KDE here... > > > > Hetz > > > Actually, I just looked at gstreamer. It lies above aRts, esd, alsa, and oss. It is a platform independent (well, not ported to everything yet, but working on it) system. I think KDE SHOULD be heading this way and am impressed that GNOME is. I think that gstreamer would be the way to go for WINE. > > > >

1 0