March 2006 - Wine-Devel - list.winehq.org

Re: Update on Software Freedom Law Center work

by Mike Hearn

> There will also be the possibility of assigning our copyrights to that > organization, which would make it easier to enforce the license Copyright assignment in other projects has been tricky, and it can't be done retroactively. It usually requires developers to submit paperwork - we don't really want that .... do we? thanks -mike

March 31, 2006

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

by Alexandre Julliard

Mike Hearn <mike(a)plan99.net> writes: >> Not to mention that SCHED_FIFO requires root, which is an absolute PITA. > > Not really. > > su -c 'wine IG2.exe' > > It's not all that inconvenient :) Until it crashes your box of course... I really don't think we want to encourage running as root, or give Windows apps a way to screw up the system. If we have to require people to upgrade their kernel to get the feature that's fine; at least then when the box dies we can blame the kernel guys ;-) -- Alexandre Julliard julliard(a)winehq.org

March 31, 2006

Update on Software Freedom Law Center work

by Alexandre Julliard

Folks, As announced at the last Wineconf, Jeremy and myself have been working for a few months now with the Software Freedom Law Center on a number of legal issues concerning Wine. We've been mostly quiet about it, so I thought I'd post a status update. There are two major tasks going on at the moment: 1. Code audit We are doing an audit of the code base, to make sure we have proper records of all contributions, and spot any potentially troublesome code. The goal is to be able to show to people who don't want to dig through the source that we have done our development properly, and that they can use Wine without fear of legal trouble. Currently, a survey is being sent out to people we have identified as major contributors, so that we can collect some information from them, like employers, license agreements, that sort of thing. This will enable us to build a complete track record for all contributions. We are still processing the results, at this point the responses we received cover approximately half of the code base (many thanks to everybody who took the time to answer!). We'll be sending the survey to more contributors in the near future to try to get as close to 100% coverage as we can. 2. Non-profit organization There are many advantages to having a non-profit organization for a project, for instance to allow tax-exempt donations, or hold assets like trademarks. However it's a lot of paperwork to do, so we never went to the trouble of setting one up. Now the SFLC is starting an organization called the Software Freedom Conservancy, that will be officially launched on Monday. It's basically an umbrella non-profit that provides services to free software projects. By joining that organization, we will get all the advantages of having our own non-profit, without having to do any of the work, so that seems like a good deal... There will also be the possibility of assigning our copyrights to that organization, which would make it easier to enforce the license, and provide some liability protection for developers. However this will only be done if most developers are comfortable with it, so I'd be interested to hear your feedback on this issue. -- Alexandre Julliard julliard(a)winehq.org

March 31, 2006

Re: Keyboard Rewrite

by Willie Sippel

Am Freitag, 31. März 2006 21:33 schrieb Tom Spear: > Hi all, this is a call for volunteers. I am hoping that certain developers > participating in another thread are willing to rewrite the keyboard code, > but we need people to test. If you are interested, please reply here > saying that you are interested, and what kind of keyboard you use, as well > as the layout you use under X. I will be creating a wiki page for this > project once the people who will be taking on this rewrite confirm that > they will do so, and will post the link to this thread as soon as it is > created. > > The purpose of this rewrite is to (hopefully) fix all of the problems > people have with key mappings, characters not showing up as expected, race > conditions, characters not showing up at all, etc, and hopefully allow us > to close out many of the bugs in bugzilla having to do with the keyboard. > > Thanks all in advance > > Tom If this is about testing, I'll gladly help. I use a German SUN Type6 keyboard (only one control key, Compose key, SUN keys instead of Windows keys, no menu key) with German layout and swapcaps. I also used to use an application that crashes due to a regression in Wine's keyboard handling it seems - could be a nice test app. -- Willie Sippel //////// | Tritium Studios // | ______________________________ //// /// | http://www.tritium-studios.com <willie(a)froq.net>

March 31, 2006

Re: Implement THREAD_PRIORITY_TIME_CRITICAL

by Mike Hearn

On Fri, 31 Mar 2006 15:21:51 +0200, Andreas Mohr wrote: > IMHO we should really add some smart detection of SCHED_ISO kernel capability > and *much* prefer to use that one then. One really wouldn't want to hang > the box... Sure, feel free to add it after this basic universal support has gone in :) Right now SCHED_ISO is only available in the -ck kernels right? > Not to mention that SCHED_FIFO requires root, which is an absolute PITA. Not really. su -c 'wine IG2.exe' It's not all that inconvenient :) > Nice To Have would be support for stuff such as SCHED_IDLEPRIO and > SCHED_BATCH... Sure. But for now this will start off OK. > Make that > static int already_warned; /* static: = 0! */ > > Since static uses 0 as default and you don't want to waste space in the > .bss(?) segment for an explicit 1 init. Good catch. Alexandre, could you modify that as you commit? thanks -mike

March 31, 2006

Re: Keyboard Rewrite

by Molle Bestefich

I have a couple of Danish keyboards. I'll gladly spend some time testing with those. (I even have one with A1-A4 keys...)

March 31, 2006

Keyboard Rewrite

by Tom Spear

Hi all, this is a call for volunteers. I am hoping that certain developers participating in another thread are willing to rewrite the keyboard code, but we need people to test. If you are interested, please reply here saying that you are interested, and what kind of keyboard you use, as well as the layout you use under X. I will be creating a wiki page for this project once the people who will be taking on this rewrite confirm that they will do so, and will post the link to this thread as soon as it is created. The purpose of this rewrite is to (hopefully) fix all of the problems people have with key mappings, characters not showing up as expected, race conditions, characters not showing up at all, etc, and hopefully allow us to close out many of the bugs in bugzilla having to do with the keyboard. Thanks all in advance Tom

March 31, 2006

Re: [Bug 1181] Keyboard translation broken: uses raw keycodes

by Tom Spear

On 3/31/06, Augusto Arcoverde da Rocha <agarobr.listas(a)gmail.com> wrote: > > On 3/30/06, Peter Åstrand <astrand(a)cendio.se> wrote: > > > > On Thu, 30 Mar 2006, Wine Bugs wrote: > > > http://bugs.winehq.org/show_bug.cgi?id=1181 > > > > > > ------- Additional Comments From Speeddymon(a)gmail.com 2006-30-03 > 10:26 ------- > [cut] > I don't know the problem with the bug 4923 [1], but when we fix the > bug 1181 [2] and make Wine use KeySym, this race condition won't occur > since X11DRV_ToUnicodeEx function will not use AltGrMask or any other > global variable concerning the keyboard state, only a table like > "ksym2vkey". Besides, applications that use X server API directly > don't have this behavior. > --- > [1] http://bugs.winehq.org/show_bug.cgi?id=4923 > [2] http://bugs.winehq.org/show_bug.cgi?id=1181 > > I'm trying to solve the bug 2400 [3] and looking more closely the code > in dlls/x11drv/keyboard.c I started thinking in rewriting this code to > use directly keysyms sent by X server to translate XEvents to vkeys > instead of the currently > "xevent->keycode->keysym->keycode->vkey/character" way as implemented > from the X11DRV_KeyEvent to X11DRV_ToUnicodeEx functions. > --- > [3] http://bugs.winehq.org/show_bug.cgi?id=2400 > > I think that rewriting the keyboard code in this way is a very good thing, and will be more than happy to help coordinate testing of it, although I can't test any myself. Rewriting the code should allow us to close many of the keyboard related bugs in bugzilla, which will be a big BIG plus in my book. Like I said, if you want me to, I will coordinate testing of new code. I'll start a new thread called keyboard rewrite and ask for volunteers with different keyboard layouts to reply to that thread to test new code. I'm also going to create an offspring of the main wiki page for this project, once given confirmation that you will do the rewrite. Tom

March 31, 2006

Re: Photoshop plugins in Gimp on Linux using Wine!

by Kuba Ober

On Friday 31 March 2006 10:24, Dan Kegel wrote: > On 3/31/06, Dan Kegel <dank(a)kegel.com> wrote: > > > > Incidentally, the port of PSPI used winelib for no obvious reason. > > > > Wouldn't it have been more robust just to use Wine? > > > > > > But it is using wine, that's what Winelib does :) [. . .] > > If a distribution ships this and a matching copy of Wine, > > and stays up to date, perhaps. > > A worse problem is that PSPI can't be built without > a closed source, non-redistributable SDK (IIRC). You're correct. Someone needs to start a project to write an open source replacement for that SDK, then. I hope it's less of a job than say wine is :) Probably whoever has that SDK could write documentation for the underlying API, someone else would write the headers, link libs and whatever glue code needed, and would post it under BSD or somesuch. Cheers, Kuba

March 31, 2006

Re: getwinegit.sh 0.31 released!

by Christian Lachner

There will be a new version soon since i found some things to change. What can you expect: All stdout and stderr gets into the logfile. (expecting getwinegit.sh's outputs) some small improvements :) greets On 3/29/06, Christian Lachner <gladiac.lists(a)gmail.com> wrote: > OK, I'm tired now but this is a new release an it owns ;). It should > be quite stable but I didn't test it. So what has changed: > > 0.31 One more Release, I'm glad about this one > - Some smaller an greater Fixes > - After Compiling, the Script creates a helperfile to help mode 4 > - Sections in Logfile > - Trap included to handle ctrl+c > - Implemented a small sleeper to give you a chance to stop the > script before it starts to clean the source > > This is one of the last versions. The last version will be called 1.0. > (maybe the next one?) > > If you miss a feature... write to the mailinglist. > > >

March 31, 2006