Talk:GNOME

From ArchWiki
Revision as of 06:54, 29 May 2012 by Fengchao (Talk | contribs) (Close old topic.)

Jump to: navigation, search

Clean up

last tip for dpms through xset I think has nothing to do...it's not a gnome feature, and it's not permanent. It should be added to startup, but the right way should be to turn off dpms statically into xorg.conf.d. I think this page is becoming too unspecific.

Thestinger to the rescue! Fixed :-) -- Karol 15:20, 18 May 2011 (EDT)
I know I'm getting really really boring but...https://wiki.archlinux.org/index.php/GNOME#XChat --4javier 16:19, 24 May 2011 (EDT)
You're not boring :-) I've moved it to XChat but I'm not sure if creating a bunch of stubs is the best way to deal with it. As I'm neither a Gnome guy nor an IRC user don't count on me to expand that article anytime soon. -- Karol 02:01, 25 May 2011 (EDT)
maybe is not be a gnome app but gnome-shell has included features for xchat to stack notifications.
http://git.gnome.org/browse/gnome-shell/tree/js/ui/notificationDaemon.js#n76
Maybe we should add a sectiong in gnome wiki called, Integrating apps in gnome-shell and include xchat, pidgin etc -- Wonder
I think that infos don't need a mention into the wiki at all. They're just a possible setting of a program preference... --4javier 06:34, 25 May 2011 (EDT)

cant quite follow your motivations, but if its consistent, please also move gtk3 and xmonad related "possible setting of a program preference" to their own page too. thanks.

gtk3 is the base of gnome3...and it's not a program, it's the main library. About xmonad https://wiki.archlinux.org/index.php/Talk:GNOME#Xmonad_section --4javier 06:50, 25 May 2011 (EDT)

right, but the xchat options listed are specific to running it under gnome (even the new page hints that). and the gtk3 options are not specific to gnome, they are relevant under any other wm/de.

You're free to create Gtk3 page and move there theming hints. :) But talk about that to wiki admin first. --4javier 07:43, 25 May 2011 (EDT)

Gnome and fontconfig settings

Since there isn't a section dedicated to fonts in gnome3 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)

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)

Seamonkey and Pulseaudio

  1. I cant setup seamonkey as default webbrowser.. This is imposible in gnome-control-center without some modyfication.. Google give nothing special, only garbage.
  2. I have "Audigy2 value" and ld10k1 from alsa-tools. How can I do this to work in 5.1? (If you have that problem or/and you know what do, tell me..) Can I disable pa and where? :)

3ED 10:03, 1 May 2011 (EDT)

Nautilus bug

I think nautilus bug has not too much to do with this page. I think move it to nautilus page should be appropriate. --4javier 13:53, 4 May 2011 (EDT)

Merge with GNOME

I report this forum discussion: this article needs to be merged with GNOME. -- Kynikos 17:54, 4 May 2011 (EDT)

I agree with cosmin, Gnome page should contain just Gnome3 info. At most we could move gnome 2.x info to a Gnome2 page or a Gnome Legacy page. --4javier 13:28, 6 May 2011 (EDT)
I'd just merge with GNOME and discard the outdated parts (almost all), keeping what still makes sense, like the external links (some need updating); the old page would stay in the history afterall. What about GNOME Tips and GNOME Shell? -- Kynikos 19:34, 6 May 2011 (EDT)

I don't agree with this merge, at all. Gnome Tips is full of crap, excuse me, out of date information. If you really want to do something about it, i propose to move some tips from gnome wiki into tips but not all of it. I still want a wiki for gnome to learn how to install, what services to configure and how to start it. Wonder

Are you talking about merge template between Gnome and Gnome Tips? I just set it to indicate that two articles overlap in scope, and something could be done there (merge, delete or better division). Also template serves as a remainder of the existence of the other page, since I think many who write or read one of them are unaware of other.
Unfortunately I'm not Gnome expert and don't know how to deal with this the best way.
After I added this template, I typed KDE in search box, and - surprise - immediately found identically unclearly divided pair of articles on KDE. - corvinus

battery icon

I have no battery / power indicator at all! https://live.gnome.org/GnomeShell/Design/Guidelines/SystemStatus/BatteryPower

solved and added

I think this is useless. gnome-power-manager is part of gnome-extra group that's already mentioned into the wiki. --4javier 13:31, 6 May 2011 (EDT)

Resizing massive titlebar

Should not be better point that sed manipulation to ~/.themes/Adwaita/metacity-1/metacity-theme-3.xml ? --4javier 07:27, 7 May 2011 (EDT)

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)

«You must install the gnome group»

This sentence is written in bold characters in the Installation section. I don't agree: I really don't want to install Epiphany in my system and I really don't want install gnome-applets in my system. These (and others) are not fundamental components of the Gnome DE, so IMHO they have to be moved in gnome-extra or their function has to be explained in the wiki, so people can choose which of them install. What you think about it? Mons 04:53, 29 December 2011 (EST)

Definitely, that section must be rewritten in a more neutral way, giving the readers all the information they need to make their own unbiased decisions. It should also make use of Template:Grp to provide quick links to the package lists (gnome, gnome-extra - unfortunately this template is i686-centric) and should avoid giving examples of how to install (groups of) packages with pacman, in accordance to Help:Style#Official packages. -- Kynikos 06:44, 30 December 2011 (EST)

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)