[winecfg 1.1] Implement saveConfigValue(), style changes, code cleanup, UI alignment

Alexandre Julliard julliard at winehq.org
Thu Aug 28 13:02:45 CDT 2003

"Dimitrie O. Paun" <dimi at intelliware.ca> writes:

> Man, oh man, quite a bit of stuff. maybe we can get rid of some of them. :)
> Or maybe we don't need UI stuff for all of them. Even on Windows users
> have to use regedit from time to time, let's not try to be more catholic
> than the Pope. Alexandre, what's your minimal set of things for winecfg
> before we can do the switch?

Well, we need everything that normal users will want to use. But I
don't think the priority should be on switching to winecfg as soon as
possible; on the contrary we should take the time to review the
config, and use that opportunity to clean things up before we make the
switch. So for instance if some parameters are too obscure to justify
implementing them in winecfg, we should ask whether we really need
them in the config at all, or whether we could handle them somehow

Also we need to fix the code that uses config parameters to try to
take into account dynamic changes as much as possible, so that you can
make a change from winecfg and see it take effect at once, without
having to restart your Wine session.

Alexandre Julliard
julliard at winehq.com

More information about the wine-devel mailing list