René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"De-circularize plotly.js require statements","articleBody":"@mdtusz \n\n**Latest list of circular dependencies:**\n- Plots \u003c --- \u003e Annotations\n- Plots \u003c --- \u003e Legend\n- Plots \u003c --- \u003e Axes (the only `Plots` calls in `axes.js` are `traceIs`)\n- Plots \u003c --- \u003e plotApi\n- plotApi \u003c --- \u003e Annotations\n- plotApi \u003c --- \u003e Shapes\n- plotApi \u003c --- \u003e Titles\n- plotApi \u003c --- \u003e Fx\n- plotApit \u003c --- \u003e Legend\n\n**Possible partial solutions**:\n- Make a component registry and register the components (e.g. Annotations, Shapes, Titles, Fx, Legend), so `plot_api.js` doesn't have to require the full component modules (similar to trace and subplot modules). **Blocking:** we'll need a centralized api for the component module, e.g. all component modules should have a `draw` method and possible and `init` method.\n- Use a more OO pattern (in the long term). Attach `relayout` and `restyle` to a plot object so that files requiring `plot_api.js` (e.g Annotations, Shapes and Fx) can use `gd.relayout()` instead of `plotApi.relayout(gd, ...)`.\n","author":{"url":"https://github.com/etpinard","@type":"Person","name":"etpinard"},"datePublished":"2016-02-03T17:06:42.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":3},"url":"https://github.com/236/plotly.js/issues/236"}