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 349267 - Help kill libegg
Help kill libegg
Status: RESOLVED FIXED
Product: eog
Classification: Core
Component: general
2.19.x
Other Linux
: Normal normal
: ---
Assigned To: EOG Maintainers
EOG Maintainers
Depends on: 120645
Blocks: 349256
 
 
Reported: 2006-07-30 10:53 UTC by Vincent Untz
Modified: 2007-09-04 21:29 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20


Description Vincent Untz 2006-07-30 10:53:00 UTC 
+++ This bug was initially created as a clone of Bug #349256 +++

Please help kill libegg. Your module contains some egg code that is now deprecated thanks to new features, most probably the new GTK+ 2.10 features like:

 + GtkRecent* (deprecating EggRecent)
 + GtkStatusIcon (deprecating EggTrayIcon and EggStatusIcon)
 + GtkCellRendererAccel (deprecating EggCellRendererKeys)
 + GtkAccelGroup now has features to deprecate EggAccelerator (see bug 85780)

Also, egg-screen-exec stuff has been deprecated: see http://cvs.gnome.org/viewcvs/*checkout*/libegg/libegg/screen-exec/README

Also, EggIconList has become GtkIconView in GTK+ 2.6.
Comment 1 Lucas Rocha 2006-09-01 13:18:49 UTC 
In eog-ng branch, we've already removed all libegg dependencies.
Comment 2 Lucas Rocha 2007-03-18 00:08:43 UTC 
eog-ng branch, which has a full rewrite of eog's core, has been merged into trunk as part of 2.19/2.20 development cycle. Therefore this bug is fixed now. Thanks for the report!
Comment 3 Felix Riemann 2007-08-19 12:43:09 UTC 
Reopening as we started using EggToolbarEditor and EggEditableToolbar.
Comment 4 Lucas Rocha 2007-09-04 21:29:57 UTC 
It doesn't make much sense to re-open this bug because there's no short-term plan to consolidate toolbar editor into GTK+. If this happens in the future, we can create new bug report to keep track of that.

The specific issue originaly reported is fixed. So, I'm closing as FIXED again.