Re: Supporting po/LINGUAS in 2.16
Le lundi 10 avril 2006 à 17:00 -0400, Rodney Dawes a écrit :
It has just come to my attention that one of the GNOME Goals is to port
GNOME to using the po/LINGUAS file for 2.16, rather than having the
LINGUAS listed directly in configure.{in,ac}.
http://live.gnome.org/GnomeGoals/PoLinguas is the link for the page
which describes the process for doing this. However, it is describing
the wrong way to fix this, and contains incorrect information about
the dependency on intltool 0.34.2.
This is actually my fault. I thought it was okay, while it was not
perfect. We'll probably add a need proofreading section for future
goals spec.
[...]
On another note, can we please discuss major changes such as this, on
this list, before deciding on making them goals that people should be
working on?
Sure. Well, maybe not always on this list, but on the appropriate list.
Vincent
--
Les gens heureux ne sont pas pressés.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: LINGUAS file support in po directories
Le mardi 11 avril 2006 à 23:22 -0400, Rodney Dawes a écrit :
OK,
So, in accordance with previous correspondence I sent about the use of
po/LINGUAS rather than ALL_LINGUAS in configure.{in,ac}, I hereby
present to you, the Correct (TM) way to migrate to using the LINGUAS
file in your po subdirectory or even multiple subdirectories with
different levels of i18n support.
Great!
I updated http://live.gnome.org/GnomeGoals/PoLinguas accordingly. Could
you verify there's no insanity in there (or fix them)?
Thanks,
Vincent
--
Les gens heureux ne sont pas pressés.
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: LINGUAS file support in po directories
On Thu, 13 Apr 2006, Vincent Untz wrote:
Le mardi 11 avril 2006 à 23:22 -0400, Rodney Dawes a écrit :
OK,
So, in accordance with previous correspondence I sent about the use of
po/LINGUAS rather than ALL_LINGUAS in configure.{in,ac}, I hereby
present to you, the Correct (TM) way to migrate to using the LINGUAS
file in your po subdirectory or even multiple subdirectories with
different levels of i18n support.
Great!
I updated http://live.gnome.org/GnomeGoals/PoLinguas accordingly. Could
you verify there's no insanity in there (or fix them)?
And Rodney, can you make that 0.35 release or at least bump the
version up to 0.35, so we can simply require 0.35 instead of
0.34.90?
behdad
Thanks,
Vincent
--behdad
http://behdad.org/
Commandment Three says Do Not Kill, Amendment Two says Blood Will Spill
-- Dan Bern, New American Language
___
desktop-devel-list mailing list
desktop-devel-list@gnome.org
http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-control-center has been branched for 2.14
On Wed, 2006-04-12 at 17:23 -0400, Rodney Dawes wrote: If any particular capplet were to just be nuked from control-center, I would prefer it to be the resolution capplet. Opening a dialog to switch between resolutions seems rather crappy to me. It would be nice to have that ability in a capplet that supports other features as well, but having the only item in a capplet be the screen resolution, is a bit off. And maybe we can integrate resapplet with it. I've been planning on integrating XICC (colour profiles) into the Resolution capplet (turning it into Screen), but haven't had the time really... Ross -- Ross Burton mail: [EMAIL PROTECTED] jabber: [EMAIL PROTECTED] www: http://www.burtonini.com./ PGP Fingerprint: 1A21 F5B0 D8D0 CFE3 81D4 E25A 2D09 E447 D0B4 33DF signature.asc Description: This is a digitally signed message part ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
Stanislav Brabec wrote: Gconf seems like an incredibly complicated way of adding an icon. And it doesn't seem to work at all. There is no connection between what I see on gconf-editor and the icons I see on my desktop. Yes, for panel it is true. But there is one chance, much simpler with GNOME 2.14 (it has merged gconf tree in ~/.gconf/%gconf-tree.xml): - Create new user account. - Configure it as you want. - Logout. - Open your ~/.gconf/%gconf-tree.xml in an text editor. - Find everything with /apps/panel/default_setup in its key. - Insert it to updated panel-default-setup.entries. I don't have that file. I take it that Ubuntu ships with a previous version of Gnome. Except that I don't understand the contents of ~/.gconf These are XML files with user's changes of configuration read by gconf daemon. Yes, I know what XML is, and I'm quite comfortable with XML. But that doesn't tell me what any of of those files means or how they work. They really aren't self-describing and there are 124 of them just in my ~/.gconf directory. I'm not going to read 124 XML files in a vain hope of guessing how they work. It seems easier to just cp ~/.gconf ~/.gnome2 /etc/skel/ Yes, but once user makes mistake, there is no way to reset to OEM default. But I don't have any other solution. As I keep saying, the Gconf comfiguration is a huge and incomprehensible. I shouldn't have to read 124 xml files just to add an icon. If you are talking about .../gconf/schemas/panel-default-setup.entries then I have no idea how to edit it. See above. Above you said this is an XML file. I knew that. I can tell you that OpenDocument files are XML, does that suddenly mean that now you know how they work? Not icon, you are adding keys there. But even this is not intuitive, if you need a new drawer: - Go to lowest existing drawer Drawer? On gconf-editor I can't see anything I'd call a drawer. I see a tree-view of what someone might call folders. And which one is last? Are you talking about /apps/panel/objects/object_9? Ok, I'm there. But what does this have to do with keys? I've figured out that the settings for the pre-configured entries are called keys (object-type, description, etc). But I don't want to add a new property to a pre-configured panel entry. I want to add a new one that corresponds to a new icon . - Right click in right empty window I see no empty window. I see two columns full of stuff, none of which seems relevant to adding an icon to the panel. - Enter the key name, including missing part of the path and /. - Exit gconf-editor. - Run gconf-editor. Drawer and key are here. I have just filled it as a bug: http://bugzilla.gnome.org/show_bug.cgi?id=338239 Thank you for filing that bug. Sadly, I don't see what adding a key to a panel entry has to do with adding an icon to the panel. I swear I'm not trying to be difficult. I did take another look at gconf-editor and I did try to find a way to do what I want. Still don't know how to edit .entries or .schemas. Like you said, they aren't exactly straight forward. In a text editor with a little understanding of XML. I have more than a little understanding of XML. That doesn't automatically make me understand how Gconf works. Do you have a little understanding of XML? Are you sure that if I gave you a broken OpenDocument file and said fix the tables you would be able to do it? Knowing XML (which I do) is not enough to understand every XML format ever made. If it did we wouldn't have to worry about Microsoft making a gibberish XML and trying to make it standard. - Change GConf path and use separate GConf database No use unless I can generate a separate GConf database. Yes, you can, it should be simple: Create $sysconfdir/gconf/2/local-defaults.path (or edit $sysconfdir/gconf/2/path) Add there a directory (see the syntax in the path file). Create this directory and make it world readable (default in most distributions). It isn't simpe, look, first I don't know the value of $sysconfigdir, so I have to guess. I'll guess that it's /etc/. Okay, I see that it's a series of include statements and one of them is /etc/gconf/2/local-defaults.path. Ok, so I go edit the file and then I find that I still haven't the faintest clue of what to put on it. There are 124 files in my ~/.gconf and none of them is obviously the one I should copy to local-defaults.path (even if I assume that copying it is what I should do - which is not known). But as I wrote before, for panel all these ways are very unintuitive. You could say that :) It is unintuitive only for default panel setup. For other things, it is very straightforward. For example - change the init splash: - Find /apps/gnome-session/options/splash_image in gconf editor. Configuring existing items is simple enough, but that doesn't make the XML file comprehensible, and it doesn't tell me how to create a new entrie that does what I want. - You see nice
Re: Solution for OEMs/Gnome
Frederic Ruaudel wrote: Hi Daniel, I'm not sure it is exactly what you are looking for, but maybe these 3 articles from redhat magazine can help you. I'd like to add an icon to the panel so that when a new user is created he sees the new icon. Sounds simple, no? Thank you for trying though. Daniel. -- /\/`) http://opendocumentfellowship.org /\/_/ /\/_/ A life? Sounds great! \/_/Do you know where I could download one? / ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
Le jeudi 13 avril 2006 à 10:23 +0100, Daniel Carrera a écrit : Yes, I know what XML is, and I'm quite comfortable with XML. But that doesn't tell me what any of of those files means or how they work. They really aren't self-describing and there are 124 of them just in my ~/.gconf directory. I'm not going to read 124 XML files in a vain hope of guessing how they work. But I don't have any other solution. As I keep saying, the Gconf comfiguration is a huge and incomprehensible. I shouldn't have to read 124 xml files just to add an icon. You were told at the beginning of this thread that such oem customizations were unfortunately something that still needed work... It isn't simpe, look, first I don't know the value of $sysconfigdir, so I have to guess. I'll guess that it's /etc/. Okay, I see that it's a series of include statements and one of them is /etc/gconf/2/local-defaults.path. Ok, so I go edit the file and then I find that I still haven't the faintest clue of what to put on it. There are 124 files in my ~/.gconf and none of them is obviously the one I should copy to local-defaults.path (even if I assume that copying it is what I should do - which is not known). If you haven't read http://gnome.org/projects/gconf/ yet, this may give you some background about gconf that might be useful in that case. And frankly, once you have seen how the gconf database is layed out with gconf-editor and once you have changed a few keys/created a few new ones in gconf-editor, the xml format should be pretty easy to understand imo... And please don't answer me I want to create an icon, not to learn about gconf I can't give you a magical way of adding a new icon, thus my mail's goal isn't to tell you how you can do it, I'm just trying to help you to understand how gconf works (and if you are not interested in that, feel free to ignore that mail). Christophe ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: System-wide settings for the panel?
Hi Daniel, On Tue, April 11, 2006 16:41, Daniel Carrera wrote: Hello, I've been trying to figure out how to change the system wise settings for the Gnome panel (e.g. add/remove icons). I can't find this anywhere. All the documentation around is for the end-user, not for admins. I've searched the list archives and all I could find was references to this question being answered before without actually finding the answer. :P I've looked through every file in my computer whose path includes gnome and panel and I can't find anything. I would be very grateful if someone could tell me how I can change the Gnome global panel settings (in particular, add/remove icons and menu entries) so that any new users get the settings I pick. Assuming you're using Ubuntu, you need to modify /usr/share/gconf/schemas/panel-default-setup-laptop.entries (or /usr/share/gconf/schemas/panel-default-setup.entries if it's not a laptop). The content of the file is like a gconf dump (see gconftool-2 --dump /apps/panel, for example). So you could modify an account, dump the configuration and copy the interesting part in the .entries file. Cheers, Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
On Thu, 2006-04-13 at 10:25 +0100, Daniel Carrera wrote: Frederic Ruaudel wrote: Hi Daniel, I'm not sure it is exactly what you are looking for, but maybe these 3 articles from redhat magazine can help you. I'd like to add an icon to the panel so that when a new user is created he sees the new icon. Sounds simple, no? Have you seriously tried sabayon yet [1], even if there isn't official documentation telling you that this is how to do it? In the dialog that you see after clicking the Users button, there is a Use this profile for all users checkbox. I assume that applies to all future users too. It's available as System/Administration/User Profile Editor in Ubuntu Dapper. I don't know about Breezy. -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
On Wed, April 12, 2006 13:41, Daniel Carrera wrote: Stanislav Brabec wrote: Thanks to all who gave suggestions. One of the suggestions turns out to work quite well: 1. Configure Gnome just the way I want it. 2. sudo cp ~/.g* /etc/skel Af least for .gconfd it is a bad idea. [snip: also .gconf and .gnome2_private] Ok, how about just ~/.gnome2 ? That should be enough for the panel, right? And what about the menu? Is that also in ~/.gnome2 ? ~/.gnome2/ is not enough for the panel. It needs to know that the .desktop file should be on a panel, on which panel, where on the panel, etc. See my previous mail to know how to configure this. Vincent -- Les gens heureux ne sont pas pressés. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: System-wide settings for the panel?
Vincent Untz wrote: I would be very grateful if someone could tell me how I can change the Gnome global panel settings (in particular, add/remove icons and menu entries) so that any new users get the settings I pick. Assuming you're using Ubuntu, you need to modify /usr/share/gconf/schemas/panel-default-setup-laptop.entries (or /usr/share/gconf/schemas/panel-default-setup.entries if it's not a laptop). The content of the file is like a gconf dump (see gconftool-2 --dump /apps/panel, for example). So you could modify an account, dump the configuration and copy the interesting part in the .entries file. Oh, that's neat. I don't know which parts are interesting, so could I just do this: gconftool-2 --dump /apps/panel /usr/share/gconf/schemas/panel-default-setup.entries Btw, yes I'm on Ubuntu. A cursory look at the output of the --dump and the panel-default-setup file suggests that the above line would do what I want. Thank you very much. Cheers, Daniel. -- /\/`) http://opendocumentfellowship.org /\/_/ /\/_/ A life? Sounds great! \/_/Do you know where I could download one? / ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-applets branched
Plans! Plans! On 4/13/06, Davyd Madeley [EMAIL PROTECTED] wrote: gnome-applets has been branched for active development towards GNOME 2.16. --d -- Davyd Madeley http://www.davyd.id.au/ 08B0 341A 0B9B 08BB 2118 C060 2EDD BB4F 5191 6CDA ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-applets branched
On Thu, Apr 13, 2006 at 09:52:14AM -0400, Luis Villa wrote: Plans! Plans! 1) Replace gtik 2) other stuff 3) ... 4) profit! -- Davyd Madeley http://www.davyd.id.au/ 08B0 341A 0B9B 08BB 2118 C060 2EDD BB4F 5191 6CDA ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
librsvg has been branched
We branched a little while ago. Mundane 2.16 plans include: *) Working with Inkscape to support multiImage *) Supporting whatever SVG 1.2 features that Cairo 1.2's SVG backend requires, so that it doesn't need to do image fallbacks *) Translating the strings (something that's long overdue) *) Using GOption Best, Dom -- Counting bodies like sheep to the rhythm of the war drums. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: gnome-applets branched
On Thu, 2006-04-13 at 22:00 +0800, Davyd Madeley wrote: 4) profit! Good luck ;) ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
Elijah Newren wrote: Daniel, Thanks for all your patience. I see from another email that sabayon has worked for you, which is great. That makes your whole below email sounds like perfect marketing material for sabayon now. :-) Please keep letting us know where any other warts are so we can fix them up if they haven't been already. Heh, sure. And I /would/ recommend sabayon to other OEMs. I'd just make sure to tell them two things: * sudo aptitude install sabayon * Click on User and then Use this profile for all users. That's enough to make it work for new (future) users, and it doesn't prevent the user from changing the configuration afterwards. This is important for the Ubuntu OEM installation, and it's not obvious, so I tested it. Best, Daniel. -- /\/`) http://opendocumentfellowship.org /\/_/ /\/_/ A life? Sounds great! \/_/Do you know where I could download one? / ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
Daniel Carrera wrote: Chipzz wrote: For .gconf you should prefer root's gconf database (but I still see a problem, that such customization is overwritten by a subsequent packages update, at least with the default gconf path). It should be pointed out that for debian (and I think also ubuntu, which is what he is using) this is simply not true. The gnome defaults are shipped in /usr, not in /etc, and gconf actually uses multiple databases on debian which allows you to do exactly that: make your own changes without them being overwritten on subsequent upgrades. Thanks. Once again, unless someone has written a document describing how to change the Gconf database (and perhaps something about how that database works) this is all of little use to me. * Please don't tell me edit the .schema file (which one? how? those things are incomprehensible - yes, I know XML). Early in this thread, the admin guide was pointed out. It has a short description of gconf schemas here: http://www.gnome.org/learn/admin-guide/2.6/ch01s02.html#gconf-27 Although if you are setting up systems, it is usually better to edit the defaults or mandatory gconf config sources rather than trying to modify schema files (which will most likely get overwritten when you install security updates anyway). Configuration sources are described here: http://www.gnome.org/learn/admin-guide/2.6/ch01s02.html#gconf-26 You can also add to the gconf search path by creating /etc/gconf/2/local-mandatory.path and /etc/gconf/2/local-defaults.path files that list additional config sources. This can be used to point to a central NFS shared config source, for instance (may be useful if you are rolling out a configuration to a large number of machines). * Please don't tell me do it wit gconf-editor (gconf-editor does *not* have any way of adding a stupid icon to the panel). The default panel layout is actually controlled through gconf. Again, the admin guide documents this, including tips on converting an existing panel layout for use as a default panel layout: http://www.gnome.org/learn/admin-guide/2.6/ch01s06.html#gconf-14 The first time a user logs in, their panel configuration will be constructed from the default layout found in gconf. James. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: System-wide settings for the panel?
I hope that you might also contribute your time in helping to make Sabayon more useful for other systems administrators who might also want to do the kind of things we're doing. It'll be useful to understand the kind of models systems administrator would want. sri On Thu, Apr 13, 2006 at 11:39:51AM +0100, Daniel Carrera wrote: Daniel Carrera wrote: I don't know which parts are interesting, so could I just do this: gconftool-2 --dump /apps/panel /usr/share/gconf/schemas/panel-default-setup.entries Well, that didn't work. But the sabayon solution (Use this profile for all users) did work. Even for not-yet-created users. Thank you very much for the help. Best, Daniel. -- /\/`) http://opendocumentfellowship.org /\/_/ /\/_/ A life? Sounds great! \/_/Do you know where I could download one? / ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list -- ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
On Thu, 2006-04-13 at 17:31 +0100, Daniel Carrera wrote: Elijah Newren wrote: Daniel, Thanks for all your patience. I see from another email that sabayon has worked for you, which is great. That makes your whole below email sounds like perfect marketing material for sabayon now. :-) Please keep letting us know where any other warts are so we can fix them up if they haven't been already. Heh, sure. And I /would/ recommend sabayon to other OEMs. I'd just make sure to tell them two things: * sudo aptitude install sabayon * Click on User and then Use this profile for all users. That's enough to make it work for new (future) users, and it doesn't prevent the user from changing the configuration afterwards. This is important for the Ubuntu OEM installation, and it's not obvious, so I tested it. It should be enough to work for ALL users, current and future. GConf looks up settings from multiple sources. Typically, it has three sources: system-wide mandatory, user settings, and system-wide default. Sabayon should be setting the system-wide default settings. If a user has not explicitly changed a setting, it will be retrieved from the defaults. So changing the defaults will affect all current users who have not explicitly opted out of being affected. But then, the panel uses a very complex key layout, which might create oddities with how the defaults work. -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
On Thu, 2006-04-13 at 09:45 +0100, Daniel Carrera wrote: Chipzz wrote: For .gconf you should prefer root's gconf database (but I still see a problem, that such customization is overwritten by a subsequent packages update, at least with the default gconf path). It should be pointed out that for debian (and I think also ubuntu, which is what he is using) this is simply not true. The gnome defaults are shipped in /usr, not in /etc, and gconf actually uses multiple databases on debian which allows you to do exactly that: make your own changes without them being overwritten on subsequent upgrades. Thanks. Once again, unless someone has written a document describing how to change the Gconf database (and perhaps something about how that database works) this is all of little use to me. * Please don't tell me edit the .schema file (which one? how? those things are incomprehensible - yes, I know XML). * Please don't tell me do it wit gconf-editor (gconf-editor does *not* have any way of adding a stupid icon to the panel). * Please don't tell me copy the config files from xyz (what use is that if I can't edit the config files in the first place?) I see that you've already found Sabayon to be a good solution, but just for information's sake: Using gconf-editor is a reasonably good way to create default and mandatory settings for simple configuration options. For example, if you want to set whether the trash icon is visible on users' desktops, you would open the Defaults window and toggle the checkbox for /apps/nautilus/desktop/trash_icon_visible. So everybody around here gets really proud of how easy this is, and they run around screaming about how easy it is to set defaults for everything with GConf. The problem is that the panel uses a fairly complex layout of dynamically-created keys and directories of keys. gconf-editor will allow you to create new keys, but it can't create new directories of keys. (Not because of any technical limitation; it's really just a design oversight. [1]) So gconf-editor just isn't powerful enough. Even if it were, figuring out the panel's complex dynamic key layout to make the changes isn't a trivial task. For things like the panel layout, mucking around with the actual keys just isn't going to be fun, whether you use gconf-editor, gconftool-2, or emacs. In this particular case, the keys themselves are too confusing for mortals. And that's why Sabayon is so great: you get to set the default settings the same way you'd set up your own desktop. [1] Technically directories don't really exist. The key paths are more like namespaces, so it just doesn't make sense in GConf to have directories without keys. But that shouldn't stop gconf-editor from being able to create new keys with new paths/namespaces. -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
I'd just like to say that Shaun's description is right on the mark. I couldn't have summarized the state of Gconf and Sabayon so well. Best, Daniel. Shaun McCance wrote: I see that you've already found Sabayon to be a good solution, but just for information's sake: Using gconf-editor is a reasonably good way to create default and mandatory settings for simple configuration options. For example, if you want to set whether the trash icon is visible on users' desktops, you would open the Defaults window and toggle the checkbox for /apps/nautilus/desktop/trash_icon_visible. So everybody around here gets really proud of how easy this is, and they run around screaming about how easy it is to set defaults for everything with GConf. The problem is that the panel uses a fairly complex layout of dynamically-created keys and directories of keys. gconf-editor will allow you to create new keys, but it can't create new directories of keys. (Not because of any technical limitation; it's really just a design oversight. [1]) So gconf-editor just isn't powerful enough. Even if it were, figuring out the panel's complex dynamic key layout to make the changes isn't a trivial task. For things like the panel layout, mucking around with the actual keys just isn't going to be fun, whether you use gconf-editor, gconftool-2, or emacs. In this particular case, the keys themselves are too confusing for mortals. And that's why Sabayon is so great: you get to set the default settings the same way you'd set up your own desktop. [1] Technically directories don't really exist. The key paths are more like namespaces, so it just doesn't make sense in GConf to have directories without keys. But that shouldn't stop gconf-editor from being able to create new keys with new paths/namespaces. -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list -- /\/`) http://opendocumentfellowship.org /\/_/ /\/_/ A life? Sounds great! \/_/Do you know where I could download one? / ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: LINGUAS file support in po directories
Looks OK to me. Perhaps you could add a note about the no/nb thing too, so that we can ensure all the modules are using nb now as the locale name. That would help alleviate the concerns that Joe Shaw brought up yesterday in his blog entry about po/LINGUAS. -- dobey On Thu, 2006-04-13 at 08:52 +0200, Vincent Untz wrote: Great! I updated http://live.gnome.org/GnomeGoals/PoLinguas accordingly. Could you verify there's no insanity in there (or fix them)? Thanks, Vincent ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
Daniel: I think you are very right that being able to add icons to the panel is something that many OEM's would like to do. I think nobody has yet asked for this feature loud enough. The main problem here is with exposing the GConf configuration interfaces that control the appearance of the panel. In the past, these have changed in incompatible ways, which is why the instructions in the 2.6 guide no longer work with newer versions of GNOME, for example. What would be useful would be if someone wrote a script that modified the GConf settings appropriately to add an icon to the panel. Then if the panel configuration usage of GConf changes, the script can be modified to continue working. This avoids exposing the GConf keys directly, which is probably a good idea. Since it sounds like people are mucking around with editing their .gconf files by hand, why not write a script to do this work and attach it to bug 166623. http://bugzilla.gnome.org/show_bug.cgi?id=166623 Then we could probably ship it and there you go. Brian You were told at the beginning of this thread that such oem customizations were unfortunately something that still needed work... Well... I've been told many times on this thread that it's easy. I have no problem with it needing work. I don't expect Gnome to be perfect. But if people keep saying it's easy without actually giving me reasonable way to do it I'll speak up. And please don't answer me I want to create an icon, not to learn about gconf I've never said that. Indeed, I've said that I'm willing to put in a reasonable amount of work. I've read the Gconf help, I've read parts of the XML files. I really have spent a lot of hours on this. But the feedback I've received has been roughly equivalent to saying that I must figure out how to edit the gconf xml files without help. Personally, I think that is more than a reasonable amount of effort because there are so many files and they are complex. I don't expect to have a one-click solution. But I hope you'll understand how it seems from my point of view. I'm simultaneously told that (1) it's easy and that (2) I have to figure out how to edit a complex XML file myself. Best, Daniel. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Solution for OEMs/Gnome
On Thu, 2006-04-13 at 13:50 -0700, Brian Cameron wrote: Daniel: I think you are very right that being able to add icons to the panel is something that many OEM's would like to do. I think nobody has yet asked for this feature loud enough. They have, and Sabayon was created, and Sabayon was suggested at the start of this thread. No need for more loudness. [snip] -- Murray Cumming [EMAIL PROTECTED] www.murrayc.com www.openismus.com ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Fwd: [gnome-love] Participate to the GNOME Goals and feel the love!
You are welcome to disagree all you want. You are still wrong. 3d is a very different beast from SVG. You can not create a single SVG that will render properly at different sizes. In 3D games, and the like, where even at a distance, the object still looks good, this is because of how the core functionality works. SVG was not designed well to be scalable beyond small thresholds. It does not add or remove particular details of an object when scaling up or down, as 3D applications do. Even scaling an SVG icon drawn at 48x48 down to 32x32, it often looks quite bad. SVG is not the savior of icons that you think it is. -- dobey On Thu, 2006-04-13 at 02:13 +0200, Esben Stien wrote: I don't agree;). If you make a simple big one and scale it down, it'll still look good. You don't make an icon small; at least in my view and I do a lot of 3d modeling. I never think about size when I model. It's all relative. If I model a bus, then go up on a mountain and look down on the bus, it's still the bus, just smaller. ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: About-me-password backend
I agree, if we are going to support PAM, this is something we have to look at. Note that I'm currently just working on bug #321567, which is about usability issues in the dialog, so I'm just using what's already there. I would be happy to improve more than the usability though! I thought using /usr/bin/passwd as the backend was chosen because one didn't want to leave out systems which weren't PAM-enabled. But then again, gdm (and probably other modules) relies on PAM (I think?) for authentication. I have some old code (an old password-changer actually) which communicates directly with PAM. It relies on a backend to update the authentication token, which has to be run as root. I would love if someone experienced with PAM could help me with this :) Best regards, Johannes H. Jensen deworks On 11. apr. 2006, at 14:56:55, Matthias Clasen wrote: On 4/10/06, Johannes H. Jensen [EMAIL PROTECTED] wrote: Dear almighty GNOME hackers, I'm in need of some pointers! I'm currently hacking on the about-me password dialog (see #321567), which is spawning /usr/bin/passwd to authenticate and change the password. In the new dialog, I'm dividing the process in two, so that the user has to authenticate with his current password first (which spawns passwd to verify). If passwd doesn't complain and prompts for the new password, he can enter his new password, retype it and hit Change password. When he hits the button, some time has elapsed since he first authenticated (and thus passwd was spawned). Note that any solution which only asks for old and new password is not fexible enough. pam allows very different setups, and the change password feature in the capplet should support them. What we do in fedora is to just spawn /usr/bin/userpasswd, which is designed to handle all this. Matthias ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
Re: Fwd: [gnome-love] Participate to the GNOME Goals and feel the love!
On Thu, 2006-04-13 at 18:24 -0400, Rodney Dawes wrote: On Thu, 2006-04-13 at 02:13 +0200, Esben Stien wrote: I don't agree;). If you make a simple big one and scale it down, it'll still look good. You don't make an icon small; at least in my view and I do a lot of 3d modeling. I never think about size when I model. It's all relative. If I model a bus, then go up on a mountain and look down on the bus, it's still the bus, just smaller. You are welcome to disagree all you want. You are still wrong. 3d is a very different beast from SVG. You can not create a single SVG that will render properly at different sizes. In 3D games, and the like, where even at a distance, the object still looks good, this is because of how the core functionality works. SVG was not designed well to be scalable beyond small thresholds. It does not add or remove particular details of an object when scaling up or down, as 3D applications do. To be perfectly fair, there are provisions in SVG for adjusting various details at different sizes. But we don't have good tools to take advantage of that, and even if we did, it could very well be harder on our overworked artists than just making raster images. But it's absolutely true that we need adjustments to the icons at different sizes. We're not making scale models of objects; we're making icons that should be easy to recognize and identify. Esban, you talk about modeling a bus. Go out for a drive and look for a street sign with a bus on it. Is it a photo-realistic representation of a bus? Of course not. It's probably a silhouette of what you think a bus looks like, and it probably doesn't have every last curve and dent that a real bus would have. And if I were making that bus icon for a big street sign, I'd probably include about six windows or so. Not photo-realistic windows, just squares where it's not black. But if I were to make that same icon for something small (say, an indicator light in your car that tells you when a school bus is near), I'd leave out some of those windows, maybe all of them. It's not just that icons don't need to be perfect replicas to do their job. In fact, perfect replicas will generally do an even worse job. -- Shaun ___ desktop-devel-list mailing list desktop-devel-list@gnome.org http://mail.gnome.org/mailman/listinfo/desktop-devel-list
