After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 88279 - No Credits dialog
No Credits dialog
Status: RESOLVED FIXED
Product: gconf-editor
Classification: Applications
Component: general
git master
Other other
: High enhancement
: ---
Assigned To: Gconf Editor Maintainers
Gconf Editor Maintainers
Depends on: 136746
Blocks:
 
 
Reported: 2002-07-16 02:00 UTC by Jordi Mallach
Modified: 2005-08-15 01:55 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
incomplete patch (needs stripped down copy of gnome-about.[ch]) (3.29 KB, patch)
2002-10-28 13:25 UTC, Jordi Mallach
none Details | Review
Patch using gnome_about_ (3.92 KB, patch)
2004-03-31 00:23 UTC, Fernando Herrera
none Details | Review

Description Jordi Mallach 2002-07-16 02:00:15 UTC
I can't see any "Credits" button in the about window, so I can't see
information about the code hackers, documenters or translators.

Please add it, for great justice!
Comment 1 Jordi Mallach 2002-10-28 13:23:40 UTC
Well, I tried giving this a go, but discovered gconf-editor isn't
using libgnomeui at all. andersca said he would rather add
gnome-about.[ch] in gconf-editor's sources, as he doesn't want to link
to gnomeui just for a stupid about dialog.
When I tried doing this, I came across a maze of .h deps. Someone who
knows how to chop unneeded things of these header and source files
should probably finish this patch.
Comment 2 Jordi Mallach 2002-10-28 13:25:45 UTC
Created attachment 11886 [details] [review]
incomplete patch (needs stripped down copy of gnome-about.[ch])
Comment 3 Fernando Herrera 2004-01-15 16:15:28 UTC
This patch needs to wait after the feature freeze, but I'm not sure
this is the right way... maybe linking gconf-editor with libgnomeui
and make it a gnome program is better. How many apps around there are
using gtk+gconf without being gnome apps? Are they relevant for
gconf-editor?
Comment 4 alexander.winston 2004-01-24 03:47:04 UTC
Adding the PATCH keyword.
Comment 5 Jordi Mallach 2004-01-24 08:26:19 UTC
I'm removing the PATCH keyword, as the patch is incomplete and
probably quite broken.

I think keeping gconf-editor just GTK could be a Good Thing. If some
gconf setting broke all GNOME apps, you could still fix it up by using
the GTK-only gconf-editor, to some extent.
Comment 6 Fernando Herrera 2004-03-31 00:23:50 UTC
Created attachment 26126 [details] [review]
Patch using gnome_about_

This patch uses the gnome_about_new function.
This depends on gconf-editor becoming a gnome app (patch on bug #133052)
Comment 7 Jordi Mallach 2004-03-31 09:51:33 UTC
Hi fer,

I tend to agree with andersca's point of view of 1.5 years ago: gconf-editor
might be used when GNOME-related stuff is quite broken, to try to change some
gconf setting that makes it not work at all, for example. If we make
gconf-editor a GNOME app, it'd be useless in this scenario, for example.
Comment 8 Fernando Herrera 2004-04-23 08:01:07 UTC
Commited.