October 2007 - Wine-Devel - list.winehq.org

Re: CSS changes to the Wiki

by Dimi Paun

On Fri, 2007-10-12 at 21:29 +0200, Kai Blin wrote: > > John Klehm pointed me at a post from Mitchell Mebane (at > http://www.winehq.org/pipermail/wine-devel/2007-August/058622.html) > > Someone care to give that a spin? I've implemented the feature, but I don't think it helps. Can someone test it out, and maybe suggest an alternate solution if problem still persists? -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

Oct. 12, 2007

stdout for win16 tests

by Dan Kegel

win16 doesn't have the notion of stdout/stderr, so 16 bit C compilers like watcom tend to simulate stdout by putting up a window. http://win16test.googlecode.com/svn/trunk/src/test.h (a port of the 32 bit test.h) uses freopen to open a log file to receive all the ok() and trace() output from the tests instead of letting it go to the fake stdout window. That's fine, but it means that crashes and wine output from wine itself don't get mixed in properly (since they go to linux stderr, not to win16 "stderr"). So I threw together a patch that uses the dos stdout that is shared by all win16 apps. Not sure if it's the right way to go, but it does let you use plain old redirection to capture the log messages, and it lets you redirect both test app traces and wine traces to the same file. I'm sending it to wine-devel mostly so Lei and anyone else working on the 16 bit tests can have a look. I haven't had a chance to pursue this further myself. - Dan -- Wine for Windows ISVs: http://kegel.com/wine/isv

Oct. 12, 2007

Re: imm32: Avoid spamming the debug output.

by EA Durbin

Imm is disabled by default on North American Windows installations. That's a behavior I think should be mimicked in wine. http://msdn2.microsoft.com/en-us/library/ms776161.aspx IMM is only enabled on East Asian (Chinese, Japanese, Korean) localized Windows operating systems. On these systems, the application calls GetSystemMetrics with SM_DBCSENABLED to determine if IMM is enabled. _________________________________________________________________ Peek-a-boo FREE Tricks & Treats for You! http://www.reallivemoms.com?ocid=TXT_TAGHM&loc=us

Oct. 12, 2007

Re: Support GCOV for Wine 1.0?

by Dimi Paun

On Fri, 2007-10-12 at 13:11 -0700, Dan Kegel wrote: > Font sizes change randomly based on previous lines. It's > unpredictable. True, but I'd argue that "total crap" is a bit harsh. In any event, this has nothing to do with the Wiki. It generates correct HTML (if anyone notices any problems, I'd be happy to fix it, but I've seen none AFAICT). The problem is with CSS + browsers. This is a nasty problem that is hard to deal with, no matter where you store the data. If people can help with the CSS problem, it would be much appreciated. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

Oct. 12, 2007

Re: Support GCOV for Wine 1.0?

by Dan Kegel

On 10/12/07, Dimi Paun <dimi(a)lattica.com> wrote: > On Fri, 2007-10-12 at 12:00 -0700, Scott Ritchie wrote: > > Make no mistake, what we have now is crap. It's a shame we show it to > > users when it's so laden with display bugs. > > I'm afraid I don't understand -- what is crap, and > where are the display bugs? Font sizes change randomly based on previous lines. It's unpredictable.

Oct. 12, 2007

Re: CSS changes to the Wiki

by Kai Blin

On Wednesday 10 October 2007 11:35:57 Kai Blin wrote: > Hi folks, > > I seem to remember that someone posted a patch to the wiki's CSS that will > stop the lists from looking ugly. I can't find that patch, though. > > Can someone point me at it? John Klehm pointed me at a post from Mitchell Mebane (at http://www.winehq.org/pipermail/wine-devel/2007-August/058622.html) Someone care to give that a spin? Cheers, Kai -- Kai Blin WorldForge developer http://www.worldforge.org/ Wine developer http://wiki.winehq.org/KaiBlin Samba team member http://www.samba.org/samba/team/ -- Will code for cotton.

Oct. 12, 2007

Re: Support GCOV for Wine 1.0?

by Dimi Paun

On Fri, 2007-10-12 at 12:00 -0700, Scott Ritchie wrote: > Make no mistake, what we have now is crap. It's a shame we show it to > users when it's so laden with display bugs. I'm afraid I don't understand -- what is crap, and where are the display bugs? -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

Oct. 12, 2007

Re: Support GCOV for Wine 1.0?

by Scott Ritchie

Dimi Paun wrote: > On Fri, 2007-10-12 at 10:47 -0700, Dan Kegel wrote: >> It'd be nice to have the best of both worlds, >> i.e. a wiki backed by git, and written >> in such a way that users who preferred to avoid >> online editing could use git to edit >> it locally, using an easy local preview tool, >> with strong formatting capabilities (like html) >> instead of the unhappy situation we have now, >> where formatting is an unreliable mystery. > > Yes, I've been dreaming for a long time after such > a system. There is a wiki out there that uses git > as backend, I forget the name now. But they need > more maturing. As for formatting, you don't want > to be too crazy, HTML is powerful but also verbose, > a wiki needs terse syntax, and that often comes > at the expense of seldom used formatting power. > That being said, I agree that it could be done a > bit better than what we have now. Make no mistake, what we have now is crap. It's a shame we show it to users when it's so laden with display bugs. > >> The other good thing about our wiki is that it >> has very good uptime and performance >> (thanks Dimi). > > Thank you Dan, I'm really glad to see people > use it, and they enjoy the experience. My hope > is that it will become even better going forward. > The wiki is still, however, amazingly awesome. Thank you, you're really on top of it :) Thanks, Scott Ritchie

Oct. 12, 2007

Re: Support GCOV for Wine 1.0?

by Dimi Paun

On Fri, 2007-10-12 at 10:47 -0700, Dan Kegel wrote: > It'd be nice to have the best of both worlds, > i.e. a wiki backed by git, and written > in such a way that users who preferred to avoid > online editing could use git to edit > it locally, using an easy local preview tool, > with strong formatting capabilities (like html) > instead of the unhappy situation we have now, > where formatting is an unreliable mystery. Yes, I've been dreaming for a long time after such a system. There is a wiki out there that uses git as backend, I forget the name now. But they need more maturing. As for formatting, you don't want to be too crazy, HTML is powerful but also verbose, a wiki needs terse syntax, and that often comes at the expense of seldom used formatting power. That being said, I agree that it could be done a bit better than what we have now. > The other good thing about our wiki is that it > has very good uptime and performance > (thanks Dimi). Thank you Dan, I'm really glad to see people use it, and they enjoy the experience. My hope is that it will become even better going forward. -- Dimi Paun <dimi(a)lattica.com> Lattica, Inc.

Oct. 12, 2007

Re: server: Use the security descriptor passed in when creating events.

by Robert Shearman

Alexandre Julliard wrote: > Robert Shearman <rob(a)codeweavers.com> writes: > >> Use a new object_attributes struct for passing the information about >> whether a security descriptor is specified or not to the server. >> > > This breaks Photoshop CS2, we segfault while trying to access a > security descriptor it gives us. > Thanks for catching this. I presume it occurs while running Photoshop CS2 and not during the install process. -- Rob Shearman

Oct. 12, 2007