Quote:
Originally Posted by user_none
Some of the information about the EPUB is stored in GUI widgets and pulled out of it when needed. It's not all in one nice and easy to access place that can be decoupled from the GUI.
|
I hope the original designer of Sigil had a very good reason to do it like that. Personally, I would never have intertwined Sgil's GUI and business logic.
(Even if it wasn't for the fact that, when I was in university, it would almost certainly lower your mark by two points or so if you did something like that without a *very* good reason...)
OK... in that case, turning Sigil into an EPUB library is out. It would indeed be much better to just look at the code, and rewrite it in Python.
Quote:
|
All of the editors I mentioned can open and save epubs. They lack the advanced editing components such as a metadata editor but the basics and the starting point you've mentioned they already do.
|
OK, thanks. I did not know that.
Meh. No magic bullet there. It's the same as I implement specs for microcontrollers, only a lot bigger (and probably more ambiguous too, with things like "may have the option to... but does not require to...").
Quote:
|
Finally, understanding the epub format has a lot to do with calibre. I've implemented conversion for a number formats. Calibre's conversion pipe line is in -> OEB (basically the guts of an epub) -> out. That has helped a lot.
|
I can imagine.
Thanks, I will certainly look at that. I've set up a basic Python development environment to test some stuff. I just picked 3.3.2 (latest) for some eperimentation.
What version of Python does Calibre use at this moment? There is some (very small) stuff I may want to add to one of Kiwidude's plugins. I think it's a good exercise to get going with Python and take a first look at how Calibre actually works, but of course then I must use the same Python version as Calibre does.