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
Save this until after the launch - recording now as an idea to consider for later.
In the loading of the tool, we use the setSubs method to sequence events that need to occur after other events. However, some of these events are scheduled later than they need to occur, and many of the events wait for some asset to be loaded externally before triggering internal code that performs things in the browser. We could achieve some performance improvements by cleaning up which events trigger what, to make sure that everything that could occur simultaneously to an asset download does occur. This assumes that the browser is able to achieve better performance by having multiple async requests at the same time.
The most likely candidate is that we wait to trigger the loadMetaData function in the map-view until the map is loaded from Mapbox; Mapbox loading takes 3-4 seconds, and most of the resulting funcionality doesn't need the map itself to be present.
Additional consideration while we're looking at improving the sequencing of the setSubs - eliminate errors like this one by making sure that code doesn't get called to early. These errors currently don't affect performance because the functions they happen in run fine later when triggered by user behavior, but would be good to eliminate:
The text was updated successfully, but these errors were encountered:
Save this until after the launch - recording now as an idea to consider for later.
In the loading of the tool, we use the
setSubs
method to sequence events that need to occur after other events. However, some of these events are scheduled later than they need to occur, and many of the events wait for some asset to be loaded externally before triggering internal code that performs things in the browser. We could achieve some performance improvements by cleaning up which events trigger what, to make sure that everything that could occur simultaneously to an asset download does occur. This assumes that the browser is able to achieve better performance by having multiple async requests at the same time.The most likely candidate is that we wait to trigger the
loadMetaData
function in the map-view until the map is loaded from Mapbox; Mapbox loading takes 3-4 seconds, and most of the resulting funcionality doesn't need the map itself to be present.Additional consideration while we're looking at improving the sequencing of the setSubs - eliminate errors like this one by making sure that code doesn't get called to early. These errors currently don't affect performance because the functions they happen in run fine later when triggered by user behavior, but would be good to eliminate:
The text was updated successfully, but these errors were encountered: