I got caught with my pants down! Not even having a .leo file at the center of my development for this project! Caught by the creator of Leo itself!
Jokes aside, I am honored. This is a great way to start my weekend! Like I said in the main thread about this project, I pushed a small milestone in the repo a few minutes ago: full leo browsing, headline and body. (still not optimised, debounced, nor editable) Going forward, I'll take a couple hours to study leoVue a little bit, to maybe make a tcp/ip communication instead of just stdIn/Out... I also have to study your leoFlexx plugin a bit more to see what else I can gather again from it to make everything easy and smooth! :) But on the short term, this weekend I'll probably just make the headlines and body text editable, being able to edit the outline structure along with it would be another nice milestone! I also have monday off (long weekend!) so perhaps I'll reach it! As a small explanation to start things up & help understanding : The main mechanic is that I'm using a simple stack of promises to keep track of what's asked of the leoBridge's side of things. The first 'asked' command by vscode interface is pushed on top of this stack, and resolved from the bottom so its first-asked first-served kind-of logic. The set of possible commands that it responds to is limited for now obviously. I knew nothing of the vscode extension api two weeks ago, so i'm pretty new to all this too! Please dont hesitate to ask for any clarification whatsoever, So all right for now, I'm going to bed! Cheers! :D -- Félix On Friday, August 30, 2019 at 3:20:35 PM UTC-4, Edward K. Ream wrote: > > I have just taken a quick look at the leointeg repo > <https://github.com/boltex/leointeg>. Some notes: > > As you will see, there are only four TypeScript files in the src folder. > They correspond roughly to the code in the leoflexx.py plugin > (--gui=browser). These files are concise. Their overall purpose is fairly > clear, but I have little idea of how they actually work. > > In several places Robert borrows code from leoflexx.py. I'm thrilled that > concepts such as *archived position* have become useful in a new context. > > I've cloned the repo and will likely use a recursive import script to > study it in detail. Not sure that Leo can import TypeScript files in a > Leonine way. > > gitk shows that work started August 10, and continued on 9 days from > August 13 to Aug 29. So this is rapid progress. > > It would be really cool to animate the gitk commits, showing (in Leo) what > each commit did. Leo git-diff command and other git utils provides the > basis for such an "animation". I'm tempted... > > Oh, how I wish Robert and I were cubicle mates. I'd love to ask him > questions, line by line about his code. This would give me a higher level > view than even the git-diff animation. For example, scripts/leoBridge.py > appears to be plain python, but how is it executed? Perhaps I should know > the answer, having written leoflexx.py, but I don't :-) > > Most of the rest of leointeg looks like VS-code glue: .json files, etc. > > *Summary* > > This project is tremendously exciting. The present code is compact and > powerful. I'll continue my studies. > > Edward > -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/17f53ab6-c694-4ffa-9fde-76fa7e56c3e3%40googlegroups.com.
