Can't use Glade 3.10.2 with Shotwell
Submitted by Eric Gregory
Assigned to cli..@..ba.org
Link to original bug (#718133)
Description
---- Reported by eric@yorba.org 2011-12-16 13:14:00 -0800 ----
Original Redmine bug id: 4501
Original URL: http://redmine.yorba.org/issues/4501
Searchable id: yorba-bug-4501
Original author: Eric Gregory
Original description:
I'm getting a "catalog not found" error in Glade when trying to run ./sw-glade (and after building the .so). I suspect this is because I'm running the latest version of Glade, which is not available in Oneiric.
Glade 3.10.2 can be found here:
Related issues:
- related to shotwell - 5066: Add Tag and Modify Tag do not work (Fixed)
---- Additional Comments From shotwell-maint@gnome.bugs 2013-05-01 11:38:00 -0700 ----
History
Comment 1
Updated by Adam Dingle over 1 year ago
- Assignee set to Clinton Rogers
Comment 2
Updated by Adam Dingle over 1 year ago
-
Assignee deleted (
<strike>
_Clinton Rogers_</strike>
)
Comment 3
Updated by Eric Gregory over 1 year ago
It might be worth re-investigating if we still need to generate a shared library for Glade. We don't for Geary and it works fine.
Comment 4
Updated by Adam Dingle over 1 year ago
Right. I still hope we can fix this for 0.12, but have unassigned it for the moment since other bugs are a higher priority.
Comment 5
Updated by Adam Dingle over 1 year ago
-
Target version deleted (
<strike>
_0.12_</strike>
)
Comment 6
Updated by Adam Dingle over 1 year ago
- Target version set to 0.13
Comment 7
Updated by Adam Dingle over 1 year ago
- Assignee set to Clinton Rogers
Comment 8
Updated by Clinton Rogers over 1 year ago
- File works_with_glade.diff added
- Status changed from Open to Review
- % Done changed from 0 to 70
Comment 9
Updated by Clinton Rogers over 1 year ago
- Status changed from Review to 5
- % Done changed from 70 to 100
- Resolution set to fixed
Comment 10
Updated by Clinton Rogers over 1 year ago
- Status changed from 5 to Open
- % Done changed from 100 to 20
Reason for reopening:
Glade doesn't 'know' about TextEntryDialog objects, so the 'add tags'/'modify tags' dialog currently can't be edited from within Glade (other dialogs in the application can still be viewed and edited as expected).
Comment 11
Updated by Eric Gregory over 1 year ago
TextEntryDialogs are of course native to Shotwell and not Gtk. Is this what the shotwell.so mechanism was built for? Because I'm sure we could find a simpler method to do the same thing.
Comment 12
Updated by Clinton Rogers over 1 year ago
I'm looking into this at the moment; I believe that this is what the 'catalogue' mechanism is intended for - you can tell Glade about types that are composed of other types it already knows about and have them work as expected (I think).
The right way to solve this may be through that...
Comment 13
Updated by Eric Gregory over 1 year ago
We decided to avoid this in Geary for simplicity. The problem with the .so mechanism is you end up with a Catch-22 where the code depends on Glade and Glade depends on the code.
The other way to solve it is to not define the dialog in Glade, just the UI that goes inside of it (put 'em in a frame or box) and then in the code load that frame/box into a hard-coded dialog object.
Comment 14
Updated by Clinton Rogers over 1 year ago
- Status changed from Open to Review
- % Done changed from 20 to 50
-
Resolution deleted (
<strike>
_fixed_</strike>
)
Went with Eric's suggestion from comment 13.
Comment 15
Updated by Clinton Rogers over 1 year ago
- Status changed from Review to 5
- % Done changed from 50 to 100
- Resolution set to fixed
Comment 16
Updated by Charles Lindsay 7 months ago
- Status changed from 5 to Fixed
--- Bug imported by chaz@yorba.org 2013-11-25 21:55 UTC ---
This bug was previously known as bug 4501 at http://redmine.yorba.org/show_bug.cgi?id=4501 Imported an attachment (id=262208)
Unknown Component Using default product and component set in Parameters Unknown milestone "unknown in product shotwell. Setting to default milestone for this product, "---". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
Version: 0.13
Resolution: RESOLVED FIXED