hoschi

Cool. You can "watch" the Github repo with the button in the right upper place beside "star" and "fork".

With the buffer events and especially `nvim_buf_call` of NeoVim it is possible to do everything without hacks.

this already works, just use `YodeCreateSeditorReplace`. The command creates a seditor and opens it in the current window. You can then use the created seditor like any other buffer. To open a selected code part in normal splits do:

:YodeCreateSeditorReplace :vsp <Leader>blt

Yode-Nvim can create more regions of the same file as well as a floating "window manager" for regions called "layout". Yode-Nvim syncs changes from regions to files in real time where you need to "write" the changes by hand with NrrwRgn.

fixed it

Splits are not based on content, but are controlled by a layout algorithm. For horizontal splits, for example, the size changes every time you create a new one. Yode-Nvim is based on the size of the seditors and enlarges/reduces them automatically. There are more layouting algorithms planned and they can be different for each tab, the code is already set up for that.

Yode (the POC 4 years before) itself only worked with a (JavaScript) AST to create seditors. Tree-sitter would have helped here to provide an AST for different programming languages uniformly directly in NeoVim. Yode-Nvim is more powerful than the first version because it operates on lines to create seditors. In this respect Tree-sitter doesn't matter for Yode-Nvim. If someone uses Tree-sitter to select code in visual mode, he can easily create seditors for code objects like functions. This is also possible without Tree-sitter, but you have to select the function yourself.

Demo page is just white background :(

there is a lot of that stuff in the readme on Github (icon top right corner). Ask me if something isn't clear :)

I tested Sencha, jQuery Mobile and Dojo 1.7 and 1.8 a week ago with my Nexus phone -> Dojo 1.8 wins clearly when it comes to performace of touch events and transitions :)