--enable-spell-checking how to implement

[kevinh...@gmail.com]

I understand from reading that Chromium spell checker should be available in contenteditable elements by passing --enable-spell-checking. I do not know where to pass this.  Do I have to re-build nw.js and pass it as an argument then?  Rebuild node?  run install --enable-spell-checking ?  I have an app up and running but still am pretty unfamiliar with the ins and outs of nw.js.  There seems to be a lot of layers to this technology that I don't quite grasp.  Any help would be appreciated.  Thanks.

[John Peat]

In your package.json, add a chromium-args line - something like this

{

  "name": "APPNAME",

  "main": "index.html",

  "chromium-args": "--enable-spell-checking"

}

That works AOK for me

[kevinh...@gmail.com]

Thanks, yes, that did it.  I should have known since I'm already using chromium-args.

On a related subject, happen to know if there is an API so the user can add words to the dictionary?

[Murray Hopkins]

This might be relevant by way of background info.

https://github.com/nwjs/nw.js/issues/6654

I am now looking at 3rd party options because the native chrome functionality seems restrictive and I need something now. 

Please post any progress you make.

Cheers,

Murray

--
You received this message because you are subscribed to the Google Groups "nw.js" group.
To unsubscribe from this group and stop receiving emails from it, send an email to nwjs-general...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[John Peat]

I looked at third-party options too (Nanospell) - when I saw the cost I quickly realised that the Chrome checker would be fine-and-dandy! :)

The thing is, if you're spell-checking an HTML Input component you can make your own spell-checker (there are several written in JS already) - it all comes down to whether it's worth your time OR money to get this working "just so"?

[kevinh...@gmail.com]

I know what you mean.  I have made an implementation using Typo.js, but after attempting to write a UI in JS that competes with the performance of core code, it seems quite hacky in comparison, so I am tending to think also, "Chrome spellchecker would be fine-and-dandy".  Nevertheless, the stubbornness in me can't seem to leave it alone.  I made a post on SO looking for suggestions for the UI, but haven't had any replies.  If someone has ideas, I'd be interested in hearing:

https://stackoverflow.com/questions/51032808/implementing-an-as-you-type-spell-checker-ui-for-type-js

On Monday, June 25, 2018 at 7:37:36 PM UTC-6, kevinh...@gmail.com wrote: