August 2003 - Wine-Devel - list.winehq.org

Re: listview expert required

by Dimitrie O. Paun

On Fri, 29 Aug 2003, Rein Klazes wrote: > Hi Dimitrie, > > This is causing a regression in newsbin pro. > > New postings are highlighted by a green background colour. With the > patch the text in the second and higher columns is painted with a normal > backgound colour instead of green. > Selected rows are OK. Can you give this a try please and tell me if it works: Index: dlls/comctl32/listview.c =================================================================== RCS file: /var/cvs/wine/dlls/comctl32/listview.c,v retrieving revision 1.359 diff -u -r1.359 listview.c --- dlls/comctl32/listview.c 25 Aug 2003 23:44:51 -0000 1.359 +++ dlls/comctl32/listview.c 29 Aug 2003 20:13:33 -0000 @@ -3565,7 +3565,8 @@ cdsubitemmode = notify_customdraw(infoPtr, CDDS_PREPAINT, &nmlvcd); if (nSubItem == 0) infoPtr->cditemmode = cdsubitemmode; if (cdsubitemmode & CDRF_SKIPDEFAULT) goto postpaint; - prepaint_setup(infoPtr, hdc, &nmlvcd); + if (nSubItem == 0 || (cdmode & CDRF_NOTIFYITEMDRAW)) + prepaint_setup(infoPtr, hdc, &nmlvcd); /* in full row select, subitems, will just use main item's colors */ if (nSubItem && uView == LVS_REPORT && (infoPtr->dwLvExStyle & LVS_EX_FULLROWSELECT)) Thanks! -- Dimi.

Aug. 29, 2003

Re: Figuring runtime settings

by puoti＠inwind.it

Maybe you're looking for this: http://appdb.winehq.com

Aug. 29, 2003

Figuring runtime settings

by James E. LaBarre

