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 349257 - Help kill libegg
Help kill libegg
Status: RESOLVED WONTFIX
Product: beagle
Classification: Other
Component: General
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Beagle Bugs
Beagle Bugs
gnome[unmaintained]
Depends on: 525428 662755
Blocks: 349256
 
 
Reported: 2006-07-30 10:32 UTC by Vincent Untz
Modified: 2018-07-03 09:53 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Vincent Untz 2006-07-30 10:32:33 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 Kevin Kubasik 2006-08-01 12:39:08 UTC
We should probably get all the different mono apps to coordinate on this, since its dumb for us all to be rewriting bindings. In addition, will this gtk code be available in the next release of gtk-sharp? If so, its really just a matter of waiting for that to hit the mainstream.
Comment 2 Vincent Untz 2006-08-01 12:48:24 UTC
AFAIK, the next gtk# binds GTK+ 2.10, so yes, it's only a matter of waiting for its availability :-)
Comment 3 Joe Shaw 2006-08-01 21:34:12 UTC
We are currently using the EggTrayIcon and at least some of the EggAccelerator stuff.  Unfortunately I think the latter was cut-and-pasted from Tomboy which may have done some of its own modifications.  I think the work there was done mostly for parsing the textual representation, like "<Alt>F12" to a real key combo.  We'll have to investigate further and possibly coordinate with Alex.
Comment 4 Jared Moore 2007-08-05 05:37:42 UTC
I could be wrong, but just grepping the source I can't find any reference to egg other than in beagle/glue/egg{accelerators,trayicon}.{c,h} and in the Makefiles. Has this been fixed without the bug being closed?
Comment 5 Debajyoti Bera 2008-01-03 01:02:16 UTC
I think the bug is referring to the presense of beagle/glue/egg{accelerators,trayicon}.{c,h} itself. From what I can tell, beagle-search uses some EggAccelerator code right now.
Comment 6 Debajyoti Bera 2008-03-31 03:31:26 UTC
Vincent, once we move the keybinding code from our app to gnome-keybindings, is there a way for the user to set it from our settings dialog ?

E.g. currently in our settings dialog, the user can set the shortcut for showing/hiding beagle-search. With this bug resolved, if I understand it currently, the user would be able to do this in a more generic way using gnome-keybindings. But would it still be possible for the user to use our settings dialog to set the shortcut ? Or is that not recommended anymore and users should only use gnome-keybindings.
Comment 7 Debajyoti Bera 2008-04-05 17:25:04 UTC
One more hurdle, about multimedia key. Beagle currently cut and pastes code from gnome-settings-daemon for handling multimedia keys. But I did not find any gtk_ code, e.g. replacement for example egg_accelerator_parse_virtual where the keystring could come from a multimedia key.
Comment 8 André Klapper 2018-07-03 09:53:41 UTC
Beagle is not under active development anymore and had its last code changes in early 2011. Its codebase has been archived (see bug 796735):
https://gitlab.gnome.org/Archive/beagle/commits/master

"tracker" is an available alternative.

Closing this report as WONTFIX as part of Bugzilla Housekeeping to reflect
reality. Please feel free to reopen this ticket (or rather transfer the project
to GNOME Gitlab, as GNOME Bugzilla is deprecated) if anyone takes the
responsibility for active development again.