Browser Extension

[chrissimon-au]

Is your feature request related to a problem? Please describe.
A browser extension that provides IDE-like Contextive support for any given webpage (hover/autocomplate for domain specific terminology).

Describe the solution you'd like
An extension in each of the major browsers (chrome/derivatives, firefox, edge, safari...)

Describe alternatives you've considered
App-specific addins/plugins/extensions.

Additional context
Links that may help:

https://github.com/davedawkins/sutil-template-chromex/tree/main
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Build_a_cross_browser_extension

[chrissimon-au]

Open Questions

Configuration

After #54, when working with a file in the IDE, contextive will know which definitions apply by searching up the folder tree to find the nearest *.glossary.yml file which implicitly applies to all files in the subtree underneath it.

Even if all possible *.glossary.yml files are made available at a given URL, how will the browser extension know which context applies when working on a given page?

Proposal is to define a new configuration file which effectively maps URL globs/regexes and/or page content globs/regexs to contexts. This configuration file would be hosted at it's own URL, and configuring the browser extension is just a matter of pointing at this file. The file would look something like:

{
 "contexts": {
 "contextAName": "url to definitions file",
 "contextBName": "url to definitions file"
 },
 "pageMaps": [
 {
 "matches": {
 "url": "*",
 "title": "Context A",
 "content": "*"
 },
 "contexts": [
 "contextAName"
 ]
 },
 {
 "matches": {
 "url": "*",
 "title": "Context B",
 "content": "*"
 },
 "contexts": [
 "contextBName"
 ]
 }
 ]
}

[chrissimon-au]

An alternative under consideration, to keep with the principal of distributing per-context configuration would be a list of objects that represent glossary/activation settings.

[
 {
 "glossaries": [
 "https://glossary.company.com/path/to/context-part1.glossary.yml"
 "https://glossary.company.com/path/to/context-part2.glossary.yml"
 ],
 "activations": {
 "urls": [
 "https://somesite.com/*",
 "https://anothersite.com/part2/*"
 ]
 }
 }
]

At launch the activations would only allow defining a set of url globs. Over time it could be expanded with other keys that permit activating on the basis of page titles or a content match, tbd.

This would easily allow to have all org glossaries shown on the same sets of pages (e.g. the wiki domain, or email domain)

Or to have a list of objects where each context is constrained to a particular domain.

[chrissimon-au]

Browser extension is now live and documentation added.