January 2009 - Wine-Devel - list.winehq.org

Re: Contribution to the Toolbar common control

by Alan Feldman

:-) Happy New Year to all, Alan Feldman On Wed, Dec 31, 2008 at 9:13 PM, Austin English <austinenglish(a)gmail.com> wrote: > On Wed, Dec 31, 2008 at 6:53 PM, Alan Feldman <alanfeld(a)gmail.com> wrote: >> Ouch Austin. But thanks Ricardo for explaining to Austin that I wasn't >> actually contributing "code" and I also didn't use any reverse >> engineering to come up with that discovery. > > Didn't mean for it come off as harsh. I know that wasn't code, but I'm > not sure how much he can contribute, having seen the disassembly. > > That said, the information is appreciated, and hopefully someone can > put it to use. > > Thanks for helping wine! > -- > -Austin >

Jan. 1, 2009

Re: Commit stats

by Eric Pouech

Hans Leidekker a écrit : > $ for year in {2002..2008}; do \ > count=$( git log | grep ^Date: | grep $year | wc -l ); \ > echo "Number of commits in $year: $count"; \ > done > Number of commits in 2002: 3094 > Number of commits in 2003: 3283 > Number of commits in 2004: 3851 > Number of commits in 2005: 6006 > Number of commits in 2006: 8431 > Number of commits in 2007: 9532 > Number of commits in 2008: 11292 > > -Hans > > > > > digging a bit deeper: for year in {2002..2008}; do \ count=$( git log | grep -2 -e "^Date.*$year" | grep ^Author: | sed -e 's/<.*>//' | LC_ALL=C sort -u -f | wc -l ); \ echo "Number of committers $count in year: $year"; \ done Number of committers 185 in year: 2002 Number of committers 166 in year: 2003 Number of committers 183 in year: 2004 Number of committers 211 in year: 2005 Number of committers 197 in year: 2006 Number of committers 217 in year: 2007 Number of committers 234 in year: 2008 of course, this doesn't take into account the different names used by the same person (ie there is for example a "frangois gouget" in the committers' list...) but this gives a good idea of the variation A+ -- Eric Pouech "The problem with designing something completely foolproof is to underestimate the ingenuity of a complete idiot." (Douglas Adams)

Jan. 1, 2009

Re: Commit stats

by Paul Vriens

Hans Leidekker wrote: > $ for year in {2002..2008}; do \ > count=$( git log | grep ^Date: | grep $year | wc -l ); \ > echo "Number of commits in $year: $count"; \ > done > Number of commits in 2002: 3094 > Number of commits in 2003: 3283 > Number of commits in 2004: 3851 > Number of commits in 2005: 6006 > Number of commits in 2006: 8431 > Number of commits in 2007: 9532 > Number of commits in 2008: 11292 > > -Hans > > I had a look at these stats as I'm (still) playing around with gitstat in combination with Wine. The numbers didn't match up so I had a closer look. 'git log' shows the author date and not the commit date. So maybe this one is more correct? $ for year in {2002..2008}; do \ count=$(git log --pretty='format:%cd' | grep $year | wc -l ); \ echo "Number of commits in $year: $count"; \ done Number of commits in 2002: 3094 Number of commits in 2003: 3283 Number of commits in 2004: 3851 Number of commits in 2005: 6006 Number of commits in 2006: 8404 Number of commits in 2007: 9540 Number of commits in 2008: 11307 Oh and btw, Happy New Year to all ! -- Cheers, Paul.

Jan. 1, 2009

Re: Drumming up qa publicity for sketchup on wine via Digg

by Roderick Colenbrander

> Sketchup seems to be working pretty well, so I just posted > http://digg.com/linux_unix/Google_Sketchup_7_working_in_Wine_1_1_11 > to see if I could attract some real sketchup users > to find more bugs. > > If folks agree that's a good idea, they can support it > by digging it so it can show up on the front page. > > Thanks, > Dan > It doesn't require opengl hacks in the form of registry settings like previous Sketchup versions? Roderick -- Sensationsangebot verlängert: GMX FreeDSL - Telefonanschluss + DSL für nur 16,37 Euro/mtl.!* http://dsl.gmx.de/?ac=OM.AD.PD003K1308T4569a

Jan. 1, 2009

Shell32 proxies/stubs

by Michael Karcher

Hello developers, this is just to let you know where the 3 standalone patches and three patch series I just posted to wine-devel are going: Having proxies for the COM objects of shell32.dll in actxprxy.dll, just as Windows XP and Vista does. It started with me wanting a guinea pig object that is apartment threaded and has proxies/stubs and present on every Windows installation to test a strange corner case in ole32. Looking around in my XP, I decided to use the MyComputer object that is already used in the ole32 testcase. Then I found out that Windows has them, but Wine misses them and thought to myself: Hey, this is just COM, adding a proxy should be just adding some lines to Makefile.in and widl does the rest. It turned out to be a quite fun project that revealed problems and/or missing features at nearly every component involved. The things I sent up to now fix most of the things below the proxies. What is still unsent is a three-patch-series to actxprxy to really add the proxies, and testcases for the remoting. While the shelllink testcase passes on my system even with remote calls, the shlfolder testsuite does not work correctly yet, revealing even more issues with ole32/widl I'm currently attacking. Regards, Michael Karcher

