To put it succinctly: As far as programming is concerned, LeoJS is a general-purpose IDE within another general-purpose IDE (VSCode).
On Wednesday, September 18, 2024 at 11:50:33 AM UTC+2 rengel wrote: > I admire the great intellectual effort and accomplishment behind LeoJS! > > I have installed LeoJS in VSCode (VSCodium). Now I'm trying to wrap my > mind around the relationship between LeoJS and VSCode and to figure out how > I can use LeoJS to improve my workflow. I understand, that I now can work > with my Leo outlines from within VSCode. But frankly, why should I want to > this? Compared to the clean interface of the LeoPy desktop all this unsused > VSCode stuff around LeoJS is just visual clutter. > > But what about programming? > > After years of using Python, today I program mainly using Elixir/Erlang > for desktop development and Phoenix LiveView for web development. I use > VSCode as my IDE. > VSCode has excellent plugins/extensions for these languages. The languages > have tools for creating complete working project skeletons(i.e. *mix* of > Elixir). > > VSCode provides essential tools for writing, debugging, and managing code > across various programming languages and frameworks. Inbuilt key features > include: > > - *Code Editing* | Syntax highlighting, intelligent code completion, > and linting. > - *Integrated Terminal* | Allows running command-line operations > directly from the editor. > - *Version Control Integration* | Built-in Git support. > - *Extension Support* | Customizable through an ecosystem of > extensions for languages, frameworks, and tools. > - *Cross-Platform* | Available on Windows, macOS, and Linux. > > LeoJS offers roughly the same functions, albeit in a different language, > so users have to master two different sets of commands for the same > functionality. In order to use LeoJs's superior editing functions (finer > granularity of editing single files, clones, and 'code weaving'), one has > to import the project structure created by the language tools into a Leo > outline - basically using LeoJS as a mor capable duplicate of the VSCode > Explorer. That would be another duplication of effort. > > So for me the question is: "How can I leverage LeoJS in VSCode effectively > to work with the project structures and program skeletons created by > specialized language-specific tools?" > > -- 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/63105d46-85c7-48fa-8494-2851f8822091n%40googlegroups.com.
