Quote:
Originally Posted by jbacelar
Ah Kovid! you are great.
|
Indeed.
Quote:
Who needs a WYSIWYG editor?
With the code editor and the preview window, I think that's enough.
|
Agreed. An updating preview is enough. Edit, save, update preview. I often use LilyPond (a sheet music language, a bit like TeX), and one of its main editors, Frescobaldi, works like this. It's enough.
Quote:
Originally Posted by kovidgoyal
So to move this conversation along, here's a concrete offer. I offer to implement the *rest* part of it -- list of files, edit metadata, edit tocs, renaming/moving files, editing the spine, various automated actions from the Polish Books component -- if someone will volunteer to tackle the editor component.
I can set up a basic GUI shell that does most of that in a few weeks, and then let whoever volunteers work on the editor component. But, I will only spend the time to do that if I get a firm commitment from someone to handle the editor part. That committment will need to include ongoing support for fixing bugs in the editor component.
|
Thanks for this offer. If I had known anything about Python, and known more about GUI programming with QT (I'm normally one of the guys that does the stuff you never see, and what I did with GUI's was in C# and previously Delphi), I would have committed to this. As it stands now, I do not know if I have the skills (yet).
I need/want an option to edit EPUB. As I don't yet know if I can help to program it, however much I'd want to, I can at least offer to use it from the start (with Sigil as a backup), and test all the new functions.