wine-devel

wine-devel@winehq.org

4 participants
84402 discussions

Re: Bugzilla, was Re: wineconf summary
by Jeremy Newman 19 Mar '02

19 Mar '02

On Tue, 2002-03-19 at 09:19, Dimitrie O. Paun wrote: > On March 19, 2002 08:49 am, Andriy Palamarchuk wrote: > > We already have such list. It is called "wine-user" > I'm not sold on the benefit of a bugs list either. We aren't that many > people, there's no point into slicing the traffic too much at this point. Actually, on winehq.com there still is a wine-bugs mailing list. What I can do is setup the Bugzilla database to send emails to that list when new bugs are added etc. We have been using a bugs(a)codeweavers.com email account to monitor this already. All I would need to do is forward those emails to that list. Also, the list could be setup like wine-patches, where replies to bugs go to wine-users but not back to the wine-bugs list. In essence the wine-bugs list would be browse only. Thoughts? -- __ _WebGeek/NetAdmin CodeWeavers -= http://www.codeweavers.com | \| |_____ __ ___ __ __ _ _ _ -= http://www.dracowulf.com | .` / -_) | | / ' \/ _` | ' \ -= mailto:jnewman@codeweavers.com |_|\_\___|\_/\_/|_|_|_\__,_|_||_| -= ICQ: 1842980 Yahoo: laxdragon

2 1

Joel on WINE
by Roland 19 Mar '02

19 Mar '02

Joel says something about WINE on: http://www.softwaremarketsolution.com/ Citation: Joel: But due to chicken-and-egg problems, running Windows apps is probably nonnegotiable for most people, so WINE is going to have to get a lot better before Linux is a threat to the desktop. I sort of expected with all the effort Corel put into it, it should be there by now, but they seem to be as far as ever from seamlessly running Win apps. (By the way, a lot of people think that the Windows API is too much of a moving target for WINE to catch up. As a Windows developer, let me say, this is rubbish. Almost every Windows app out there is tested on Win 95 to make sure it runs decently on the entire 32 bit Windows product line. If WINE could ever catch up to Win 95, they would be almost completely done. The target hasn't moved anywhere since August, 1995.) Linux is a great server OS, and with some UI work, it would be even better. (Yes, people still pay extra for NT on their servers because the GUI admin tools are much easier than

1 0

Fwd: Re: Road to 0.9
by Michael Cardenas 19 Mar '02

19 Mar '02

Yeah, I wanted to ask Alexandre at the conference how regression testing is a requirement. We need some specific numbers here. How many tests does he expect us to have? 10? 100? James Hatheway wrote: >>>* Regression Testing - Francois, Andridy, Patrick, >>>Dimi, Andi, Steven >>> >>Hmm, Regression Tests development will never finish. >>Can you define any specific goal for the regression >>tests you want to accomplish for 0.9? >> > >I believe the goal from Alexandre was that he just wanted >the frameworks stabilized, with documentation and some sample >tests. (I know there is a framework in place, it was demonstrated >at the conference, but I'm not sure if the API was frozen or not) > > >-James >

2 1

Re: Road to 0.9
by Ulrich Czekalla 19 Mar '02

19 Mar '02

On Tue, 2002-03-19 at 12:57, Dimitrie O. Paun wrote: > On March 19, 2002 12:48 pm, Andreas Mohr wrote: > > > > > The point is not to freeze the protocol completely, it will clearly > > > continue to evolve even after 1.0. The idea is that once the protocol > > > is declared frozen all future changes are done in a way that preserves > > > backwards compatibility. And the mechanisms to do that are mostly in > > > place now, which is what I mean by saying it is finished. > > > > OK, so in other words the wineserver *is* more or less "independent from > > such changes". > > How can that be? What we want is that DLLs compiled with 1.x, work (at the > binary level) with any 1.y server, where x <= y, right? > As long as you don't change the protocol used you can make as many changes as you like to the wineserver. It shouldn't affect dll compatibility. > -- > Dimi. > >

1 0

Re: Road to 0.9
by Michael Cardenas 19 Mar '02

19 Mar '02

I think this will really bring us a long way to having a stable wine. Does anyone besides lawson have a pet application that they use all the time? Any volunteers? James Hatheway wrote: >>C. Testing apps? I have no real idea what you mean. >> > >Sorry, I guess I should have been more clear, I just typed in >word for word my brief shorthand notes :) > >Basically, the idea that we had was the concept of getting users >to volunteer to "own" an app, ie. responsible for yelling when >we break an app. This already sort of happens, but never >in a formal way. We never decided the details, but I envisiage >having one person volunteering to each test their favourite app on every >release and filing bugs. (in a way that is helpful, we'll have docs for that) > > >-James >

2 1

Re: wineconf summary
by Michael Cardenas 19 Mar '02

19 Mar '02

I tried it and it doesn't work on any platform. I'll let lpbn know now. Sylvain Petreolle wrote: >I know, but it's not a normal situation ... >everyone should be able to see the entire data, >particularily those that don't have Internet Explorer >... >Think you don't have kde ? (like pure RedHat users) > > >>>why does the site lpbn.org does not show the >>> >>summary >> >>>of the conference when we use netscape or mozilla >>> >>? >> >>Works with Konqueror... >> >>LLaP >>bero >> > > >___________________________________________________________ >Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en français ! >Yahoo! Mail : http://fr.mail.yahoo.com > >

1 0

[Fwd: Re: Bugzilla, was Re: wineconf summary]
by Michael Cardenas 19 Mar '02

19 Mar '02

Dimitrie O. Paun wrote: >On March 19, 2002 08:49 am, Andriy Palamarchuk wrote: > >>>dimitry suggested posting the top 10 or >>>20 bugs to wine-devel every other week, and I >>>suggested putting the in WWN. >>> >>I'm not sure about usefullness of this one. What we >>need are people, responsible for Wine subsystems. >> > >No, this is from another perspective. And that is, getting more people into >Wine devel, like the Abiword folks do. Problem is that right now the barrier >to entry is enormous: the project is huge, and there is no clear list of >_small_ tasks (which require little knowledge of the project). Going through >Bugzilla is not an option -- few people do that. If we extract a list of >10-20 bugs, and post them on WWN, a _lot_ more people will see them, click on >it, etc. It's just a way of getting people into the game, that's all. > I think it's also important to keep the developers focused. If we just work on whatever comes up, or whatever users ask for at any given moment, we won't focus on getting to 0.9 and it won't happen. I think that ideally we should move to a release schedule like KDE does where they work towards releases at specified dates. There needs to be a time where we all try to do clean up and focus on doing grunt work to solidify releases.

1 0

RE: Linuxism in dlls/msvcrt/msvcrt.spec?
by Medland, Bill 19 Mar '02

19 Mar '02

> -----Original Message----- > From: Gerald Pfeifer [mailto:pfeifer@dbai.tuwien.ac.at] > Sent: Monday, March 18, 2002 8:31 AM > To: wine-patches(a)winehq.com > Cc: Martin Faxer > Subject: Linuxism in dlls/msvcrt/msvcrt.spec? > > > I believe there is a Linuxism in dlls/msvcrt/msvcrt.spec which expects > that _tolower and _toupper exist as functions. > > The following patch by Martin Faxér > <gmh003532(a)brfmasthugget.se> addresses > this; if this patch seems unacceptable, we'd appreciate a > note and a short > explanation why the current code is fine and the patch is not fine. > > Thanks, > Gerald Well actually I think both are wrong; I am just doing the patch. (Actually I don't understand where the _toupper is coming from) The problem is that _toupper is NOT the same as toupper; _toupper does not test that the character is lowercase; it just converts it. The patch is to hook into the existing MSVCRT__toupper and MSVCRT__tolower. Bill

1 0

debugging longman dictionary
by Rizsanyi Zsolt 19 Mar '02

19 Mar '02

Hi! I'm trying to debug what goes wrong with the Longman Dictionary of Contemporary English. I have succeeded installing it under wine on a fake windows installation. (I had some problems, and posted them on wine-user, but I have succeded) Now I get an unhandled exception (page fault on read access). But I cant find the cause of the problem. Maybe somebody could hint me how to proceed. I'm attaching the output of wine --debugmsg +relay LDOCE32.EXE Also I have set up a breakpoint, and stepped through the last 10 instructions before the page fault, but I dont understand what that code is trying to do (it is somewhat strange). Also it may be usefull if you could put in a faq or some other documentation that the next output (which is very frequent), is just a check running debugger. This check is usually done in sharewares to check whether the program is debugged. This is the characteristic output: fixme:win32:DEVICE_Open Unknown/unsupported VxD SICE. Try --winver nt40 or win31 ! fixme:win32:DEVICE_Open Unknown/unsupported VxD SIWVID. Try --winver nt40 or win31 ! fixme:win32:DEVICE_Open Unknown/unsupported VxD NTICE. Try --winver nt40 or win31 ! At first I tried to define these VxD-s, but when I did so the program instracted me to stop the debugger and restart. Thanks for your attention, and I hope you can help me :) Zsolt Rizsanyi

2 1

Status of Wrc port to mingw
by Steven Edwards 18 Mar '02

18 Mar '02

I'm currently trying to port wrc to mingw. Everthing builds fine except when running "bison -bppy -ppp -d -t ./ppy.y" I get "conflicts: 2 shift/reduce". I have started bug 474 in bugzilla if anyone wants to help with this. Thanks Steven _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com

2 2

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

2001

wine-devel