On 5/8/07, Brian Vincent brian.vincent@gmail.com wrote:
On 5/8/07, Tom Spear speeddymon@gmail.com wrote:
That would be the framework. I appreciate the response. Is this something that either now or in the future will be officially supported by wine, or even a true goal of wine, or is it more of a side project for you and some others?
It's not an explicit goal, but it does work, and it is a configuration that we want to keep working. It's just not a configuration that gets tested every day, so there might be some little issues. Previously ReactOS was the big consumer of Wine DLL's as PE.
Ok, thanks for the input. Thanks to all of the developers for their hard work, and dedication. Unfortunately I am going to have to mute myself on the list (I can hear the sighs of relief now), as I dont think I am getting anywhere trying to get even trivial patches committed. I sent a patch over a week ago to correct a trace message (not the one for winecfg, but one for uninstaller), and it never got committed. Then I get told to send all of my patches to a developer privately for review before I send them to the patches list, and when I send them to that developer, I _basically_ get told that I should bother submitting them.
I know I'm not good enough to even write conformance tests right now, which is why I dont work on the major API's or even on the conformance tests, but sheesh, what do I have to do to get one problematic trace fixed? I'll send that patch one more time, just to make sure it got to the list, and I would appreciate someone offering some comment if there is a reason that it should not be committed.