On Fri, Jun 26, 2020 at 2:33 PM Félix <[email protected]> wrote:
Wow!! I would be delighted to have any help I can get with leoInteg! > Glad it's ok with you. The more I study vs code, the more I think it is a great platform for hosting Leo's bridge. > ...please wait before I do that before branching off dev... > Heh. I have lots of studying to do first. Yesterday I spent over an hour getting typescript in 5 minutes <https://www.typescriptlang.org/docs/handbook/typescript-in-5-minutes.html> to work, hehe. I made every conceivable mistake setting up .vscode/launch.json and test/ekr_ts_tests/tsconfig.json. It was all good. This is how I learn. *sidenote: I was wondering why you're talking about electron.... I just > looked it up, I thought vscode was a fork of atom, ... turns out they're > both forks of electron! * > I had forgotten that electron just draws web pages using chromium <https://www.chromium.org/Home>! This means that we get all the great w3c technologies and decades (centuries? millennia??) of rendering engineering. The architecture (master/renderer processes <https://www.electronjs.org/docs/tutorial/application-architecture#main-and-renderer-processes>) seems like an excellent foundation. I am also thinking that vs code will provide a more natural host for Joe Orr's great work. > *About Syntax Coloring Strategy In LeoInteg: * > > Indeed, syntax coloring is not that trivial as I originally thought so... > I am hoping that Leo's syntax can be an embedded language <https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide#embedded-languages> specified with a single embeddedLanguages contribution point. What do you think? As you say, handling @others is going to take considerable work. 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/CAMF8tS2M6-_y8pAmSLvuVLSNJWX8Ts%3Dv5GUgnO3RvjDTnqaFSw%40mail.gmail.com.
