> - I see that the command palette already supports some of Leo's > outline-oriented (essential) commands. It might be good to use a separate > Leo decorator to denote commands that leoInteg should support. But that's a > nit.
They do have a decorator: "Leo", opening the command palette and ctrl+shit+P and typing 'leo' will restrict to leo commands. (you wont see them all because of space restriction but typing letters that are part of a command - i.e. "lazy typing matching like sublime" ) But English is not my first language, and I feel I'm missing some meanings in your comments regarding this point. What do you mean by that exactly? - I also see that you support some Leo settings in the way cool settings > pane. In vscode, with the 'git-lens' extension installed, (i think it comes by default now even!.. not sure...) open the command palette and start typing "git welcome" to see what inspired me for that settings "webview" page! - I don't see syntax coloring in the Leo outlines. Wheuat?? what do you mean? syntax coloring works and it makes the whole 'leoInteg" landscape come together so nicely! I have to re-do all my gifs and movies because of that! Have you pulled 'dev' ? maybe I forgot to push ,,, I'll check again... maybe you meant that i had not finished language specific coloring (switching when encountering @language xxx until the next marker.) yes then you'Re right. but there is still parenthesis matching, etc.. and regular basic syntax coloring in leo bodies of @directives, code, comments, @, @c, etc..... but since I got a grasp of textmate syntax it does not worry me to finish this in a week or two... ... unless you meant literaly 'outline' syntax coloring? Is there color in the 'outline'? ... in Leo i dont see color in my outlines... hmm... - After F5, the new window contains an "Outline" area in the Explorer area. > It says "The active editor can not provide outline information". What is > the purpose of the "Outline" area? There is also a "Timeline" area. It > shows "No timeline information was provided". I wonder whether this might > be related to a plugin, say gitLens. aha! - those are regular vscode views that are usually in the explorer panel indeed. they are standard, The 'outline' will show you a regular 'outline' of class methods, properties of a file that would be open in an editor. ...any file... just select a source in the explorer, it opens and boom, half a second later, a generated outline appears. its a plain representation of the source file. (the opposite of building with leo, if you will... or maybe like a plain 'import' tree without any structure depth to represent anything.) I'm not explaining it very well, see this paragraph instead: https://code.visualstudio.com/docs/getstarted/userinterface#_outline-view Timeline is the timeline of, again, whatever file would be opened and focussed on. Félix On Monday, June 22, 2020 at 5:12:33 PM UTC-4, Edward K. Ream wrote: > > On Sun, Jun 21, 2020 at 11:52 AM Félix <[email protected] <javascript:>> > wrote: > > That's great news to wake up to! >> > > Yeah, I'm pumped as well. A few random thoughts: > > - I had forgotten about #1025 > <https://github.com/leo-editor/leo-editor/issues/1025>. You are quite > right to say that leoInteg should support all (and only) Leo's essential > features. > > - I see that the command palette already supports some of Leo's > outline-oriented (essential) commands. It might be good to use a separate > Leo decorator to denote commands that leoInteg should support. But that's a > nit. > > - I also see that you support some Leo settings in the way cool settings > pane. > > - I just now realized what my "user error" was concerning F5. I have to > remember to open the leoInteg folder if somehow it has been closed. > > - I don't see syntax coloring in the Leo outlines. > > - After F5, the new window contains an "Outline" area in the Explorer > area. It says "The active editor can not provide outline information". What > is the purpose of the "Outline" area? There is also a "Timeline" area. It > shows "No timeline information was provided". I wonder whether this might > be related to a plugin, say gitLens. > > It's somewhat important to specify the concept that leoInteg is not trying >> to hide or replace Leo by implementing it's functionality in js/ts... To >> the contrary: It's shamelessly openly exposed as a 'facade', and the real >> Leo is running behind. No wizard of 'Oz' here :) >> > > I agree. This design is essential. > > 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/6686e62f-c4c3-4e49-a600-5cd8c353274bo%40googlegroups.com.
