Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Write an Article on "Plugin Handling" #8

Open
ilexp opened this issue Feb 24, 2018 · 0 comments
Open

Write an Article on "Plugin Handling" #8

ilexp opened this issue Feb 24, 2018 · 0 comments
Labels
Core Area: Duality runtime or launcher Editor Area: Duality editor or support libraries Help Wanted Contributions especially appreciated Page Request Creation of a new docs page / topic

Comments

@ilexp
Copy link
Member

ilexp commented Feb 24, 2018

Summary

Write a wiki article that deals with how Duality handles plugins and plugin reloads in the editor. This came up in a conversion on the chat, see here:

conversation

Analysis

  • Core and editor plugins
  • How they are loaded
  • How they are re-loaded
  • In which cases is a restart required and why
    • Why both need to be re-loaded when B depends on A and only A changes.
    • Why a restart is required on dependent reloads.
    • Why a restart is required on editor plugin reloads.
  • Approaches to reducing the frequency of restarts.
    • Define a common, infrequently changed "base" plugin A, and let core plugin B and editor plugin C depend on it, but not on each other.
@ilexp ilexp added Help Wanted Contributions especially appreciated Page Request Creation of a new docs page / topic Editor Area: Duality editor or support libraries Core Area: Duality runtime or launcher labels Feb 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Core Area: Duality runtime or launcher Editor Area: Duality editor or support libraries Help Wanted Contributions especially appreciated Page Request Creation of a new docs page / topic
Development

No branches or pull requests

1 participant