Leo Integration Status Update

[Félix]

Hello all of you Leonistas!

Here's what I've been up to lately, in this continuing pandemic quarantine reality:

I've celebrated the one-year anniversary of LeoInteg's development by taking a little more than a month off of programming... And for fun, made a remake of the 'intro to Leo" video. 

So check it out: https://youtu.be/SYwlfdEukD4 (and the other how-to install video if you haven't tried it yet: https://youtu.be/rutt11xL54I)

It was a great opportunity to learn to use Blender and openShot, which I've wanted to learn from a long time now...

I guess i'll include it in LeoInteg's documentation until I update it somewhat later to a more serious version ;)

But most importantly, It was a period where I wanted to wait and see if the changes in the vscode API by vscode's team, which rendered leoInteg less stable, were permanent. 

Seem that they are permanent indeed, and that the body-pane instantiation and logic will have to be changed substantially. 

So that's what I'll focus on - as I get back to work on LeoInteg and polish the somewhat ad-hoc integration of the last features that were last included (multiple documents support and switching documents, among others) in the days to come.

Looking forward to a useable '1.0' version in a couple of months :) 

Cheers! and please let me know what you think about the video!

--

Félix

[Edward K. Ream]

On Mon, Sep 21, 2020 at 12:45 AM Félix <felix...@gmail.com> wrote:

I've celebrated the one-year anniversary of LeoInteg's development by taking a little more than a month off of programming... And for fun, made a remake of the 'intro to Leo" video. 

So check it out: https://youtu.be/SYwlfdEukD4

Great job! Some comments:

1. The newer terminology is "external file" rather than "derived file". The old term appears at least once in the tutorial.

2. Replace "ot" with "of" in one of the nodes.

3. Rather than illustrate the mechanics of clones, I would suggest a few words about why clones are important, namely that clones allow you to create "views" of data that filter out all extraneous details. The clone-find commands are the killer app for clones.

BTW, the voice doesn't sound like you. Is it computer generated?

Edward

[Félix]

Thanks for the comments! Exactly the kind of details I need to make a better version down the road

I intend to accumulate a hearty list of comments and suggestions in order to make a more polished version... (without the tongue-in-cheek teaser at the end), at about around spring time, where I expect to have achieved a proper level of stability with LeoInteg 

(Accompanying videos are always nice to have when trying to launch a '1.0' version of a software product!)

I've also noticed the "ot"/"of" typo last minute as I was uploading, omg...

Your point # 3 is reminding me I should try and use those 'clone' related commands and wrap my mind around them!

About the voicing, yep its not me - it's just google voice samples :)

I'm now back on working on LeoInteg, but for the first few days I'll try to solve a couple smaller and easy issues before really solving the main issue : redoing the body pane logic following vscode's API change side-effects in order to make a 0.1.13 release on the master branch.

--

Félix

[Arjan]

Very nice video. Also, looking forward to a stable LeoInteg!

Now, if there's a light theme called "Winter is coming", there should also be a dark theme called "The night is dark and full of terrors"? ;)