[RFC] winecfg enhancements
Hi, I am looking at how we can make winecfg more useful. I have already supplied patches to allow importing a ubuntu human theme to work :). So I am now looking at how to build on that. On the Desktop Integration tab, I am planning on adding the following improvements: * Split the Appearance section into Theme and Appearance. The rationale behind this is while the two are linked, they are also distinct. It will make it possible to simplify "Install theme..." to just "Install...", and support enhancements below. * Pre-populate the Theme list with themes in WINDOWS/Resources/Themes and with other *.theme files added by the user. The rationale behind this is that it simplifies the workflow for the average usage (e.g. install a theme, then select it). * Rename "Install theme..." to "Add...". The rationale is that we are not installing a theme, but setting it as the theme being used. Having the theme appear in the Themes list in the future further supports this name change and workflow. * Rename "(No Theme)" to "Wine Default". The rationale behind this is that it isn't true that there is no theme installed (in the sense that a theme can be a set of colours and metrics). * Provide an "Export..." button to the Themes section. The rationale behind this is that it makes it easier to create, modify and preview themes being created. Therefore, you could create a Ubuntu Human or Oxygen theme from winecfg. * Make the theme importer read the themes [Theme]/DisplayName property. The rationale behind this is to make the display name user friendly. * Add --import-theme command line support to winecfg. The rationale behind this is to support loading a theme via a script (e.g. post-install configuration), without resorting to the winecfg GUI. * Make the shell folders a drop down list. The rationale behind this is that it is unclear what "link to" applies to. An alternative is to make the listview have the showselalways flag, so it is clearer what folder "link to" is relating to. Q: Should we provide a --simple mode for winecfg that has the work flow that Ubuntu is planning? Not specifying --simple would bring up the standard winecfg dialog. - Reece
Q: Should we provide a --simple mode for winecfg that has the work flow that Ubuntu is planning? Not specifying --simple would bring up the standard winecfg dialog.
If you don't explain what that is, don't expect to many responses. At least, I don't know what it is. --Juan
On 13/02/2008, Juan Lang <juan.lang(a)gmail.com> wrote:
Q: Should we provide a --simple mode for winecfg that has the work flow that Ubuntu is planning? Not specifying --simple would bring up the standard winecfg dialog.
If you don't explain what that is, don't expect to many responses. At least, I don't know what it is.
From https://wiki.ubuntu.com/BetterIntegratedWineSpec: <quote> System->Preferences->Windows Applications
Here we reimplement only the Wine configuration options we need. * (Pulldown menu): "Default Windows version to emulate when launching Windows applications" o Windows 2000 is currently the upstream default, which works for most apps * (unchecked by default) Automatically launch applications upon inserting a disc o This is where the user can disable autorun by default if he enabled it with the checkbox in the autorun prompt * (radio button default): Allow full screen applications to change the resolution * (radio button alternate): Contain full screen applications in a window when smaller than the desktop o These are the two main use cases of Wine's various Window managing options. The latter might not be fully functional in time for Hardy. * (button) Advanced o Launches winecfg, or a similarly functional GTK application. We can consider removing this when Wine's defaults get good enough, however likely not by Hardy. To reimplement the configuration we need in GTK requires some upstream changes (see [WWW] ConsoleConfiguration on Wine's wiki. </quote> And the other proposed improvements? Those were mentioned and can be commented on. - Reece
On Feb 13, 2008 2:29 PM, Reece Dunn <msclrhd(a)googlemail.com> wrote:
And the other proposed improvements? Those were mentioned and can be commented on.
I've skimmed the discussion and while its important to me it bears much too verbose. Can we just get some mockup images of that the proposed changes would look like? -- Steven Edwards "There is one thing stronger than all the armies in the world, and that is an idea whose time has come." - Victor Hugo
Reece Dunn <msclrhd <at> googlemail.com> writes:
Hi,
I am looking at how we can make winecfg more useful. I have already supplied patches to allow importing a ubuntu human theme to work :). So I am now looking at how to build on that.
[...]
- Reece
I think this could probably do with some consideration http://bugs.winehq.org/show_bug.cgi?id=6233 , it describes how the Applications tab does not belong among the other tabs because it should be higher up in the hierarchy of things.
On 13/02/2008, Jeff Zaroyko <jeffzaroyko(a)gmail.com> wrote:
Reece Dunn <msclrhd <at> googlemail.com> writes:
I am looking at how we can make winecfg more useful. I have already supplied patches to allow importing a ubuntu human theme to work :). So I am now looking at how to build on that.
I think this could probably do with some consideration http://bugs.winehq.org/show_bug.cgi?id=6233 , it describes how the Applications tab does not belong among the other tabs because it should be higher up in the hierarchy of things.
There are several bugs related to winecfg currently. Also, the Ubuntu devs have some ideas on improvements to winecfg on their wiki, as well as some ideas for command line access to winecfg, install/uninstall and other functionality. Ideally, there should be a winecfg meta-bug, like what we have for 1.0 and have the various enhancements grouped into relevant bugs. This will allow attachments (like mockups to be added), as well as tracking patches and ideas. I'll start setting this up, and raising the Ubuntu comments as enhancements, to better track things and get the usability and scriptability of wine configuration and management up to where they should be. Does anyone know how to set up the meta bug/group to track these? - Reece
"Reece Dunn" <msclrhd(a)googlemail.com> wrote:
Does anyone know how to set up the meta bug/group to track these?
We decided to avoid meta bugs in Wine. I'd suggest to discuss the things first on wine-devel, and make sure that there is an agreement to what you are planning to change. Only then start adding features, change functionality. -- Dmitry.
On 14/02/2008, Dmitry Timoshkov <dmitry(a)codeweavers.com> wrote:
"Reece Dunn" <msclrhd(a)googlemail.com> wrote:
Does anyone know how to set up the meta bug/group to track these?
We decided to avoid meta bugs in Wine. I'd suggest to discuss the things first on wine-devel, and make sure that there is an agreement to what you are planning to change. Only then start adding features, change functionality.
Ok. I was trying to find a better way of tracking planned changes - what I am planning, the changes that Ubuntu are interested in and other usability issues from other sources. Perhapse the wiki is a better place for tracking planned changes, provided that there is a more consistent way of tracking feature requests/requirements, analysis and design documentation. - Reece
How about a keyword/wiki page tracking the requests. -Austin On Thu, Feb 14, 2008 at 5:36 AM, Dmitry Timoshkov <dmitry(a)codeweavers.com> wrote:
"Reece Dunn" <msclrhd(a)googlemail.com> wrote:
Does anyone know how to set up the meta bug/group to track these?
We decided to avoid meta bugs in Wine. I'd suggest to discuss the things first on wine-devel, and make sure that there is an agreement to what you are planning to change. Only then start adding features, change functionality.
-- Dmitry.
Reece Dunn wrote:
On 13/02/2008, Jeff Zaroyko <jeffzaroyko(a)gmail.com> wrote:
Reece Dunn <msclrhd <at> googlemail.com> writes:
I am looking at how we can make winecfg more useful. I have already supplied patches to allow importing a ubuntu human theme to work :). So I am now looking at how to build on that.
I think this could probably do with some consideration http://bugs.winehq.org/show_bug.cgi?id=6233 , it describes how the Applications tab does not belong among the other tabs because it should be higher up in the hierarchy of things.
There are several bugs related to winecfg currently. Also, the Ubuntu devs have some ideas on improvements to winecfg on their wiki, as well as some ideas for command line access to winecfg, install/uninstall and other functionality.
Great. One bug == one bugzilla entry. One enhancement == one bugzilla enhancement entry
Ideally, there should be a winecfg meta-bug, like what we have for 1.0 and have the various enhancements grouped into relevant bugs. This will allow attachments (like mockups to be added), as well as tracking patches and ideas.
There is no metabug for Wine 1.0. There is a query that is run that shows bugs that should be closed/corrected before Wine 1.0 is released
I'll start setting this up, and raising the Ubuntu comments as enhancements, to better track things and get the usability and scriptability of wine configuration and management up to where they should be.
Again, one bug or one enhancement - one bugzilla entry. Some of the bugs/enhancements should be there before Wine 1.0 is released, some others can wait and others still may never be there.
Does anyone know how to set up the meta bug/group to track these?
No. Metabugz are not desired for additional functionality. Their purpose should be only to track bugs found in a particular release candidate that will stop a product release. It is undesirable to have a metabug for a series of enhancements. James
On 13.02.2008 10:15, Reece Dunn wrote:
* Pre-populate the Theme list with themes in WINDOWS/Resources/Themes and with other *.theme files added by the user.
I dimly recall this is already the case. winecfg lets uxtheme enum installed themes, which in turn should look into said directory.
* Rename "Install theme..." to "Add...".
The rationale is that we are not installing a theme, but setting it as the theme being used. Having the theme appear in the Themes list in the future further supports this name change and workflow.
Well but it really installs. It copies the selected file to Themes dir. See on_theme_install() in winecfg. -f.r.
participants (8)
-
Austin English -
Dmitry Timoshkov -
Frank Richter -
James McKenzie -
Jeff Zaroyko -
Juan Lang -
Reece Dunn -
Steven Edwards