Just a copy / paste in case someone joins this thread: 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 On Saturday, August 10, 2019 at 3:49:34 PM UTC-4, Robert Cholette wrote: > > First I'd like to apologize for just asking this on github, I didnt > realise here was perhaps a better place to ask this kind of thing... > > Hi! Long time leo user here. I use it mainly for the 'core' features: > outline organisation of my code : @clean nodes, structure with @others. And > I alt-tab leo alongside with another editor/IDE for > running/debugging/compiling/linting/beautifying/etc... > > I dont care so much about vim/emacs integration nor dont even understand > what those buffers/minibuffers are and all around feel like that qt-gui > framework didnt age very well. (no offence meant here, as I would be > devastated to think I offended edream, he's like my programming 'idol') > I also do not use @buttons and internal scripting in leo altough i can see > its use for some people. > > I mainly use Leo for its 'file-generation'/'file-reading' (mainly @clean) > feature via the outline structure that it provides. Organising a program > with an outline, clones and @others is the best! Which also, if I may say > so, is Leo's 'killer feature'. > > So i'd like to try and integrate, or 'roll my own' leo in my other > favorite editor so that I have the subset of leo's features that I just > defined as its 'killer features' available without having Leo 'opened'. > Is leoBridge the way to go? ...or is there a way to start leo with no GUI > and have it listen for commands on a specific port for input/output of > commands and answers? > > Many thanks in advance!! > -- 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/cc038a11-e57a-4913-a994-ea36b9225fc8%40googlegroups.com.
