Difference between revisions of "Talk:GNOME"

From ArchWiki
Jump to navigation Jump to search
m (Candidates for removal (discussion): rm closed discussion)
(Moderation: messy removal and reorganization of content: edit)
(One intermediate revision by the same user not shown)
Line 99: Line 99:
  
 
{{Unsigned|22:51, 27 June 2014‎|Paulie4}}
 
{{Unsigned|22:51, 27 June 2014‎|Paulie4}}
 +
 +
== Moderation: messy removal and reorganization of content ==
 +
 +
This article was completely rewritten with [https://wiki.archlinux.org/index.php?title=GNOME&diff=next&oldid=341064] by [[User:Gen2ly]] without any kind of useful comments to explain what was done: a lot of content has been removed, and I don't have enough hours in my days to compare the revisions section by section, so if somebody is looking for something that was here before this "touch-up", this post will help retrieving it.
 +
 +
Also something may have been broken, for example a broken section link as been left in [[GNOME#Artifacts_when_maximizing_windows]].
 +
 +
For the records, this is absolutely '''not''' the way to edit an article, please everybody remember the ArchWiki is not your own personal blog, so always split big changes in small edits accompanied by meaningful edit summaries.
 +
 +
-- [[User:Kynikos|Kynikos]] ([[User talk:Kynikos|talk]]) 11:53, 29 October 2014 (UTC)

Revision as of 11:53, 29 October 2014

GNOME and fontconfig settings

Since there isn't a section dedicated to fonts in GNOME 3 I was thinking about writing one, but I put it here first:

GNOME doesn't use the dpi settings set by xorg server to scale fonts, instead it uses a fixed dpi of 96 that cannot be changed unlike previous versions:

/* As we cannot rely on the X server giving us good DPI information, and
 * that we don't want multi-monitor screens to have different DPIs (thus
 * different text sizes), we'll hard-code the value of the DPI
 *
 * See also:
 * https://bugzilla.novell.com/show_bug.cgi?id=217790•
 * https://bugzilla.gnome.org/show_bug.cgi?id=643704
 */

The gnome-settings-daemon plugin xsettings relies on this hardcoded value for some calculations and there is currently no way of changing it beside customizing the code in abs. The dimension of text can be tweaked changing the text-scaling-factor (1.0 by default), using gnome-tweak-tool or editing the following key in dconf-editor:

org.gnome.desktop.interface.text-scaling-factor

The xsettings plugins will also merge some Xft values in the X resources db overwriting values set in .Xresources od .Xdefaults files. The defaults are:

Xft.antialias:	1
Xft.dpi:	96
Xft.hinting:	1
Xft.hintstyle:	hintmedium
Xft.lcdfilter:	lcddefault
Xft.rgba:	none

Some of those values can be changed using dconf-editor (org.gnome.settings-daemon.plugins.xsettings) or gnome-tweak-tool. It is possible to change this values using xrdb -merge ~/.Xresources after gnome is started but gnome will still use its values internally so it is not a good idea.

It is a good idea to configure your fonts.conf in a way consistent with the gnome settings otherwise, at least on my laptop, fonts will looks weird in some gnome apps.

The dpi setting of the Xserver can be changed to 96 following this guide, this way it will be the same for all applications, the drawback is that fonts might look too small or too big in other application if the real DPI of your monitor differs too much from 96.

For and LCD monitor it is a good idea to activate the lcd filter setting the following keys in dconf-editor:

org.gnome.settings-daemon.plugins.xsettings.antialiasing rgba
org.gnome.settings-daemon.plugins.xsettings.rgba-order rgb, bgr, vrgb or vbgr (as your monitor requires)

Since the lcdfilter is not designed to work together with autohinting it is a good idea to disable it also in fonts.conf. It is also a good idea to use the same hinting value as in your font.conf, the default in gnome is medium:

org.gnome.settings-daemon.plugins.xsettings.hinting medium

This values in fonts.conf will match the gnome settings:

<match target="font">
 <edit mode="assign" name="rgba"><const>rgb</const></edit>
 <edit mode="assign" name="autohint"><bool>false</bool></edit>
 <edit mode="assign" name="hinting"><bool>true</bool></edit>
 <edit mode="assign" name="hintstyle"><const>hintmedium</const></edit>
 <edit mode="assign" name="antialias"><bool>true</bool></edit>
 <edit mode="assign" name="lcdfilter"><const>lcddefault</const></edit>
</match>

(to be finished, please comment or fix) —This unsigned comment is by Erm67 (talk) 23:58, 8 January 2012‎. Please sign your posts with ~~~~!

I think that info must be in Font configuration, linked from there if needed -- Kycok (talk) 10:57, 3 June 2014 (UTC)

deleted manual hotkeys modification

Manual edit of accel.scm into nautilus config doesn't fit with this page. And this can't be a generic method, cause not every application has an accels.scm file, even if it has that, it's location in ~/.config is not mandatory. 4javier 08:09, 25 April 2011 (EDT)

It fits with this page just as much as the remaining part on changing hotkeys does because both serve the same purpose. So I disagree with that it should be downright deleted, particularly as for me (thus possibly others) the can-change-accels way did not work. I added it again (a bit more carefully phrased) to the "Troubleshooting" section. -- Misc 15:40, 25 April 2011 (EDT)
I still think that applications' specific method of changing accels should be mentioned in the application page itself. Into this page I'd leave just a reminder (i.e. "If this method doesn't work see application's wiki page for app specific file"). But I don't delete it anymore until somebody else tell us his opinion. 4javier 20:35, 25 April 2011 (EDT)
Perhaps update Nautilus and reference it? Perhaps simply add that article to the related articles? --stefanwilkens (talk) 23:33, 6 September 2012 (UTC)

Xmonad section

I think xmonad section should be generalized for every other wm: openbox, fluxbox, ratpoison etc. Is there some gnome3 user who can test the method with other wm than xmonad? --4javier 05:40, 16 May 2011 (EDT)

Add link to official extensions site

I think to add a link to extensions.gnome.org, also in order to easy manage the extensions in the browser from the /local page. --Gimmy 05:22, 23 January 2012 (EST)

Link added, this probably deserves a section of its own now that extensions play such a vital role in GNOME. A future rewrite / restructure of this article may be needed. --stefanwilkens (talk) 23:52, 6 September 2012 (UTC)

Reference to NetworkManager

GNOME 3 uses network-manager-applet, which in turn uses NetworkManager. Maybe this page should contain a reference to NetworkManager, so people with network problems in GNOME know where to look for the solution. I suppose many people do not know that using GNOME means using NetworkManager. Pelzflorian (talk) 16:31, 14 March 2014 (UTC)

Using GNOME not always means using NetworkManager :) But it's a dependency for network in GNOME, so I vote +1 -- Kycok (talk) 11:00, 3 June 2014 (UTC)

ownCloud Integration

I noticed missing ownCloud functionality in some GNOME applications (Nautilus & Documents) if gfvs-goa is not installed. I am not sure what else is affected or how exactly this works. I also didn't find any mention on the File manager functionality nor the GVFS pages. I was thinking of contributing to the Troubleshooting section but I do not know enough about the topic or wiki editing. Beanaroo (talk) 09:21, 3 June 2014 (UTC)

Display Dimming Change

Re https://wiki.archlinux.org/index.php/GNOME#Display_dimming: https://git.gnome.org/browse/gnome-control-center has commit bd3b8beeae9a3d88483aa0d33fd10042593735a6 from January 16 that removes "idle-dim-time" from GSettings and has this additional comment:

And make the default time for the dimming be based upon the idle timeout.
If there is no idle timeout, dim at one minute of idle.
If there is an idle timeout, ensure that the dim time is at least 10
seconds, otherwise a third of the idle-delay

I'm not sure if we should remove the #Display_dimming section of this wiki or update it to say something else.

—This unsigned comment is by Paulie4 (talk) 22:51, 27 June 2014‎. Please sign your posts with ~~~~!

Moderation: messy removal and reorganization of content

This article was completely rewritten with [1] by User:Gen2ly without any kind of useful comments to explain what was done: a lot of content has been removed, and I don't have enough hours in my days to compare the revisions section by section, so if somebody is looking for something that was here before this "touch-up", this post will help retrieving it.

Also something may have been broken, for example a broken section link as been left in GNOME#Artifacts_when_maximizing_windows.

For the records, this is absolutely not the way to edit an article, please everybody remember the ArchWiki is not your own personal blog, so always split big changes in small edits accompanied by meaningful edit summaries.

-- Kynikos (talk) 11:53, 29 October 2014 (UTC)