You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should solve the “unresponsive page” problem. Web workers are specifically designed for this sort of issue. The main difficulty will be that fluid.js contains a fair bit of DOM-manipulating code (mainly using d3.js to make new elements and insert them into the page), but web workers don’t have direct access to the DOM.
Initial experiment: put importScripts('fluid.js') into a worker and run from index.html
Separate creation of chart element from insertion into DOM
Return (id $\mapsto$ fig) map from PureScript main?
Break dependency on d3-selection (and other d3 modules that use DOM)?
import { loadFig } from ('./output/App/Fig/index.js') idiom to run PureScript functions directly?
Drop runAffs helper for processing arrays of Aff, in favour of runAff'
Should solve the “unresponsive page” problem. Web workers are specifically designed for this sort of issue. The main difficulty will be that
fluid.js
contains a fair bit of DOM-manipulating code (mainly using d3.js to make new elements and insert them into the page), but web workers don’t have direct access to the DOM.importScripts('fluid.js')
into a worker and run fromindex.html
main
?d3-selection
(and other d3 modules that use DOM)?import { loadFig } from ('./output/App/Fig/index.js')
idiom to run PureScript functions directly?runAffs
helper for processing arrays ofAff
, in favour ofrunAff'
drawFig’
,drawFile’
specialisations ofrunAff'
See also:
The text was updated successfully, but these errors were encountered: