I have now pushed our first attempt at implementing all this to PageEdit master.
So if you build your own, you can pull from master on PageEdit.
To test it you will need to take an epub and unzip it someplace and then open PageEdit and navigate to the OPF file inside the epub folder.
** IT WILL NOT YET WORK WITH OPF Files via Sigil **
If this change seems to be a real improvement for users when proofing/fixing files, we will then modify Sigil so that an OPF can be used with OpenWith in Sigil and that Sigil will properly set all of the file watchers for all of the files in the spine on launch so all changes made are caught.
FYI: It may have have rough edges since it was thrown together very quickly.
Treat it as Beta software
Also, if this works and we integrate it with Sigil, I can then enable intra-epub links in PageEdit (that go to other xhtml files in that spine).
Feedback Welcome! from those who can build PageEdit on their own and use an unzipped epub with it.
If in the end, people feel it really does not add much value to PageEdit, we can easily revert this change.
KevinH
Quote:
Originally Posted by KevinH
No promises but .... we are thinking about allowing PageEdit to accept on launch an opf or a simple sorted list of file paths in spine order as xml. Then have PageEdit dynamically build a navigation menu, and forward and back keys, so that a user of Sigil could use PageEdit to more easily visually proof and spellcheck the xhtml documents in the spine in sequence without having to go back to Sigil to just load the next chapter.
If a PageEdit user makes any change and then hits forward or back arrows, the user will be prompted to save or discard, and the next file on the list will be loaded automatically (with wraparound at each end of the list).
Would you use a feature like that? With it and the current spellcheck PageEdit has built in it should make final proofing and very very minor edits easier.
Is this worth chasing?
|