On Sun, May 31, 2009 at 12:45 AM, Stephan Rose <ker...@somrek.net> wrote: >> If you're looking for something better specified, try finishing off >> gdiplus. > ... I'll check into gdiplus missing bits sometime next week. :) > > My name's Andrew Eikum, I'm an undergraduate Computer > Science student at the University of Minnesota. > I contacted a Wine dev a few weeks ago asking for a small > project to use to get familiar with Wine. I was pointed > towards the gdiplus section and told to begin stubbing > out the missing functions, to facilitate debugging. > After familiarizing myself with how Wine's DLLs are built, > and with Git, I'm now making quick progress. I expect to > have a (huge) patchset ready in the next week or two with > most of the gdiplus functions stubbed.
Excellent! (And Stephan, there's more than enough work to go around, don't worry that Andrew's going to do it all :-) > After that, I plan to begin work on implementing some of > the functions. My degree's emphasis is computer graphics, > so working on gdiplus will give me a chance to learn more > about the field as well as apply what I already know. > I'm looking forward to working with other Wine devs on > gdiplus, and other parts of Wine in the future. That's great to hear. Looking forward to seeing your patches. BTW, don't forget to look at http://wiki.winehq.org/GdiPlus, which has a few notes that might be helpful. My archive of Lei's notes at http://kegel.com/wine/sweng/2008/project.html from last year might be useful, too - it was tailored for people new to wine who want to contribute to gdiplus. (Though its big list of bugs is mostly all fixed now, I think only four remain.) - Dan
