Starter projects for new Wine contributors?
Hi all! I'm looking for suggestions for starter projects for new contributors that would take something like a week to do, and wouldn't require much knowledge of Wine ahead of time. http://wiki.winehq.org/TodoList is the place we've gathered that stuff, but nothing there really grabs me. I suppose the tasks http://wiki.winehq.org/CrossCallsWtoA http://wiki.winehq.org/ConstifyData http://wiki.winehq.org/SpecDiscrepencies might qualify. Do they still need doing? http://winehq.org/site/fun_projects has some cool stuff on it, particularly the idea of using Mono's libgdiplus to implement gdi+ in Wine. (That's probably more than a week's worth of work, though.) http://wiki.winehq.org/SummerOfCode has very cool stuff in it, but that's all about 100x times harder than what I'm looking for. And then there's riched20. It's missing quite a few little features; see the 11 open bugs here: http://bugs.winehq.org/buglist.cgi?product=Wine&component=wine-richedit&bug_... Might some of those be doable in a couple days? - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv
On Mon, 2006-01-09 at 16:36 -0800, Dan Kegel wrote:
http://wiki.winehq.org/TodoList is the place we've gathered that stuff, but nothing there really grabs me. I suppose the tasks http://wiki.winehq.org/CrossCallsWtoA http://wiki.winehq.org/ConstifyData http://wiki.winehq.org/SpecDiscrepencies might qualify. Do they still need doing?
Absolutely. It would be great if we can finally get them over with. Not so sure about ConstifyData, but there we either need to get rid of it if nothing is left to do, or provide a comprehensive list of what is to be done like we do in the other cases, so we have a better feel of the scope and magnitude of the task.
http://winehq.org/site/fun_projects has some cool stuff on it, particularly the idea of using Mono's libgdiplus to implement gdi+ in Wine. (That's probably more than a week's worth of work, though.)
This should really be moved to the Wiki :).
And then there's riched20. It's missing quite a few little features; see the 11 open bugs here: http://bugs.winehq.org/buglist.cgi?product=Wine&component=wine-richedit&bug_... Might some of those be doable in a couple days?
Yes, I think so. From past experience, once you get past the first few days of understanding what is going on, you can fix/implement a lot of these little features. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.
On 1/9/06, Dan Kegel <dank(a)kegel.com> wrote:
Hi all! I'm looking for suggestions for starter projects for new contributors that would take something like a week to do, and wouldn't require much knowledge of Wine ahead of time.
Tests! Pretty much any level of C programmer (even me!) could whip out a test for any Win32 API they care about and provide something useful within a few minutes to an hour. I'm still mostly lurking but I might have a few tests to post in the future. It's just the easiest thing to do to get developers to look at problems I'm running into but don't quite know how to fix. Once I make a test that a more seasoned wine developer can use to accelerate their work, it's more likely they'll fix it (and keep it that way). http://www.winehq.org/site/docs/winedev-guide/testing -Al Tobey
http://wiki.winehq.org/TodoList is the place we've gathered that stuff, but nothing there really grabs me. I suppose the tasks http://wiki.winehq.org/CrossCallsWtoA http://wiki.winehq.org/ConstifyData http://wiki.winehq.org/SpecDiscrepencies might qualify. Do they still need doing?
http://winehq.org/site/fun_projects has some cool stuff on it, particularly the idea of using Mono's libgdiplus to implement gdi+ in Wine. (That's probably more than a week's worth of work, though.)
http://wiki.winehq.org/SummerOfCode has very cool stuff in it, but that's all about 100x times harder than what I'm looking for.
And then there's riched20. It's missing quite a few little features; see the 11 open bugs here: http://bugs.winehq.org/buglist.cgi?product=Wine&component=wine-richedit&bug_... Might some of those be doable in a couple days? - Dan
-- Wine for Windows ISVs: http://kegel.com/wine/isv
On 1/9/06, Al Tobey <tobert(a)gmail.com> wrote:
On 1/9/06, Dan Kegel <dank(a)kegel.com> wrote:
Hi all! I'm looking for suggestions for starter projects for new contributors that would take something like a week to do, and wouldn't require much knowledge of Wine ahead of time.
Tests!
I agree completely. Testing the API is especially relevant for win32 developers, because they're coding an API they're familiar with. Even if a new developer has little programming experience, win32 or otherwise, tests are a great place to start. It helps the new developers by familiarizing them with the particular API they are testing, and it sheds light for not only wine developer's, but anyone who references wine as a source of win32 API information. Tests verify our implementation of the API, and make sure no regressions sneak into the code. -- James Hawkins
Am Montag, den 09.01.2006, 21:02 -0500 schrieb Al Tobey:
I'm looking for suggestions for starter projects for new contributors that would take something like a week to do, and wouldn't require much knowledge of Wine ahead of time.
Tests!
Another way is: Fixing Tests, that currently fail on Windows. Test-Results: http://test.winehq.org/data Binaries: http://www.astro.gla.ac.uk/users/paulm/WRT/CrossBuilt/ The MinGW Cross-Compiler is used to build the Binaries I'm building native Windows-EXE using the Cross-Compiler-Packages from Hans ( http://mirzam.it.vu.nl/mingw/ ) A recent Example was the failure of "ntdll.dll:exception" on Win95-WinME - Run the Test on Windows to find the Problem - Fix the Problem - Build and run the Wine-Test: "make -C dlls/ntdll/tests/ test" - Build the Windows Test: "make -C dlls/ntdll/tests/ crosstest" - Run "ntdll_crosstest.exe" on all available Windows-Versions (I'm using qemu for this) - Create the "useful_name.diff" - Mail the Patch to wine-patches - Wait for Commit
-- By By ... ... Detlef
participants (5)
-
Al Tobey -
Dan Kegel -
Detlef Riekenberg -
Dimi Paun -
James Hawkins