[DiapDealer]

Also... the existing GUI will naturally be the editor for configs (both new and existing ones that have been loaded), but I'm thinking there's also going to need to be functionality to safely rename/delete existing configs.

What are your thoughts on which xhtml files are processed in the various scenarios?

1) I'm imagining that an Automated List run should process all files with bk.text_iter(). Because other tools in the same Automated List would not limit themselves to the same files that TagMechanic would single out with Book Browser's bk.selected_iter() anyway. If you need that kind of granularity, use the Full or Minimal GUI.

2) The Full GUI and the Minimal GUI scenarios will use the existing files selected in Book Browser's bk.selected_iter() (like it is for Full GUI now). Mainly because changing that in Full GUI mode would be a large step away from long-standing behavior, and even if I did allow the selection of files directly in Full GUI mode, the Minimal GUI would not have the ability to do anything but pick the config and run. So it's either all text files or Book Browser's bk.selected_iter() for the Minimal GUI. I'm leaning toward the latter for consistency.

Thoughts?