Energy, prototypes, leoPrototype.py and leo/proto

#684: Create a browser gui for Leo is one of the largest projects in Leo's history. It might take 6 months or more to complete. The only way to confront such a project is to focus on prototypes that take only one or two days. That puts us

Re: Energy, prototypes, leoPrototype.py and leo/proto

On Saturday, February 17, 2018 at 6:32:01 AM UTC-6, Edward K. Ream wrote: >> A new leo/proto folder will contain prototype code, organized by developer. Rev d13c608 of the new proto branch creates this directory structure: - leo/proto - Joe - Terry - leoserver - Vitalije Using first

c2803b5: the 'proto-leo-server' command

Here it is: @g.command('leoserver') @g.command('proto-leo-server') def proto_leoserver(event): """ Terry's fully functional Leo web interface :-) First announced here, in a comment to #684: https://github.com/leo-editor/leo-editor/issues/684#issuecomment-363992724 The

d4fbf6f: g.runExternalCommands

This new method will be a common helper for the proto-* commands. It will also be more generally useful. Here is the first draft: def runExternalCommands(c, commands, base_dir = None, path_setting = None, warning = None, ): ''' A helper for prototype commands or any other

Re: a826cf2: The proto-leo-el-vue command

On Saturday, February 17, 2018 at 9:14:50 AM UTC-6, Edward K. Ream wrote: > Doing 'npm install' works, but slows things down... > We could always define an command that installs, then runs, but building from the console seems good enough for now. Hmm. I think it is a mistake to include the

Re: Energy, prototypes, leoPrototype.py and leo/proto

On Saturday, February 17, 2018 at 7:10:08 AM UTC-6, vitalije wrote: Just keep in mind that these subprojects when built, install lot of > subfolders and files which need to be ignored by git. Default gitignore is > designed for the situation when project folder is actually root of project. >

Re: Energy, prototypes, leoPrototype.py and leo/proto

On Sat, Feb 17, 2018 at 7:14 AM, Edward K. Ream wrote: Rev 0138853 of the proto branch adds Vitalije's two projects. > ​Important: the readme.md files in these two projects contains detailed build instructions. We devs are debugging the process of trying out other people's

Re: a826cf2: The proto-leo-el-vue command

On Saturday, February 17, 2018 at 9:24:25 AM UTC-6, Edward K. Ream wrote: Hmm. I think it is a mistake to include the dist folder in Leo's git repo. > Actually, this folder contains only main.js, so it seems safe enough to distribute it. Let me know if you disagree. Edward -- You received

Re: Energy, prototypes, leoPrototype.py and leo/proto

On Sat, Feb 17, 2018 at 1:55 AM, Edward K. Ream wrote: A new leo/proto folder will contain prototype code, organized by developer. > This folder will allow devs to push work for others to see. > All prototypes will live in a long-lived *proto* branch, or sub-branches if

Re: Energy, prototypes, leoPrototype.py and leo/proto

On Saturday, February 17, 2018 at 6:55:40 AM UTC-6, Edward K. Ream wrote: > I'll add subfolders under proto/Joe and proto/Vitalije soon. Rev 0138853 of the proto branch adds Vitalije's two projects. But now we come to two problems: 1. It's not wise to add Joe's LeoVue project to the proto

effective collaborate with .leo for doc.?[via]Advices for Leo documentation in Chinese translated version?

2 years ago: Re: How to collaborate using Leo https://groups.google.com/d/msg/leo-editor/Mr1cAfi8BLs/Q2PlDxsrBwAJ discuss about Leonard(Leo user) and Nancy(not Leo user) how to work together, the result is : @clean be upgraded, and support perfect auto merge from Nancy fixed resource files. but

a826cf2: The proto-leo-el-vue command

This has been laughably easy. Here is the new code, in leoPrototype.py: @g.command('leo-el-vue') @g.command('proto-leo-el-vue') def leo_el_vue(event): """ Vitalije's electron/vue project:: Leo in CoffeeScript and Vue. Original sources and documentation at:

Re: Energy, prototypes, leoPrototype.py and leo/proto

On Sat, Feb 17, 2018 at 7:18 AM, Edward K. Ream wrote: > On Saturday, February 17, 2018 at 7:10:08 AM UTC-6, vitalije wrote: > > Just keep in mind that these subprojects when built, install lot of >> subfolders and files which need to be ignored by git. > > ​Rev 1e56cc8 creates a .gitignore file

Re: a826cf2: The proto-leo-el-vue command

in dist folder would end up binary version of the electron desktop application (50+ Mb for each operating system). I guess safest would be to git ignore dist folder too. On Saturday, February 17, 2018 at 4:27:34 PM UTC+1, Edward K. Ream wrote: > > On Saturday, February 17, 2018 at 9:24:25 AM

Re: Energy, prototypes, leoPrototype.py and leo/proto

Just keep in mind that these subprojects when built, install lot of subfolders and files which need to be ignored by git. Default gitignore is designed for the situation when project folder is actually root of project. I am not sure that will be a problem but just be cautious not to accidentally

Re: Energy, prototypes, leoPrototype.py and leo/proto

On Saturday, February 17, 2018 at 7:14:22 AM UTC-6, Edward K. Ream wrote: > It's not wise to add Joe's LeoVue project to the proto folder. It takes over 86 MB of disk space. The proto-leo-el-vue command shows the way forward. An @string setting will point to the base directory of Joe's work.

Re: a826cf2: The proto-leo-el-vue command

On Sat, Feb 17, 2018 at 11:27 AM, vitalije wrote: > in dist folder would end up binary version of the electron desktop > application (50+ Mb for each operating system). I guess safest would be to > git ignore dist folder too. > ​Thanks. 1bf2258 changes .gitignore in both

Re: a826cf2: The proto-leo-el-vue command

On Sat, Feb 17, 2018 at 1:38 PM, vitalije wrote: > - Doing 'npm install' works, but slows things down. >> >> >> I suggest to use yarn instead of npm. You need to execute once > npm install -g yarn > > to install yarn globally and then instead of > npm install > # use > yarn

Running shell commands. New: g.execute_shell_commands_with_options

This will be pre-writing for an expanded and improved version of this part of Leo's scripting miscellany . There are at least three ways to execute shell

Re: a826cf2: The proto-leo-el-vue command

> > - Doing 'npm install' works, but slows things down. > > > I suggest to use yarn instead of npm. You need to execute once npm install -g yarn to install yarn globally and then instead of npm install # use yarn # and instead of running npm run use just yarn # for example yarn dev # or

Scripting leo: Programmatic way to reference the vnode containing the script that is being executed?

Hi there, I'm trying to get deeper into scripting leo and have hit upon a question I can't find an answer to. Firstly, I can't seem to find a way to programmatically reference the vnode containing the script that is being executed (or the root vnode thereof in the case where the script is

Re: Energy, prototypes, leoPrototype.py and leo/proto

Made some changes to leoserver explained in the commit message: https://github.com/leo-editor/leo-editor/commit/736a6a5 eliminate jQuery.ajax() calls and some other changes, but that's the main difference. Using fetch() instead will break the client for legacy broswers like IE, but let's

Re: Scripting leo: Programmatic way to reference the vnode containing the script that is being executed?

On Saturday, February 17, 2018 at 5:57:19 PM UTC-6, John Clark wrote: Firstly, I can't seem to find a way to programmatically reference the vnode > containing the script that is being executed (or the root vnode thereof in > the case where the script is composed using numerous child nodes). >