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

Design / discuss event-system to inform plugins as well as internal modules of any activity #45

Open
elkowar opened this issue Dec 22, 2022 · 1 comment
Labels
discussion Topics that needs design / architecture discussions topic-core Things related to the editor core topic-pm Things related to the plugin-manager

Comments

@elkowar
Copy link
Contributor

elkowar commented Dec 22, 2022

Plugins will need to react to events such as insertion, deletion, cursor movement, etc.
Similarly, things like a jumplist would need to remember cursor position after any jump and/or text insert action.
There are definitely a lot more of those things.
We should discuss a general event-system for these things, allowing us to modularize out any non-core components by having them simply register event-listeners and work in the background. Most, if not all things that rely on this can probably be expressed as plugins!

@elkowar elkowar added discussion Topics that needs design / architecture discussions topic-core Things related to the editor core topic-pm Things related to the plugin-manager labels Dec 22, 2022
@elkowar
Copy link
Contributor Author

elkowar commented Jan 4, 2023

Update: Event system has been discussed a good bit now. However, more detailed discussions on what events should exist and how the API should look still need to take place.

@elkowar elkowar added this to the Proper architecture milestone Jan 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
discussion Topics that needs design / architecture discussions topic-core Things related to the editor core topic-pm Things related to the plugin-manager
Projects
Status: Todo
Development

No branches or pull requests

1 participant