On Friday, May 3, 2024 at 9:45:46 PM UTC-4 Félix wrote: Thanks for this great question Thomas!
Lastly, *for modifying LeoJS itself *(instead of running scripts from custom @commands or @buttons, or building an extension and accessing the LeoJS global 'g' object) you would just need to clone the LeoJS repository. To then build and run it would be the same process as any of the VSCode sample extensions, such as this hello-world extension <https://github.com/microsoft/vscode-extension-samples/tree/main/helloworld-sample>. (That is to say, running the 'npm install' in the repository folder command to get all dependencies, and pressing F5 to start the 'run and debug' command in VSCode.) This is where I lose track of what to do. So far as I know up until now, an extension needs to packaged in a particular way with certain metadata. I only know how to install such packaged extensions from the marketplace. I suppose I need to know how to run an extension when one has not gone through all that packaging process and is not using the marketplace. Of course, with Leo-Python you don't have to do anything special: the code is just there and you run it. (BTW I have already cloned the repo). Another aspect of running one's modified LeoJS code is how to *not* run the existing LeoJS (the marketplace extension) without de-installing it. -- 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/ac9e65e0-0047-42b0-ad7b-17d8a13470fan%40googlegroups.com.
