Re: [anjuta-devel] Glade catalog configure switch



On 03/03/2013 11:55 PM, Tristan Van Berkom wrote:

I'm not sure I follow your problem space. If Anjuta embeds the
libgladeui-2 widgets for editing UIs, and installs it's own catalog
files to whichever location it chooses, then what's to stop Anjuta
from informing Glade about the location of Anjuta's catalog files
(before initializing Glade) using GLADE_CATALOG_SEARCH_PATH ?

http://developer.gnome.org/gladeui/3.14/catalogintro.html

I appreciate the suggestion, but I see a couple of issues with this
approach:

1. While we could probably have our Glade plugin set these environment
variables, that solution feels like a hack for one specific problem that
the vast majority of our users won't have. I don't think something like
that belongs in the Glade plugin. And it would only work if you opened
the files from within Anjuta.

2. Glade files aren't always edited from within Anjuta. What would
happen if I opened a UI file from my file manager or from an e-mail or
bug report? In most cases the file association system would start Glade,
probably without the environment variables set, and it wouldn't work
anyway. I really don't want to have to set an environment variable every
time I open one of my UI files. I'm betting that most of us edit glade
files much more often than we run configure. Besides, Anjuta remembers
configure switches, and I assume that most Anjuta devs use Anjuta to
work on Anjuta, so this would be set and forget for pretty much anybody
that's affected by this change.

I can't speak for the rest of my team, but I think putting a hack in the
Glade plugin or having to set environment variables is a little messy.
IMO it's just better to have the build system make sure it goes to the
right place so that it always just works, no matter how you open our UI
files. The cost here is that we have to remember to pass an extra option
to configure, but in return we don't bother those that don't need it and
it works in all cases for those that do with no extra effort.

Thanks,
James




[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]