I thought I'd drop by to say thanks for the Editor plugin feature.
Now I finally bit the bullet and read through the demo I realise it is not nearly as difficult as I had anticipated. In fact I think the endless [code - test ...] loop is faster than with the User Interface Action plugins.
This is really going to speed up my incessant book tweaking as I no longer need to keep switching between the Editor and my UIA plugins. What a joy!
I've been using the excellent Container classes for quite a while now and I wonder whether you might consider adding some convenient extra properties. For example, anyone who regularly tweaks ebooks is likely to need:
Code:
for name in [n for (n, lin) in container.spine_names]:
do stuff to an HTML page
on a regular basis. It would be convenient to just code something like:
Code:
for name in container.spine_list:
do stuff to an HTML page
I also use a spine list when I want to make sure a selection of tweaked names is displayed in spine order.
Similarly properties for the following may be useful to other tweakers:
- list of CSS names
- list of all image names
- list of raster image names
- list of svg image names
- cover image name
- cover page name
- NCX name
- nav name
- list of spine names which appear in the TOC
If you're amenable to the general idea but lack the time, I'd be happy to have a first stab at the code for your consideration.