From: Danuvius <dan...@gm...> - 2008-08-30 23:23:07
|
Is there a constant or a function that returns the plugin directory? I would like to store a configuration file that is used to remember plugin options set by the user. ... basically I'd like to get back: /home/user/.gramps/plugin/ but obviously in a reliable way, in case it is different from the standard linux directory used for gramps. Sincerely, Danuvius |
From: Danuvius <dan...@gm...> - 2008-08-30 23:45:58
|
Argh! I notice after much pointless looking around, that GRAMPS (or at least GRAMPS 3) already remembers Option settings. Or at least it seems to. Is that an official feature? (To override the plugin-specified defaults with the user's last specified settings?) Sincerely, Danuvius On Sat, Aug 30, 2008 at 7:23 PM, Danuvius <dan...@gm...> wrote: > Is there a constant or a function that returns the plugin directory? > > I would like to store a configuration file that is used to remember > plugin options set by the user. > > ... basically I'd like to get back: /home/user/.gramps/plugin/ but > obviously in a reliable way, in case it is different from the standard > linux directory used for gramps. > > Sincerely, > > Danuvius > |
From: Brian M. <br...@gr...> - 2008-08-31 16:24:43
|
> Argh! I notice after much pointless looking around, that > GRAMPS (or > at least GRAMPS 3) already remembers Option settings. Or > at least it > seems to. > > Is that an official feature? (To override the > plugin-specified > defaults with the user's last specified settings?) Yes, that is the way Gramps was designed. User option selections are stored in ~/.gramps/report_options.xml If you delete that file, the defaults will be used. ~Brian |
From: Danuvius <dan...@gm...> - 2008-08-31 22:57:27
|
Lest my frustration be misconstrued: That's great! =) Not being aware of it, I was trying to put together something that did the same thing specifically for my plug-in. Thanks for the confirmation! Sincerely, Danuvius On Sun, Aug 31, 2008 at 5:24 PM, Brian Matherly <br...@gr...> wrote: >> Argh! I notice after much pointless looking around, that >> GRAMPS (or >> at least GRAMPS 3) already remembers Option settings. Or >> at least it >> seems to. >> >> Is that an official feature? (To override the >> plugin-specified >> defaults with the user's last specified settings?) > > Yes, that is the way Gramps was designed. User option selections are stored in ~/.gramps/report_options.xml > > If you delete that file, the defaults will be used. > > ~Brian > |
From: J. S. <jul...@gm...> - 2008-09-01 04:29:59
|
2008/8/31 Danuvius <dan...@gm...>: > Is there a constant or a function that returns the plugin directory? Even if you already found you don't need the answer, it is: USER_PLUGINS = os.path.join(HOME_DIR, "plugins") Don't hardwire it to ~/.gramps/plugins (the usual value). I usually run several versions of GRAMPS and change the value of HOME_DIR for each so that they don't conflict with each other. In fact, the default value for HOME_DIR changes depends on the platform, but can also be changed thorugh environment variables. The logic is in src/const.py.in Julio |