Re: Issue #3710: EKR's last lecture

I have finished #3710 : EKR's last lecture. personal goals > What's your goals? Does that changed? Just a remind. Whenever I discover something I think I "should" do, I ask myself two questions: - Do I *need* to do it? - Do I

Re: FYI: Two new LeoU/devinfo items

Issue #3729 tells how to read Leo's code. I wondered, is it possible and necessary to make a simple learning path based on low difficulty, medium difficulty, and high difficulty? For example, there are three examples of plugin

Re: LeoJS: What is the equivalent of LeoPyRef.leo?

Thanks, Felix. Now if we wanted to test out a code modification or addition, how would we incorporate that into an extension that VSC could load or install? On Sunday, December 24, 2023 at 12:15:08 PM UTC-5 Félix wrote: > Hi Thomas, > > Great question -- Thanks for asking! > > Since LeoJS is

Re: LeoJS: What is the equivalent of LeoPyRef.leo?

Hi Thomas, Great question -- Thanks for asking! Since LeoJS is a VSCode (or vscodium) extension, its source code is compiled/minified somehow, and many other source files are omitted from the final 'distribution' package. Therefore, the way to open and view LeoJS source files (or browse it's

FYI: Two new LeoU/devinfo items

Issue #3729 tells how to read Leo's code. Issue #3730 tells how to becoming a Leo dev. All comments about these issues are welcome *here*. The issues themselves are locked. Edward

Issue #3710: EKR's last lecture

I have finished #3710 : EKR's last lecture. This issue is locked. I welcome all comments *here*. Edward -- You received this message because you are subscribed to the Google Groups "leo-editor" group. To unsubscribe from this group and

PR #3721 (improved caching) now in devel

PR #3721 simplifies Leo's caching code. Leo should work exactly as before. Leo now *only* writes data to the *.leo/db/g_app_db* folder. Leo no longer creates *other *sub-folders of the .leo/db folder. You may clear these other folders if

Re: question about code organization issues for personal common libraries and multiple plug-ins

On Sunday, December 24, 2023 at 5:50:42 AM UTC-5 Edward K. Ream wrote: - Define a shared @command f1 node in your myLeoSetting.leo for your function f1. - Execute the function with: c.doCommandByName("f1"). That's how most of my custom things work. -- You received this message because you

Re: question about code organization issues for personal common libraries and multiple plug-ins

Here is the easy (and flexible!) way: - Define a shared @command f1 node in your myLeoSetting.leo for your function f1. - Execute the function with: c.doCommandByName("f1"). I'm going to do a bit of a balance between plugins or the way which you said. For now, Thomas's approach to 'place a

Re: question about code organization issues for personal common libraries and multiple plug-ins

On Sat, Dec 23, 2023 at 8:23 PM HaveF HaveF wrote: > I frequently employ the same specific functions such as fun1, fun2, and so on. Here is the easy (and flexible!) way: - Define a shared @command f1 node in your myLeoSetting.leo for your function f1. - Execute the function with: