On Sun, Jun 21, 2020 at 11:52 AM Félix <[email protected]> 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/CAMF8tS2CUcqqV%2Bgqz_apw72HJ81FXB-t1XNKZw%2BMqRV8YUhUBQ%40mail.gmail.com.
