Libglade deprecated in favor of GtkBuilder
Bug #479347 reported by
Francesco Marella
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Entertainer Media Center |
Fix Released
|
Medium
|
Francesco Marella |
Bug Description
The GNOME Release team has officially deprecated libglade in favor of
GtkBuilder.
Some reasons:
* GtkBuilder is actively maintained.
* GtkBuilder can create non-widgets (like treemodels).
* It's one less library.
Entertainer should use GtkBuilder.
All the .glade files should be checked and modified if necessary.
Related branches
lp:~francesco-marella/entertainer/glade-less
- Matt Layman: Approve
- Jamie Bennett: Pending requested
-
Diff: 7030 lines (+2890/-3124)14 files modifieddocs/COPYING (+1/-0)
docs/DEPENDENCIES (+0/-1)
entertainerlib/backend/components/feeds/feed_utils.py (+0/-1)
entertainerlib/client/translation_setup.py (+14/-8)
entertainerlib/dialog.py (+103/-100)
entertainerlib/gui/system_tray_icon.py (+8/-7)
entertainerlib/tests/test_feedconfigtools.py (+0/-1)
entertainerlib/uis/log_dialog.ui (+55/-57)
entertainerlib/uis/manager.ui (+2049/-2170)
entertainerlib/uis/open_feed_source_dialog.ui (+54/-51)
entertainerlib/uis/system_tray_icon_menu.ui (+53/-61)
setup.py (+2/-2)
tools/po/entertainer.pot (+544/-658)
tools/translations_generator.py (+7/-7)
Changed in entertainer: | |
assignee: | nobody → Francesco Marella (francesco-marella) |
status: | New → In Progress |
Changed in entertainer: | |
status: | In Progress → Fix Committed |
Changed in entertainer: | |
milestone: | none → entertainer-0.5 |
status: | In Progress → Fix Committed |
Changed in entertainer: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Francesco, thanks for looking into this. Moving from libglade to gtkbuilder was definitely desired, but no one had the time to look into doing it.
I've noticed that you've been working on some branches for Entertainer the last couple of days. Once you feel that the branch is in a stable state, please propose it for merging into the future branch so that it can be reviewed by members of the team (this is Entertainer's standard workflow). Once the merge proposal is worked (i.e. responding to reviewer feedback), the branch can be approved, a commit message added, then our branch landing tool, Tarmac, can do the merging for us.