Hello, About a month ago I did a bunch of tests with vscode's extension capabilities along with tests with leoBridge's control of Leo. Mostly throwing spaghetti at the wall and seeing what sticks. I got excited, you guys kind of liked it I guess, but it all added up to a whole bunch of spaghetti code mess as you may have noticed if you browsed my sources. Mostly so in the 'communication' between vscode and the python script (Leo) part.
I sincerely apologize for this and present you now instead with a cleaned up version, where code-duplication was eliminated and all processes are now streamlined and simplified! I think this is a great moment for testing that "basic browsing" works fine before adding outline editing, and map mostly all or the rest of Leo's functionality to be used seamlessly from vscode... https://github.com/boltex/leointeg Please try it out (browsing along with headline and body editing for now) and ask about anything I may have overlooked in this short invitation to beta-test my stuff for free ;) here is the last changelog entry: - Major 'Browsing' update before adding outline editing and file saving & derivation - Refactored and simplified communication between vscode and leoBridge - Stabilized browsing with multiple simultaneous (and different) body panes - Added Leo Outline into explorer view (in addition to the dedicated Leo sidebar view) - Supports new command to open a node on the side from the context menu - Multiple configuration options: Open Settings with CTRL+',' type 'leo', or look for 'leo integration' in extensions Many thanks!! -- Félix -- 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 leo-editor+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/29949267-fa3d-471e-b591-e8f5d5f61796%40googlegroups.com.
