y-ack / e Goto Github PK

things that need to be done

• merging the editor and the interface into one
• make WindowTree and Pane into one
• create split pane function that can be used to easily generate branches
• give every class a rust-doc i do not want to ever look at this in 5 years and be confused at what the fuck everything is

isn't necessary but i think it would be nice if there was some way to dynamically load backends instead of having all of them statically linked into the editor

we should probably have some of the following

• name and version information
• custom variables for easy configuration
• some standard way for users to document their package so it is easier for users to interact with

we also need to figure out how each package should interact with each other in a global space

handle! keys! properly!

Originally posted by @y-ack in #21 (comment)

a lot of useful features for a language including contextual autocomplete can be satisfied with an LSP and it's bad to deny that

https://github.com/gluon-lang/lsp-types
https://microsoft.github.io/language-server-protocol/

LSP usage will of course be optional but I think it would be a good idea if we had LSP support integrated into the editor itself
whether this should be implemented in Lua or in Rust will probably be considered if we ever get around to this

eventually look into making a new block/window subclass that only draws borders when given rules are satisfied (to illusion combined border)

• block/window subclass
• border rules
• default rules only draw one border along siblings
• border rules configurable via lua

the current window that is being edited should probably be stored somewhere and then the reference is swapped with another window

• Buffers
• Interface
  • Windows
    • Configuration for how they are displayed.
  • Modeline

will add things over time just need something to put in todo project

yeah

clean up implementations and expose to lua
😔

point can probably end up in illegal states right now due to just incrementing/checking point.column, when it needs to wrap at lines,
so there need to be functions to abstract trying to handle point motion linearly

Originally posted by @y-ack in #21 (comment)

yeah,

when deleting content in the demo, you can visibly see that the tree is parsing at an incorrect offset

need to look at