Switch to OOP style code

This commit is contained in:
2026-02-04 00:38:11 +00:00
parent e3fc5323df
commit a62d4a18a8
50 changed files with 3011 additions and 3078 deletions

12
TODO.md
View File

@@ -10,19 +10,19 @@ Copyright 2025 Syed Daanish
```
* Next few super long boring things to do
* redo lsp threads such that no mutex needed for any rope stuff
* redo lsp threads such that no mutex needed for any rope stuff (necessary rn)
- Also make the classes own the methods in lsp
- This will mean that parsers/renderers and keystrokes will not need to be individually locked
- And so it will be much faster
- At which point the main thread can also be blocked on user input or lsp responses and still be fast
* Add a superclass for editor called Window (which can be popup or tiled)
* Add a recursive tiling class for windows
* Handled by a single renderer that calls and renders each window
- And a bg if no window open
* Make editor's functions into its own methods (classify it)
* Add a superclass for editor called Window (which can be popup or tiled) (done)
* Add a recursive tiling class for windows (done)
* Handled by a single renderer that calls and renders each window (done)
* Make editor's functions into its own methods (classify it) (done)
- While at it
- Seperate system functions into a class that branches to support local / ssh / server modes.
- Even lsp shouldnt be directly controlled because it can branch on local and server modes
- check wolfSSH stuff for remote editing
- Redo hooks as a engine of its own.
- And factorize renderer into its own class (and make it just return an array of the render without knowing teh x,y)
- which is just managed by the renderer