Hello all, I am new to the wine scene and would like to try my hand at a little wine hacking. Are there any bugs out there that would be easy for a newbie to fix while letting me learn a bit about the inner workings of wine? I have read all the material about getting started developing, but I am just lacking a bit of direction on what to work on :)
Thanks for your help, ryan
On Mon, Nov 26, 2001 at 08:02:32PM -0500, Ryan C. Stallings wrote:
Hello all, I am new to the wine scene and would like to try my hand at a little wine hacking. Are there any bugs out there that would be easy for a newbie to fix while letting me learn a bit about the inner workings of wine? I have read all the material about getting started developing, but I am just lacking a bit of direction on what to work on :)
Well, personally I think that trying tons of programs is the best way to start hacking on wine. That way you'll soon find a feature that's rather easy to implement/fix, and thus you'll gather more experience. See search.microsoft.com for docu.
Its also a good idea to hang out in #winehq on irc.openprojects.net, then you can nag the more experienced developers and pick up problems that people report and attempt to fix them :).
David
On Tue, 27 Nov 2001 11:19:01 +0100, Andreas Mohr wrote:
| On Mon, Nov 26, 2001 at 08:02:32PM -0500, Ryan C. Stallings wrote: | > Hello all, | > I am new to the wine scene and would like to try my hand at a little wine | > hacking. Are there any bugs out there that would be easy for a newbie to fix | > while letting me learn a bit about the inner workings of wine? I have read | > all the material about getting started developing, but I am just lacking a | > bit of direction on what to work on :) | Well, personally I think that trying tons of programs is the best way | to start hacking on wine. | That way you'll soon find a feature that's rather easy to implement/fix, | and thus you'll gather more experience. | See search.microsoft.com for docu. | | -- | Andreas Mohr Stauferstr. 6, D-71272 Renningen, Germany | Tel. +49 7159 800604 http://home.nexgo.de/andi.mohr/ | | | | |
"Ryan C. Stallings" wrote:
Hello all, I am new to the wine scene and would like to try my hand at a little wine hacking. Are there any bugs out there that would be easy for a newbie to fix while letting me learn a bit about the inner workings of wine? I have read all the material about getting started developing, but I am just lacking a bit of direction on what to work on :)
Thanks for your help, ryan
you can also look at François call for volunteers 3 months ago (I removed the part which have been worked on)
Easy:
* PrgWin95/98: System metrics differ from the Win9x values #48: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=48 One day I'll fix this one... I swear. Unless you want to work on it first. In that case I'll provide you with my test application and dumps of the metrics for Win95, Win98, NT4, 2000, ...
* The doc about the command line arguments and the config file is out of date. See TextCP, XVideoPort and Synchronous for instance. I'm sure there are plenty of other things that are out of date.
* Metabug: Test Wine with the Common Control Spy Samples #239: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=239 Get the Common Control Spy samples and test Wine with them. You will need the native comctl32 dll but you can do the tests without rebooting between each test or using two computers.
* PrgWin95: Listbox getting a recessed border instead of a flat one #56: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=56 (I can provide you with the sample application) This one my be fixed, to check...
* I think it would be nice to add a tool that displays the dlls version information like 'About' does in the windows explorer. I have some code you could use as a starting point and I think it could be merged with winver. In fact this would be almost stabdard windows programming.
* Tabs are missing their inner border #243: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=243 There's a bug in the drawing of the border of the common control tabs. Fixing each of the four instances of the code is easy. It would be interesting to find a way to factorize some of this code.
Medium (I expect these would take longer or be a bit harder)
* Quickbooks Pro Timer does not accept date (GetCalendarInfoA error) #276: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=276 GetCalendarInfoA/W are not implemented yet. They involve quite a lot of internationalisation aspects, but providing a first implementation that at least handles the common cases should be feasible.
* CreateIcon does not resize bitmaps #175: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=175 I did a similar fix somewhere some time ago. I can provide a sample application and I might be able to point you in the right direction.
* winemaker: 'winemaker --nomfc' does not have the intended effect #227: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=227
* winemaker: Ignores the '--with-{mfc,wine}' options once they are cached #225: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=225 If you're familiar with autoconf and know how configure scripts should behave...
* StrokePath ignores PS_JOIN_xxx #11: http://wine.codeweavers.com/bugzilla/show_bug.cgi?id=11 This should not be too difficult to fix but it would certainly help if you are familiar with GDI.
* Checking the differences between what's in the Windows dlls and what's in our spec files... and fix the contents of our spec files as appropriate. I already have a list of all the APIs in each of the dlls for Win95, Win98, NT4 and Wine2000, plus a script that can show the differences.
* Enhancing the above perl script. In particular it could be made smarter wrt. detecting whether an API is exported by ordinal or not.
A+
-
Andreas Mohr -
David Hammerton -
eric pouech -
Ryan C. Stallings