Re: Lostwages: howto.diff

[Paul Vriens]

On Mon, 2005-08-15 at 08:44, Tom Wickline wrote:
> Hello All,
>
> We have moved to winecfg......
>
> Tom
>
> Changelog:
> spelling fix, doc update

Hi Tom,

you're patch shows:

-<p>Wine is currently in a transitionary phase. We are working on replacing the 
-cryptic configuration file with an easy to use graphical utility called winecfg.
-In the meantime, however, we recommend that you use a handy program called 
+<p>If your using an old version of Wine we recommend that you use a handy program called

As winecfg is currently THE tool why not refer to this (and maybe also to Winetools) this way more
and more people will use it (and make it better?).

Cheers,

Paul.

Lostwages: howto.diff

[Tom Wickline]

On 8/15/05, Paul Vriens  wrote:
> As winecfg is currently THE tool why not refer to this (and maybe also to Winetools) this way more
> and more people will use it (and make it better?).

for new versions of Wine winecfg is the default tool to setup/edit a setup.
So I figured most people would use it in new versions. There is the
possibility even probability new users won't know about winecfg... I
was just recommending WineTools for people still using older versions
of Wine. I'm sure the WineTools guys will fix there nifty tool to
comply with the changes that have taken place. And I will be editing
this page again to tell people to choose the front end of there
choice.

So do you think I should say if you use a version of Wine from
20050628 forward we recommend that you use winecfg, and for versions
older than 20050628 use WineTools?

Tom
> Cheers,
>
> Paul.

Lostwages: howto.diff

[Andreas Mohr]

Hi,

On Mon, Aug 15, 2005 at 05:39:39AM -0400, Tom Wickline wrote:
> On 8/15/05, Paul Vriens  wrote:
> > As winecfg is currently THE tool why not refer to this (and maybe also to Winetools) this way more
> > and more people will use it (and make it better?).
>
> for new versions of Wine winecfg is the default tool to setup/edit a setup.
> So I figured most people would use it in new versions. There is the
> possibility even probability new users won't know about winecfg... I
> was just recommending WineTools for people still using older versions
> of Wine. I'm sure the WineTools guys will fix there nifty tool to
> comply with the changes that have taken place. And I will be editing
> this page again to tell people to choose the front end of there
> choice.
>
> So do you think I should say if you use a version of Wine from
> 20050628 forward we recommend that you use winecfg, and for versions
> older than 20050628 use WineTools?

I'd do it like that. winecfg can make use of some good testing, so we
should "trick" people into using it...

Just try to make sure that people won't get the impression that WineTools is
simply a wine configuration tool, just like winecfg. It's a bit more than that,
with its extension package installation (MSI, ODBC, IE, ...)
and installation entries for common well-tested applications.

Andreas