Plugins

[BetterRed]

I've run into a 'con' regarding the removal of BookView.

I have been having a look at Doitsu's proselint plugin, and I quite like it. However I dislike editing 'content' in Sigil's CodeView - i.e the text that people read as opposed to the code that renderer's process. The sort of checks this plugin performs can lead to the re-writing of many sentences and even several contiguous paragraphs.

Given proselint is a content evaluator, it would be much better to have it available in PageEdit. Are there any plans to port Sigil's plugin capabilities to PageEdit?

Meantime I could install an older version of Sigil and use Book View. Can anyone offer any guidance on the best way of having two versions of Sigil installed simultaneously on Windows - preferably sharing the same settings.

If I could I'd rename the thread "PageView Plugins"

BR

[KevinH]

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.

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.

[DiapDealer]

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.

[BetterRed]

Originally Posted by KevinH

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

Originally Posted by KevinH

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.

Originally Posted by DiapDealer

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

[Doitsu]

Originally Posted by BetterRed

One of the factors that makes me dislike editing content in CodeView is the limitation to monotype fonts (Consolas, Lucinda etc).

You can specify any font, by changing the following line in sigil.ini.

code_view_font_family_standard=Consolas

[BetterRed]

Originally Posted by Doitsu

You can specify any font, by changing the following line in sigil.ini.

code_view_font_family_standard=Consolas

Would be irritating when I want to switch back to monotype. I don't mind flipping a font in preferences - but having to close the program. edit a file, save it, and restart the program to change fonts would be a PITA.

A proselint plugin for calibre would be a better solution

BR

[Turtle91]

There must be a way to change the font options for CV.... I just looked at the list in my version of Sigil (9.18 on Win64) and it includes the Barcode font I installed many moons ago.
I can't see someone including that as one of the limited standard fonts. Unfortunately, I can't recall doing anything special to add that font. Perhaps Diap or Kevin know how that could have been accomplished??

[DiapDealer]

Originally Posted by Turtle91

There must be a way to change the font options for CV.... I just looked at the list in my version of Sigil (9.18 on Win64) and it includes the Barcode font I installed many moons ago.
I can't see someone including that as one of the limited standard fonts. Unfortunately, I can't recall doing anything special to add that font. Perhaps Diap or Kevin know how that could have been accomplished??

You didn't do anything special. Sigil/Qt populates the Code View font choices with only system fonts that are identified as mono-space fonts. Just installing a new mono-spaced font on your OS is enough to have it show up in the Appearance prefs for Code View.

[BetterRed]

Originally Posted by DiapDealer

You didn't do anything special. Sigil/Qt populates the Code View font choices with only system fonts that are identified as mono-space fonts. Just installing a new mono-spaced font on your OS is enough to have it show up in the Appearance prefs for Code View.

I appreciate the sentiment (nobody wants to code in TNR) - but apart from that is there any reason that all fonts shouldn't be available in the drop down?

BR

[DiapDealer]

Other than tradition and most coders' preferences, there's no functional reason that I know of (but I could be mistaken). Never really thought about it, I guess. I just assumed that like me, most coders would lose their minds using variable-width fonts for code/markup. *shrug*

[BetterRed]

Seems to be OK if I change it in the ini file, but doing that whenever I want to change focus from editing code to content is a PITA (and therefore dangerous)

Added : oops: I'm not sure it is OK, after changing code_view_font_family_standard to Arial in the ini file, when I looked at Preferences it was showing Courier.

I'll run PageEdit alongside Sigil/proselint and eyeball synch

BR

[Doitsu]

Originally Posted by BetterRed

Added : oops: I'm not sure it is OK, after changing code_view_font_family_standard to Arial in the ini file, when I looked at Preferences it was showing Courier.

Think of the Sigil Code View font preference as a kind of Schrödinger's cat. Changing the code_view_font_family_standard value definitely works, but if you open the Preferences dialog box to double-check the setting, Sigil will reset it to the default monospaced font.

Originally Posted by DiapDealer

Other than tradition and most coders' preferences, there's no functional reason that I know of (but I could be mistaken). Never really thought about it, I guess. I just assumed that like me, most coders would lose their minds using variable-width fonts for code/markup. *shrug*

I also prefer monospaced fonts for European languages, however, Courier New (and other monospaced fonts) usually don't render non-Latin text well and I often have to edit sigil.ini to select a non-monospaced font. Also, users with dyslexia apparently often use Comic Sans (a sans-serif font), if no special dyslexic font, e.g. OpenDyslexic is available.

How about adding a "Monospaced fonts only" check box below the Code View Standard Font drop-down box or removing the monospaced fonts filter altogether?

[BetterRed]

Originally Posted by Doitsu

How about adding a "Monospaced fonts only" check box below the Code View Standard Font drop-down box or removing the monospaced fonts filter altogether?

I was going to make a similar suggestion, even edited a screen shot, but I put it aside after the oops - I'll attach it anyway

I ran a 50K word document through proselint today, and did the corrections in PageEdit, wasn't as tedious as I thought it might have been, I'll post a couple of 'suggestions' in the proselint thread.

I tried to dock the Validation results window on the right edge, but it didn't want to dock there, I could only get it to dock on the bottom edge. I had no trouble docking/undocking the Preview panel on the right edge - so I don't think its me.

BR

[DiapDealer]

The validation results widget is definitely restricted to the top/bottom dock areas.

[BetterRed]

Good to know it wasn't my ineptitude - but why?

BR