3 ms·
The most important point is expandability. Did it has an API or is it planned to add an API to extend the editor?
by progx 4y ago
The most important point is expandability. Did it has an API or is it planned to add an API to extend the editor?
- Deukhoofd 4y agoA third of the linked github readme is about how to do plugins.
- SpartanJ 4y agoAuthor here: The editor can be expanded via plugins and several features are presented as plugins (LSP, linter, formatter and auto-complete). But the plugins API it's not as friendly as other editors since I want to keep some control over the plugins. I think we already have many editors very expandable but also with very little to no control over the plugins/extensions environment, and that ends up creating a big mess for the final product (inconsistent UI, bad implementations, etc). Currently the plugins can only be implemented with C++ native code and new plugins will need to be merged into the project. I would like to keep control over the new features and supervise that the implementations are correctly done (mainly I care about plugins not locking the UI thread). I understand this can be bad for some but I want to keep a certain vision that needs some kind of control over the end product.