Hello
Please take the following not personal but the huge pent-up frustration constrains me to say a few words.
I've just tested one of my "longest waiting" apps to get working on linux: CorelDraw X3/X4. And I had to see that it fails already with the same errors. I tooke a short look into the bug database to see all the related bugs:
http://bugs.winehq.org/show_bug.cgi?id=11687 open (not even confirmed) since more than 3 years http://bugs.winehq.org/show_bug.cgi?id=14123 open since 2008-06-25 http://bugs.winehq.org/show_bug.cgi?id=3599 open (new) since 2005-10-15 http://bugs.winehq.org/show_bug.cgi?id=3611 open (new) since 2005-10-17
I know we had this discussion already a lot of times but after six acc. three years its time for me to say something again. I know also thats a lot more fun developing directx routines instead of fixing old bugs but sometimes You should also think about the "other" generality which uses the computer not just to play games.
It would be understandeable to me if its written in the bug that the fix of this bug will consume a lot of resources and its impossible to fix this, but just to ignore it is not "the proper way to behave".
I'm sure that there are many more of the above bugs which nobody has has ever took seriously a lock at it. Has anybody ever imagined how many apps depending on such bugs which prevents them to get running on Linux? Maybe all of the above bugs are only related to CorelDraw but its also possible that dozens or hundrets of other apps also fail with the same problems but nobody has ever wrote a bug report or saw it in the bug database and thought that it will be fixed cause its already reported?
Just take a look at: http://www.inside-it.ch/frontend/insideit?_d=_article&site=ic&news.i... English version: http://arstechnica.com/civis/viewtopic.php?f=14&t=1122655
The most of their problems where related to special windows apps running only in goverment institutions and where not able to run on Linux (wine). How many of these problems whould not even ever have been occured if such small bugs like the above whoud be fixed which makes all of those apps runnable on linux. Sorry to say that but Your politics just to develop things which makes fun or are interesting is also part of the above problem.
Regards
Roland
On 7 May 2011 12:52, Roland Kaeser roli8200@yahoo.de wrote:
I know also thats a lot more fun developing directx routines instead of fixing old bugs but
No, it isn't. Sorry. But you know, git is awesome. You can spend days doing all kinds of interesting things, like figuring out which people contribute to which areas of Wine, etc. I'll leave that as an exercise for the reader, but you'll probably find there aren't actually all the many people "developing directx routines" all day. Fortunately Wine, like any good Free Software project, has much more people that are good at complaining associated with it than, well, any of these nasty developers, so that makes it all ok.
It would be understandeable to me if its written in the bug that the fix of this bug will consume a lot of resources and its impossible to fix this, but just to ignore it is not "the proper way to behave".
Most wine developers are just people sorting out problems that either affect them or have some intrinsic reason to work on the problem. Many of them get started because they want to resolve a bug to allow a Windows program to run. If the bugs you are experiencing are not getting traction then you can always have a look yourself.
On 5/7/11 3:52 AM, Roland Kaeser wrote:
Hello
Please take the following not personal but the huge pent-up frustration constrains me to say a few words.
I've just tested one of my "longest waiting" apps to get working on linux: CorelDraw X3/X4. And I had to see that it fails already with the same errors. I tooke a short look into the bug database to see all the related bugs:
http://bugs.winehq.org/show_bug.cgi?id=11687 open (not even confirmed) since more than 3 years http://bugs.winehq.org/show_bug.cgi?id=14123 open since 2008-06-25 http://bugs.winehq.org/show_bug.cgi?id=3599 open (new) since 2005-10-15 http://bugs.winehq.org/show_bug.cgi?id=3611 open (new) since 2005-10-17
I know we had this discussion already a lot of times but after six acc.
Many bug fixes depend on fixing a six year old + bug (421). However, if you feel so strongly, then maybe YOU can take a stab at trying to fix a bug. It is NOT easy (6724 is one bug that I'm working on and it has been around for four+ years.)
Also, not all developers are working on fixing and improving DirectX. Some are working on code improvements and long overdue code cleanups.
James McKenzie
Am 07.05.2011 12:52, schrieb Roland Kaeser:
http://bugs.winehq.org/show_bug.cgi?id=11687 open (not even confirmed) since more than 3 years http://bugs.winehq.org/show_bug.cgi?id=14123 open since 2008-06-25 http://bugs.winehq.org/show_bug.cgi?id=3599 open (new) since 2005-10-15 http://bugs.winehq.org/show_bug.cgi?id=3611 open (new) since 2005-10-17
After i read through the bugs, i think the activity wasn't that low. But e.g. no reply by you or the bug reporter on comments like http://bugs.winehq.org/show_bug.cgi?id=14123#c8 or http://bugs.winehq.org/show_bug.cgi?id=3611#c22 is also a reason. Further you can't motivate volunteers by attacking them.
-
André Hentschel -
Henri Verbeet -
James McKenzie -
Lats -
Roland Kaeser