Thread: Plugins
View Single Post
Old 09-20-2019, 02:00 AM   #4
BetterRed
null operator (he/him)
BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.BetterRed ought to be getting tired of karma fortunes by now.
 
Posts: 21,789
Karma: 30237628
Join Date: Mar 2012
Location: Sydney Australia
Device: none
Quote:
Originally Posted by KevinH View Post
No, PageEdit will not support Plugins as that would mean having to copy a huge body of code that enables plugins as well as adding a complete Python 3 interpreter.
Fair 'nuff

Quote:
Originally Posted by KevinH View Post
That said, if proselint highlights a point in CodeView as most validator plugins do, why not launch PageEdit on that one xhtml file using the pencil icon and use the Find built into PageEdit to navigate to where you want to fix. Do all your long prose fixes in PageEdit and Save and Exit back to Sigil and rinse and repeat.

Alternatively you could add a bunch of FIXME strings in Sigil first and then search for and fix each in PageView all at once.
If I pasted FIXME's in the code the by the time I got to PageEdit I'd forget what the problem was :lol:

Thinking about it a bit more, even with Sigil 0.9.14, proselint errors would still throw me into CodeView rather than Book View, so I'd be flipping from CV to BV, back to CV... ad-infinitum. I think I'd rather run PageView alongside Sigil and keep them in synch manually - until someone can come up with an interprocess CodeView->PageView real-time synch button

One of the factors that makes me dislike editing content in CodeView is the limitation to monotype fonts (Consolas, Lucinda etc). That's fine for examining and editing 'code', but for me at least it's not fine for reading and editing 'content' - how many users have Preview set to a fixed width font.

Are there any technical reasons for this restriction. The calibre book editor has no such restriction - but it doesn't have a proselint plugin



Minor irritant I've been meaning to mention 'forever' - the 'Plugin' item in the menu has no accelerator key, Alt+P would seem to be available.

Quote:
Originally Posted by DiapDealer View Post
There are no plans to add plugin support to PageEdit that I'm aware of.

Two different installations of Sigil will inherently use the same settings. I'm not entirely certain that would be wise with a pre-0.9.15 version and 0.9.15+ version. But I could be wrong. It wouldn't hurt to try, though, as long as you make good backups of your preferences before-hand.
On thinking about it, sharing preferences wouldn't be critical or maybe not even desirable. But I'm going to try running Sigil and PageEdit and doing the synch manually. For reasons I can't comprehend I imagined proselint would interact with BV in Sigil 0.9.15. Whilst I haven't tried it, its London to a brick on it doesn't.

Thanks - BR
BetterRed is online now   Reply With Quote