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/afaab2ec-08cf-459f-af5a-9674416916f6%40googlegroups.com.
