Guidance :--- Its not completely wine configuration utility, but a generalpurpose system configuration utility for KDE. It now has got somemodule for configuring WINE also. I got this news from
http://dot.kde.org/1150047999/. I havent tested it, but it can be gotfrom here http
Hmm, Wine Doors looks pretty cool. At least, it seems to have a nice UI.
Though I question how much preset "profiles" can achieve these days ...
we're getting closer to not needing them all the time. Maybe if the
profiles can do things like install native MSI/DCOM/MDAC/InternetExplorer
etc it migh
installations, from screenshots i think so.
I got this news from here http://gnomedesktop.org/node/2689, and
more information can be got from its web site
http://www.wine-doors.org/
Guidance :
---
Its not completely wine configuration utility, but a general
purpose system configuration
ad to be changes with the winecfg tool
though. But seeing how the configuration now is plainy stuffed into the "normal"
registry, and how the important keys are simply get mixed up with other stuff
makes me wonder if it could be done otherwise. I also wondered why exactly the
registry is us
Oliver Stieber wrote:
Couldn't a macro or inline function be used, that way
there wouldn't be any additional linker dependencies.
Macros and inline functions are better than a function defined in a
library, but each one introduces a header dependency, so they should
also be avoided where po
--- Mike McCormack <[EMAIL PROTECTED]> wrote:
>
> Oliver Stieber wrote:
>
> > With a lot of wines configuration moving over to
> > HKEY_LOCAL_USER and magic comments being added to
> > identify places where configuration is read, I
> though
> > it may be a good idea to move over to a standard
>
Oliver Stieber wrote:
With a lot of wines configuration moving over to
HKEY_LOCAL_USER and magic comments being added to
identify places where configuration is read, I though
it may be a good idea to move over to a standard
function for reading configuration instead of using
direct registry acc
Hi,
With a lot of wines configuration moving over to
HKEY_LOCAL_USER and magic comments being added to
identify places where configuration is read, I though
it may be a good idea to move over to a standard
function for reading configuration instead of using
direct registry access.
Something like
James Hawkins <[EMAIL PROTECTED]> writes:
> This seemed to get pretty good support in wine-devel. The rest of the
> implementation will follow soon.
You really only want the dir symlink and hidden file options, and
these should most likely be under the Drives tab. It doesn't make
sense to let us
On Thu, 05 May 2005 08:43:00 -0400, Dimitrie O. Paun wrote:
> I think we intentionally omitted such a page before. The thinking
> is that these are really low-level settings that normal users shouldn't
> touch. Those who *need* to for whatever strange reason can use
> regedit to do so.
Yeah, I was
Maybe we can have an advanced options tab or something? I think it
would be useful for developers to be able to be able to adjust as many
useful options as possible without having to edit the registry
directly.
Chris
On 5/5/05, Dimitrie O. Paun <[EMAIL PROTECTED]> wrote:
> On Thu, May 05, 2005
On Thu, May 05, 2005 at 12:50:50AM -0500, James Hawkins wrote:
> I used the options specified for [wine] in the Wine Options Status
> page [1] to create a new wine options tab for winecfg.
I think we intentionally omitted such a page before. The thinking
is that these are really low-level settings
On Thu, May 05, 2005 at 12:50:50AM -0500, James Hawkins wrote:
> [1] http://winehq.org/site/status_options
I'm afraid this page is a bit out of date. It needs lots of
love, and I think it would be a worthwhile project to update it.
--
Dimi.
13 matches
Mail list logo
