*>I only know how to install such packaged extensions from the
marketplace.*
It's way simpler than you think: When developing and/or building an
extension (to try out new features that you've added to the LeoJS codebase
itself), you dont build a VSIX, nor go through the packaging process of
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
Thanks for this great question Thomas!
(I'll list a few ways, some of which you already know, but I'll list them
all for other people to read about in case they didn't know)
First of all, like for the original Leo, a good way to customize the
behavior is to write Leo Scripts in the body text
On Tuesday, April 30, 2024 at 10:52:57 AM UTC-5 Thomas wrote:
Using Leo, we can edit LeoPyRef, save the edits, restart Leo, and test our
changes. With LeoJS, how can we do the equivalent: editing the code of
LeoJS and testing it?
Interesting question. I am using a hybrid approach:
Develop
Using Leo, we can edit LeoPyRef, save the edits, restart Leo, and test our
changes. With LeoJS, how can we do the equivalent: editing the code of
LeoJS and testing it?
--
You received this message because you are subscribed to the Google Groups
"leo-editor" group.
To unsubscribe from this
