Quote:
Originally Posted by jackie_w
Yes, they might, but there are a variety of reasons why sharing to the public can be problematic. Mainly:
- some of them are variations on existing plugins (Modify Epub, KoboTouchExtended, EpubCheck) so I'm not going to tread on the toes of the original creators or other noble souls who try to maintain orphaned plugins.
- some of them have some overlap with standard calibre (e.g. epub-to-kepub, kepub-to-epub, epub2-to-epub3). I prefer to avoid confusing anyone.
- a lot of my Editor Tool plugins may not work 100% for all users, for all epubs. Not a problem when I'm using them myself because I know the limitations. On the first day of public release I'd probably be inundated with complaints about the 1% of corner cases that I don't care about (you'd probably be first in the queue
 ). This is when programming as a fun retirement hobby turns into PITA programming as real work. I've no desire to spend large amounts of time creating error-checks for people who might do something dumb or who just prefer to edit epubs differently to me. I'll leave the all-singing, all-dancing plugins to the professionals.
Having said all that I'm always happy to share code with other plugin hobbyists as a base for creating their own stuff. But I don't want ongoing maintenance responsibility - especially now - during the transition from python 2 to 3. |
BTW... I would be interested in those editor plugins... so I can see how they work and perhaps evolve them to my own use cases.....