Jan. 1, 2009

Commit stats

by Hans Leidekker

$ for year in {2002..2008}; do \ count=$( git log | grep ^Date: | grep $year | wc -l ); \ echo "Number of commits in $year: $count"; \ done Number of commits in 2002: 3094 Number of commits in 2003: 3283 Number of commits in 2004: 3851 Number of commits in 2005: 6006 Number of commits in 2006: 8431 Number of commits in 2007: 9532 Number of commits in 2008: 11292 -Hans

Jan. 1, 2009

Drumming up qa publicity for sketchup on wine via Digg

by Dan Kegel

Sketchup seems to be working pretty well, so I just posted http://digg.com/linux_unix/Google_Sketchup_7_working_in_Wine_1_1_11 to see if I could attract some real sketchup users to find more bugs. If folks agree that's a good idea, they can support it by digging it so it can show up on the front page. Thanks, Dan

Jan. 1, 2009

Re: Contribution to the Toolbar common control

by Austin English

On Wed, Dec 31, 2008 at 6:53 PM, Alan Feldman <alanfeld(a)gmail.com> wrote: > Ouch Austin. But thanks Ricardo for explaining to Austin that I wasn't > actually contributing "code" and I also didn't use any reverse > engineering to come up with that discovery. Didn't mean for it come off as harsh. I know that wasn't code, but I'm not sure how much he can contribute, having seen the disassembly. That said, the information is appreciated, and hopefully someone can put it to use. Thanks for helping wine! -- -Austin

Jan. 1, 2009

Re: Contribution to the Toolbar common control

by Alan Feldman

Ouch Austin. But thanks Ricardo for explaining to Austin that I wasn't actually contributing "code" and I also didn't use any reverse engineering to come up with that discovery. All I did was go to Microsoft's MSDN Libary web site and compare the Toolbar messages listed there with the "publicly available" Microsoft header files (you guys do actually allow yourselves to visit Microsoft's MSDN Library every now and then and peruse Microsoft's publicly available header files don't you?). And I discovered that there were several Toolbar messages that were listed on the MSDN Library web site that were not listed in the publicly available header files. If you had actually gone to the web links I had listed before you would have seen text similar to the following at the bottom of each link: << This message is not included in a public header at this time. It is defined as WM_USER + 94. >> All I was trying to do was give you guys actual, "published" names from Microsoft for some constants you guys are using in your code so you didn't have to suffer from looking at names like TB_UNKWN45E rather than a much more meaningful and now published name of TB_SETHOTITEM2. I will list that information here again in case someone other than yourself finds the information of use. But I really don't care whether you make use of this discovery or not. I just figured since the code from your community helped me out, I would try to give something back to you guys. Take it and make use of it, or leave it. I really don't care. TB_UNKWN45E is really TB_SETHOTITEM2 (WM_USER + 94) TB_UNKWN460 is really TB_SETLISTGAP (WM_USER + 96) TB_UNKWN462 is really TB_GETIMAGELISTCOUNT (WM_USER + 98) TB_UNKWN463 is really TB_GETIDEALSIZE (WM_USER + 99) TB_UNKWN467 (which is not in the Wine source yet) is really TB_GETITEMDROPDOWNRECT (WM_USER + 103) http://msdn.microsoft.com/en-us/library/cc835036(VS.85).aspx http://msdn.microsoft.com/en-us/library/bb787441(VS.85).aspx http://msdn.microsoft.com/en-us/library/cc835034(VS.85).aspx http://msdn.microsoft.com/en-us/library/cc835033(VS.85).aspx http://msdn.microsoft.com/en-us/library/cc835035(VS.85).aspx Take care, and good luck, Alan Feldman "ricardo filipe" <ricardo_barbano(a)hotmail.com> wrote in message news:BAY118-W42006CA0FFCB83171C224783E40(a)phx.gbl... although he used disassembly to check our implementation, he gave msdn proof for the notifications he talked about... and didn't contribute code. On Wed, Dec 31, 2008 at 9:45 AM, Austin English <austinenglish(a)gmail.com> wrote: > On Wed, Dec 31, 2008 at 3:49 AM, Alan Feldman <alanfeld(a)gmail.com> wrote: >> Hello Wine developers, >> >> I am writing to this forum because I wanted to contribute some useful >> development information to your community while at the same time not >> have to get too involved as I currently have no plans to stay involved >> going forward. >> >> I wanted to say that I am *really* impressed with the codebase that >> you guys have developed! I stumbled across the Winehq site as I was >> looking for more information on Microsoft's Toolbar common control. >> The source code you guys have has made understanding the internals of >> the Toolbar control really easy and I really appreciate the work you >> guys have done. (I even took a peek at Microsoft's comctl32.dll >> disassembly to confirm a couple of the things you guys wrote and it >> checked out) ;-) > > Wine doesn't allow reverse engineering. Sorry, but you won't be able > to contribute code if you looked at its disassembly. > > -- > -Austin >

Jan. 1, 2009