On Thu, Jan 6, 2022 at 9:47 PM Félix <[email protected]> wrote: > > > do you plan to do about Leo's importers? > Yeah, ill transliterate the importers too (probably last though) >
I am still considering how to fully integrate Vitalije's new python importer into the main importer framework. I'll let you know what I decide. > >Will leojs continue to use a bridge to Leo for some commands? > Not sure yet, in fact I dont know yet if leointeg will somewhat be > absorbed in leojs, or the opposite... > That's fine. No rush. *More thoughts about leojs* > > - Since leojs is somewhat (in a sense) the 3rd rewrite of leointeg, and > that I was learning all those APIs and code bases at the same time, and > also because I write leojs solely with leointeg, I have now spotted many > small bugs or annoyances in leointeg (not even all noted in leointeg's > issues yet) that I will abstain of reproducing in leojs. (and fix in > leointeg later this year) > I am enjoying your corrections. Please keep them coming. > *New thing I want to try out* -> right after stabilizing the > outline-editing that I just managed to finish last week, is the possibility > of running vscode+leojs standalone in the browser : > > see* https://code.visualstudio.com/blogs/2021/10/20/vscode-dev > <https://code.visualstudio.com/blogs/2021/10/20/vscode-dev> * > and* https://vscode.dev/ <https://vscode.dev/> )* > > That's way cool. It would put leoflexx.py to rest for good :-) 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/CAMF8tS3qi7a0RZTsi5A4%3D-XCHan6pwo08PJoJD%2Bt1PP5bWGASw%40mail.gmail.com.
