Wow!! I would be delighted to have any help I can get with leoInteg! (later today/tonight I will merge the branch I'm on with 'dev' to give multiple opened files capabilities to the dev branch. making leoInteg somewhat "*seriously usable" *so please wait before I do that before branching off dev... just a suggestion... )
*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! * *About Syntax Coloring Strategy In LeoInteg: * Indeed, syntax coloring is not that trivial as I originally thought so... First thing I will need do to continues improving the syntax-coloring is make sure a selected node not only receives it's body content, but also the language the node 'begins' in. (when @language set in a parent node) That will set the original language of the node, up to some possible @language elsewhere in the node. (applicable syntaxes definitions are then applied from one @language directive up until the next one is encountered) As you can see in the 'dev' branch, a 'syntaxes' folder is now present to handle syntax coloring. In it, I have defined the "Leo Body" syntax, for body content not directly affected by an @language directive, given it the 'scopeName' * "source.leobody".* (see last line of leobody.tmLanguage.json in /sintaxes) when a body pane 'Starts' in python by virtue of his parent's body being in python at the point of insertion of the @others, or because it starts with "@language python", it will be given the scope name 'token' " *source.leoBodyPython*". for which leobodyPython.tmLanguage.json in /sintaxes will have to be written.... and so on for each language suported by Leo. I dont think we shoud re-use the already defined scope / tokens such as *'source.python'* already defined and available in vscode, because we want to give the same highlights as in Leo, not vscode. (Remember the base philosophy of leoInteg: mimic and reproduce Leo, don't jump on what's available just because it is) So please take the time to read and understand the contents of the /syntaxes folder, and also the syntax guide : https://code.visualstudio.com/api/language-extensions/syntax-highlight-guide ... (or maybe you already understand all of this? ...I didnt get anything on my first read! but i'm a bit sleep-deprived lately) Ok i'm not going to spend hours writing details about the syntax coloring I'v setup so far ... I'd better go finish the multi-file support for tonight and let you browse through what i've done so far in /syntaxes and wait for questions and remarks... So that's it for now I'll write some more details tonight or tomorrow morning :) thanks again and please don't hesitate to ask about anything or suggest better options! -- Félix On Friday, June 26, 2020 at 9:35:41 AM UTC-4, Edward K. Ream wrote: > > On Friday, June 26, 2020 at 6:30:03 AM UTC-5, Edward K. Ream wrote: > > I am presently watching this VS Code tips and tricks >> <https://channel9.msdn.com/Events/Build/2020/BOD103?ocid=AID3012654&WT.mc_id=build2020-azuredevtips-micrum>, >> >> by a vs-code dev. He has a YouTube tips channel >> <https://www.youtube.com/c/code2020>. >> > > Tip 3, goto symbol, is also great stuff. It doesn't replace the need for > organization, but it's a big help. It would be great if leoInteg supported > a "goto node" function. No rush, though :-) > > I am starting to learn vs-code <https://code.visualstudio.com/docs> and > electron <https://www.electronjs.org/docs>. The docs are superb. > > Félix, would you be interested in help with syntax coloring? It might be a > good starter project for me. > > 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/32e19ed3-5f83-410f-ae27-d62481becd78o%40googlegroups.com.