I've been able to find a lot of pages on how to run debug commands when trying to run WinApps, but they all seem to be oriented towards programmers working on modifying the code. I'm not a programmer, so my work would be more towards trying to figure out what combination of native vs builtin DLLs to use, what other DLLs I need to track down, what registry entries to modify, etc. For example; one of the apps I'd need to figure out is eBay's TurboLister (sometimes known as TurtleLister or TurdLister; it's for posting ebay auctions). I know it needs MSIE, but beyond that it still has other problems. I managed to get the install to run under Crossover Office, but then it crashes about 1 minute into using it. So what I need is a site with information on how to kludge an installation to run some particular app.

Aug. 29, 2003

Re: listview expert required

by Dimitrie O. Paun

On Fri, 29 Aug 2003, Rein Klazes wrote: > New postings are highlighted by a green background colour. With the > patch the text in the second and higher columns is painted with a normal > backgound colour instead of green. > Selected rows are OK. OK, I think I know what the problem is, I'll fix it when I get home. -- Dimi.

Aug. 29, 2003

Re: Wine 0.9 progress

by Ferenc Wagner

Francois Gouget <fgouget(a)free.fr> writes: > Do we really need a C program, a new mailing list, > automated result submission, generating HTML and now a > database just so we have something that says: > > Test | Result > ----------+--------- > kernel32 | Passed > msvcrt | Passed > oleaut32 | Passed > dsound | Passed > ... We want a little bit more than this... but I think you are right. > This all seems very much over-engineered to me. I'd really > like to see that kind of energy spent on fixing the tests > so that they actually work on Windows. I would like to. I spent some patches against the tests, and they were refused because somebody remembered something. Now I need FACTS, and since nobody seemed to provide me with facts, I try to do something about that. I still can not say that results are pouring in :) Now I also produced Makefiles, by the way... Feri.

Aug. 29, 2003

Re: Wine 0.9 progress

by Francois Gouget

On Fri, 29 Aug 2003, Dimitrie O. Paun wrote: > On August 28, 2003 06:30 pm, Jeremy Newman wrote: > > Sure, if that is the address you want for the list I can probably put it > > up tomorrow sometime. I just want to be very sure before I start work on > > it. > > Well, wine-tests-results(a)winehq.org is OK AFAICT. Are there better > proposals? [...] > No need for PHP -- the page will be static HTML generated externally > through a Perl script I'd guess. We'll have to figure a way of integrating > the above list with such a script. I'm wondering if we don't need a DB > in the middle, something like so: > > wine-tests-results --> parser --> DB --> generator --> .template > > Something like MySQL should do, but it's a non-trivial setup. Do we really need a C program, a new mailing list, automated result submission, generating HTML and now a database just so we have something that says: Test | Result ----------+--------- kernel32 | Passed msvcrt | Passed oleaut32 | Passed dsound | Passed ... This all seems very much over-engineered to me. I'd really like to see that kind of energy spent on fixing the tests so that they actually work on Windows. -- Francois Gouget fgouget(a)free.fr http://fgouget.free.fr/ Linux: the choice of a GNU generation

Aug. 29, 2003

Re: listview expert required

by Rein Klazes

On Sun, 24 Aug 2003 19:34:36 -0400, you wrote: > On August 24, 2003 05:44 pm, Dimitrie O. Paun wrote: > > Yes, this patch broke selection drawing: > > > > http://www.winehq.org/hypermail/wine-cvs/2003/04/0243.html > > > > <blush>It's my patch, mea culpa</blush>. > > Yeah, at a second look, it was rather obvious what went wrong. > > ChangeLog > Always setup the selection colour, not just in custom draw. > > Index: dlls/comctl32/listview.c > =================================================================== > RCS file: /var/cvs/wine/dlls/comctl32/listview.c,v > retrieving revision 1.357 > diff -u -r1.357 listview.c > --- dlls/comctl32/listview.c 24 Jul 2003 00:03:13 -0000 1.357 > +++ dlls/comctl32/listview.c 24 Aug 2003 23:30:31 -0000 Hi Dimitrie, This is causing a regression in newsbin pro. New postings are highlighted by a green background colour. With the patch the text in the second and higher columns is painted with a normal backgound colour instead of green. Selected rows are OK. Rein. -- Rein Klazes rklazes(a)xs4all.nl

Aug. 29, 2003

Re: Wine 0.9 progress

by Ferenc Wagner

Hello guys, some machinery is already in place (http://afavant.elte.hu/~wferi/wine) Actually I am not sure we need a database or so. What I have in mind: Whenever somebody compiles the tests (with a Samba mount it does not matter whether cross- os MSVC) s/he runs the ziptests Bash script to produce a tests.zip, and we collect it somewhere tagged by the date, eg. 20030828. People download it, do their job, and send the report to the list. If the report is identical (modulo a couple of lines which contain the current working directory and similar -- just egrep -v it) to another for the same build and Windows version, we just acknowledge the name. If it is always the case, then forget it. If not, we may need a subarchitecture or a better egrep pattern, this is manual. For a new set of data, we run the dissect Perl script, which gives a summary and one report file for each test. No need to rerun this ever. The gather script assembles the summaries for the various architectures into a summary table, with links to the small report files. Rerun when a new architecture is added for this build. We can have on directory for each build tag (like 20030828), and separate directories for each architecture in them. gather dissect works here works here ,- win95 | ,- 20030828 -+-- nt4.0 | | | `- XP index.html -+ | ,- win98 | | `- 20030914 -+-- nt4.0 | `- XP We can also have a 'latest' directory which simply links to the appropriate architecture subdirectories, and we can also gather a summary there. All the pages are static, and you can select on the main page. Find the scripts attached. I do not really want to go further until I know where/how they will run. The desing is not finished :) Feri.

Aug. 29, 2003

Re: Wine 0.9 progress

by Dimitrie O. Paun

On 29 Aug 2003, Jeremy Newman wrote: > > -- Jeremy, are you OK with setting up a simple database for > > this stuff? If so, we need to figure out a schema. > > Mysql is already on the machine, so that is fine. My concern is DB bloat > over time. Will this DB get out of control or will it remain a fixed > size? I will grow, as new tests are added to the database. We can have a monthly cleanup task to get rid of old tests (and maybe remember some fun stats while we're at it). > > -- We need to run the generator either from time to time, > > or when the DB gets updated. Any preference? > > Cron, or during the monthly build. Monthly build is preferred IMO. I'm > jumpy about giving out any further shell access to the box. There's no need for shell access -- we just need to trigger the scrip. Doing it once per month is a bit too seldom. We can run the script every day, and make it smart to not do anything if the DB has not been updated. This is easy to do. > > -- Once you have the .template, what does it need to happen > > to have it appear on WineHQ? > > Just needs to be in the templates/en dir somewhere, it can be another > level deep as well. I can provide the full path to whoever writes this > script. Perfect. As long as we don't have to put it in CVS, things are simple. The best would be for the script to just output to stdout, and you redirect that where you need to when you install it. -- Dimi.

Aug. 29, 2003

Re: Wine 0.9 progress

by Jeremy Newman

On Fri, 2003-08-29 at 07:35, Dimitrie O. Paun wrote: > On August 28, 2003 06:30 pm, Jeremy Newman wrote: > > Sure, if that is the address you want for the list I can probably put it > > up tomorrow sometime. I just want to be very sure before I start work on > > it. > > Well, wine-tests-results(a)winehq.org is OK AFAICT. Are there better > proposals? > > > Not sure how you want to accomplish this, but integrating it into the > > site should not be hard, if the output is generated using the .template > > spec of the lostwages engine. If it need to be more dynamic than that, > > some PHP work will be involved. > > No need for PHP -- the page will be static HTML generated externally > through a Perl script I'd guess. We'll have to figure a way of integrating > the above list with such a script. I'm wondering if we don't need a DB > in the middle, something like so: > > wine-tests-results --> parser --> DB --> generator --> .template > > Something like MySQL should do, but it's a non-trivial setup. > We need to figure out a few things: > -- how do we trigger the parser based on email comming in > from the list. Maybe run it as a user, and have things > done through procmail. It can work similar to how the mailman works, you have the script parse from /etc/aliases. .procmail would work as well. > -- Jeremy, are you OK with setting up a simple database for > this stuff? If so, we need to figure out a schema. Mysql is already on the machine, so that is fine. My concern is DB bloat over time. Will this DB get out of control or will it remain a fixed size? > -- We need to run the generator either from time to time, > or when the DB gets updated. Any preference? Cron, or during the monthly build. Monthly build is preferred IMO. I'm jumpy about giving out any further shell access to the box. > -- Once you have the .template, what does it need to happen > to have it appear on WineHQ? Just needs to be in the templates/en dir somewhere, it can be another level deep as well. I can provide the full path to whoever writes this script. -- Jeremy Newman <jnewman(a)codeweavers.com> CodeWeavers, Inc.

Aug. 29, 2003