DanKegel wrote: > By the way, I'm chatting with the author of PlayOnLinux about > improving relations between the two projects. A few guidelines > about how to report bugs to winehq will probably go a long way. > As a start, I'm stepping him through how to do vanilla wine > bug reports. Hopefully once he has some experience with how we > do things, he can spread the word. 1-POL already use Vanilla wine, builded from official sources, no modification. 2-A child can reproduce POL script with wine+winetricks ince POl functions are the SAME as winetricks do but instead of a monolithic monster with 90£ useless functions (for a gamer), they use small simple usefull functions like nstalling d3dx9 dlls or dotnet or vcrun...only th usefull part of winetricks (again, for a gamer). 3-POL use tips/tweaks/modifications reported on AppDB tests and AppDB tests only to make the game WORKING, like disabling hardware cursor for Kotor, ect...So arguing about modifications (not you Dan) is ridiculous. 4-POL v4 will use full python language for scripts, no more bash code you wil definitly don't want tests from it. I perfectly understand you need to be absolutely sure problems come from wine or the game only, but in his actual form, POL is a GUI doing BASH commands, the EXACT same bash commands you will do installing the game by hand. Don't tell me, when you see wine error output like this "err:ole:RevokeDragDrop invalid hwnd 0x1012c" it's POL fault, this is indeed wine error output. Now when POL users report POL bugs (GUI bugs) here it's absolutely normal you tell them it's POL related but when they report wine problems, it's neither fair nor normal to tell them it's POL fault.
