Leo 6.3.1 will be coming fairly soon

Leo 6.3.1 is necessary for two reasons: 1. There is a crasher in the leoflexx.py plugin. Somehow pylint did not detect that u.afterChangeNodeContents no longer uses the "dirtyVnodeList" kwarg. I am not amused. 2. More happily, I am working on a major simplification of Leo's undo code, per

Re: SB: What I'll be studying

I'd like to suggest looking into Svelte, a modern JavaScript framework that's compiled at build time, so it has great performance. I enjoyed this presentation: Rich Harris - Rethinking reactivity (Youtube) And the learning materials and REPL on

Re: Could someone help me install leovue on a server?

On Saturday, November 7, 2020 at 1:25:02 PM UTC+1 Edward K. Ream wrote: > After building leovue, per the instructions of #735 > , I uploaded > leovue/dist/static to my server, but the site is not working. > > Have you uploaded

ENB: Simplifying undo

The goal of #1413 is to simplify Leo's undo api so that it is easier to write macro-like scripts. The first thought was to continue the ongoing elimination of kwargs (keyword args) by eliminating kwargs from c.updateBodyPane,

Could someone help me install leovue on a server?

After building leovue, per the instructions of #735 , I uploaded leovue/dist/static to my server, but the site is not working. I suspect just a few tweaks should suffice, but I'm not sure what those tweaks are. Perhaps I should have uploaded

SB: What I'll be studying

It's becoming clearer what I'll be studying and exploring during the sabbatical. For the last 25+ years I've pretty much ignored web development. That surely was a mistake. There is a ton of interesting technology out there. My initial focus will be on node.js packages, and the frameworks and