Filipp Vakhitov 5f2baefc6c Introduce new interface for VimOutputPanel to support the output panel in Fleet ... Why is the old interface bad? - it is not obvious. You cannot create a new panel or check if it is already created. Only "getOrCreate" it - output panel is bound to editor while in Vim it is global - we have the `isActive` field and the `clear()` method at the same time, because interface implies that you store the same instance of the panel and reactivate it for each output and I don't like it. We also can forget to call `clear()` after reusing panel - we cannot "build" output before showing to make the panel more efficient. With multiple carets we can only cal `output(oldText + newText)` for each caret, and it is bad. (imagine we have global command with a lot of matches and for each time we will need to call the `output(oldText + newText)`) - the `output()` method shows panel, activates it and updates it - there are more things that I do not like, but the points above should be already enough		2024-07-08 13:09:08 +03:00
..
src	Introduce new interface for VimOutputPanel to support the output panel in Fleet	2024-07-08 13:09:08 +03:00
build.gradle.kts	Update gradle plugin to beta 8	2024-07-03 19:39:55 +03:00
Evolution.md	Add update to the evolution	2022-12-02 12:03:58 +02:00
gradle.properties	Set up publishing of the vim-engine library	2023-07-20 16:50:14 +03:00