This adds an in browser kwic indexer. It loads the current standard name table xml using a fetch request then performs the indexing on the client side.
This is intended to be a test as I was having performance issues on my own test site and nowhere else. I also don't know if how I'm doing the indexing is the most efficient way. Some thing I did to try to optimize:
used javascript Set and Map objects, which are mandated to have sub-linear complexity in the JS specification
Build the entire DOM tree before adding to the main document
I'm not sure if this helps at all, but all the styles are moved to CSS and not inline.
Once the indexing is done the memory and CPU needed to display the page are similar to the statically built KIWC index files.
This adds an in browser kwic indexer. It loads the current standard name table xml using a fetch request then performs the indexing on the client side.
Once merged, it should be available on the cf website under: https://cfconventions.org/vocabularies/kwic-index.html
This is intended to be a test as I was having performance issues on my own test site and nowhere else. I also don't know if how I'm doing the indexing is the most efficient way. Some thing I did to try to optimize:
Once the indexing is done the memory and CPU needed to display the page are similar to the statically built KIWC index files.
See the discussion for more information.