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 a Wiki Article on "Plugin Handling" #561

Closed
ilexp opened this issue Aug 25, 2017 · 3 comments
Closed

Write a Wiki Article on "Plugin Handling" #561

ilexp opened this issue Aug 25, 2017 · 3 comments
Labels
Documentation Area: Project documentation Task ToDo that's neither a Bug, nor a Feature
Milestone

Comments

@ilexp
Copy link
Member

ilexp commented Aug 25, 2017

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 Documentation Area: Project documentation Task ToDo that's neither a Bug, nor a Feature labels Aug 25, 2017
@ilexp ilexp added this to the Learning Curve milestone Aug 25, 2017
@ilexp ilexp modified the milestones: Learning Curve, General Jan 6, 2018
@BobGneu
Copy link
Contributor

BobGneu commented Jan 12, 2018

Do you mind if I do the exploration and put a draft together on this?

@ilexp
Copy link
Member Author

ilexp commented Jan 12, 2018

Nope, feel free to look into this 👍

@ilexp
Copy link
Member Author

ilexp commented Feb 24, 2018

Moved to the docs repo.

@ilexp ilexp closed this as completed Feb 24, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Documentation Area: Project documentation Task ToDo that's neither a Bug, nor a Feature
Development

No branches or pull requests

2 participants