Winecfg contains potentially harmful configuration parameters (like native overrides) and are shown in the same way as useful configuration parameters like windows version or virtual desktop. Maybe creating a box where a user can select it's level of knowledge in wine and hide part of the interface accordingly. It could also be used to show warning informations when changing this level for the first time, for instance one saying to not link wine and a real windows installation when activating the folder tab or one explaining that overrides are "bad" This might warn users playing with the buttons that it might break more things than it will solve and keep some of them from breaking there wine installation. (or putting par of winecfg in another command like winecfg-wineguru ^^)
On Mon, May 12, 2008 at 8:56 PM, Tlarhices <wineforum-user at winehq.org> wrote:> It could also be used to show warning informations when changing this level for the first time, for instance one saying to not link wine and a real windows installation when activating the folder tabWe already do this.> > This might warn users playing with the buttons that it might break more things than it will solve and keep some of them from breaking there wine installation. > > (or putting par of winecfg in another command like winecfg-wineguru ^^) >Patches are welcome.
austin987 wrote:> On Mon, May 12, 2008 at 8:56 PM, Tlarhices <wineforum-user at winehq.org> wrote: > > > It could also be used to show warning informations when changing this level for the first time, for instance one saying to not link wine and a real windows installation when activating the folder tab > > > We already do this. >Strange, for me the only thing like this contains the serial number of the drives and there type. It's true that c: can't be changed this easily but nothing for native overrides. austin987 wrote:> > > > > > This might warn users playing with the buttons that it might break more things than it will solve and keep some of them from breaking there wine installation. > > > > (or putting par of winecfg in another command like winecfg-wineguru ^^) > > > > Patches are welcome.For patches, you have to know how to program in C or to try to make someone that can program in C aware of this.
Tlarhices wrote:> This might warn users playing with the buttons that it might break more things than it will solve and keep some of them from breaking there wine installation. >If users don't get that they shouldn't be changing something they don't know - then they will learn the hardway. Nothing wrong about that. Only dumb people won't learn from their mistakes.