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 349265 - Help kill libegg
Help kill libegg
Status: RESOLVED FIXED
Product: tomboy
Classification: Applications
Component: General
unspecified
Other Linux
: Normal normal
: 1.4.0
Assigned To: Tomboy Maintainers
Tomboy Maintainers
: 520752 (view as bug list)
Depends on: 412130 520752
Blocks: 349256
 
 
Reported: 2006-07-30 10:50 UTC by Vincent Untz
Modified: 2014-05-25 02:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
GtkStatusIcon patch (40.88 KB, patch)
2008-03-24 20:04 UTC, Stefan Cosma
committed Details | Review

Description Vincent Untz 2006-07-30 10:50:42 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 Sven Herzberg 2007-03-07 17:30:17 UTC
Let's fix this for GNOME 2.20
Comment 2 Sandy Armstrong 2007-12-27 15:04:57 UTC
See bug #412130 for some insight into why we haven't acted on this yet (large deployments that want to upgrade Tomboy without being forced to upgrade gtk+/gtk#).

That being said, here is what needs to be accomplished:

1. Replace use of EggTrayIcon with GtkStatusIcon.  This will cause us to lose the current middle-click functionality (paste into Start Here note).  There might be some visual/behavior artifacts as well, since GtkStatusIcon is *not* a widget.

2. Replace use of EggAccelerator with GtkAccelGroup.  This is also used in the Tomboy tray code.  I haven't investigated it at all past that.

Fixing these bugs will be a big help in being able to distribute Tomboy as a "pure" gtk+ app on non-GNOME (or non-Linux) platforms like Maemo, OS X, and Windows.

I'd like to see a patch for fixing this, followed by a brief discussion about how to address the needs of the large deployments mentioned earlier.

Aside: I'm playing with GtkStatusIcon right now, and while using Ubuntu 7.04 (GNOME 2.18 era) I experienced runtime errors with the gtk-sharp bindings.  They seem to be working well since upgrading to Ubuntu 7.10 (GNOME 2.20 era).  I'm just making a note of this as a reminder to test older versions of Mono and gtk-sharp.
Comment 3 Boyd Timothy 2008-02-26 19:14:56 UTC
Setting the default assignee and QA Contact to "tomboy-maint@gnome.bugs".
Comment 4 Stefan Cosma 2008-03-24 20:04:45 UTC
Created attachment 107940 [details] [review]
GtkStatusIcon patch

Here is a patch that replaces EggTrayIcon with GtkStatusIcon
Comment 5 Sandy Armstrong 2008-08-02 15:39:56 UTC
*** Bug 520752 has been marked as a duplicate of this bug. ***
Comment 6 Sandy Armstrong 2008-08-02 16:06:52 UTC
Stefan, the behavior of this patch is perfect!  I'm just reviewing the code itself now, since this is kind of a messy area of Tomboy.  :-)
Comment 7 Sandy Armstrong 2008-08-02 17:50:56 UTC
I committed the Gtk.StatusIcon patch (with a few tweaks) in r2056.  Still to do before this bug is fixed:

2. Replace use of EggAccelerator with GtkAccelGroup.  This is also used in the
Tomboy tray code.  I haven't investigated it at all past that.
Comment 8 Sandy Armstrong 2009-02-02 08:25:47 UTC
I had some trouble wrapping my head around the way EggAccelerator is used in libtomboy. Removing from managed code shouldn't cause any trouble, though.
Comment 9 Sandy Armstrong 2009-03-01 17:05:20 UTC
Pushing to next cycle.
Comment 10 André Klapper 2009-08-04 14:19:44 UTC
(In reply to comment #9)
> Pushing to next cycle.

Is this still on the list? (As the code for fixing bug 349306 and bug 349308 is similar, but one module has to push the efforts...)
Comment 11 Sandy Armstrong 2009-08-04 15:48:19 UTC
Yes, the target is set as a bug to address this cycle. I hope we'll get to it, but it is not my highest priority right now.  Patches welcome.
Comment 12 Sandy Armstrong 2009-09-12 23:09:24 UTC
Next cycle, patches still welcome, etc.
Comment 13 Javier Jardón (IRC: jjardon) 2010-04-17 14:56:59 UTC
As bug #349306 is solved now, maybe you want to take a look
Comment 14 Jared Jennings 2014-05-25 02:35:51 UTC
Fixed 349265