From: J. A. C. <sof...@cr...> - 2013-04-24 15:40:30
|
Assuming that most configuration items would not change from tree to tree, I think you could get very close to what you want by building filters for each tree. Then you wouldn't need to do much more than select the appropriate filter and change the destination and web site title. If you are making many changes to the options on other tabs, then a saved configuration would be nice. Allen Crider On 04/24/2013 07:33 AM, Michael Tiernan wrote: > On Wed, Apr 24, 2013 at 7:16 AM, Chuck Arnold <cc...@de...> wrote: >> If this seems like a useful endeavor I would like to see >> this as an added feature or enhancement. > > As a follow up to my follow up... > > I opened a ticket suggesting that the narrative web *configurations* > be set up in a way that allows for the saving/loading of specific > configurations. I think this would solve some of the problem you're > discussing. > > I have four trees in my gramps DB (I'm still a novice and learning as > I go) and I'd love to be able to print out any one of the four in a > narrative website easily but for each one I have to go through a bit > of chicanary to make them work. I create a configuration, save it, > then using a CLI, I copy the configuration saved to a {tree_name} file > and then when i want to print that tree, I reverse the process so that > the {tree_name} configuration becomes the default and then I can call > up the tool to dump the tree. > |