Hah! no problem at all Thomas, I totally appreciate the criticism so don't 
worry about the tone of your comments or anything like that,  😋 hehe!

I should have indeed mentioned that* I do skim very rapidly *over all those 
information packed examples, and that *pausing *and *rewinding *often is 
more than expected from the viewer, if he wishes to try it itself instead 
of just seeing a list of what's possible.  Especially if he's relatively 
new to vscode.

I had to balance between showing a quick list of what's possible under 5 
minutes to give an overview without boring the viewer, versus explaining 
slowly with explicit details of each menu item clicked for a viewer to try 
and reproduce the experiments himself without prior vscode experience...  

and so, please do go ahead if you wish and list more of the things that are 
hard to reproduce in the video for someone less familiar with vscode, as 
I'll add a note in the description area under the video on youtube to 
address those things.

*To address the specific point you tried to reproduce*: When I do a command 
from Leo's own commands using the minibuffer, I display the keys pressed on 
screen, "ALT+X". (such as when I do 'refresh settings' at *4:17 *) For any 
other commands I perform where the focus is NOT on a Leo panel, such as at 
*1:18 
*when I do the operation you mentioned: "markdown open preview" from the 
markdown document - *not from the body pane itself btw ,* I then just use 
the generic 'commands palette' of vscode. (Which is the very first 
keybinding vscode users learn since all commands are done through that 
command palette shortcut : CTRL+SHIFT+P ) 

Félix


On Sunday, March 31, 2024 at 6:08:57 PM UTC-4 [email protected] wrote:

> Felix, I appreciate all the work but I'm not able to work with the intro 
> video.  Everything happens too fast and I think you do some things that are 
> not visible.  For example, you somehow open a Preview pane that can render 
> Markdown.  I'd like to do that. I have to guess that you got to it by a 
> right mouse click, but when I right click in the body pane I don't get a 
> menu item to open a preview.  The video doesn't give me any guidance about 
> how to set that up.
>
> It's similar with the Git integration.  There are just too many things to 
> take in during the time that a drag takes place, and then something else 
> happens that there also isn't time to take in.
>
> If things were slowed down and there were more titles or explanatory text 
> the video would be much more helpful.  I know that making these videos is 
> time-consuming and has a large learning curve - that's why I haven't tried 
> making my own! Please don't take these comments as criticizing your work - 
> I'm just trying to be helpful. 
>
> On Sunday, March 31, 2024 at 4:30:18 PM UTC-4 Félix wrote:
>
>> The sample Leo scripts shown in the video are collected in this github 
>> repository: https://github.com/boltex/scripting-samples-leojs
>>
>> The sample "LeoJS-Plugin" extension shown in the video also has its own 
>> github repository at: https://github.com/boltex/extension-sample-leojs
>>
>> On Sunday, March 31, 2024 at 4:28:00 PM UTC-4 Félix wrote:
>>
>>> *LeoJS Status Report*
>>>
>>> After stabilizing the beta version, now reaching its twelfth revision at 
>>> 0.2.12, and getting rid of its most obvious bugs and defects, I thought it 
>>> would be a good moment to address the questions posed on this forum about 
>>> the possible features and capabilities of LeoJS by producing a video 
>>> demonstration.
>>>
>>> This took a bit longer than I would have thought, months instead of 
>>> weeks, but nevertheless, here it is!
>>>
>>> https://www.youtube.com/watch?v=M_mKXSbVGdE
>>>
>>> *This five-minute video quickly goes over each of the following:*
>>>
>>>    - Using LeoJS on the web
>>>    - Commits & pull requests from VSCode's UI
>>>    - Running Leo scripts in LeoJS
>>>    - Interacting with the UI from scripts (Sample scripts)
>>>    - Creating a plugin/extension that uses LeoJS (Sample extension)
>>>    - Invoking commands, using the minibuffer and @buttons
>>>    - Using a @settings node
>>>    - UNL link support
>>>    - Previewing live render of SVG (or markdown, etc.) external files
>>>
>>> Hoping this will answer most questions the experienced leonistas had 
>>> about LeoJS being able to reproduce the original Leo's functionalities from 
>>> within VSCode.
>>>
>>> *Last but not least: I've also remade the classic 'Introduction to Leo' 
>>> video with LeoJS! *
>>>
>>> https://www.youtube.com/watch?v=j0eo7SlnnSY
>>>
>>> Hope you like those two videos!
>>>
>>> I'll now focus on the very last few remaining LeoJS issues and features 
>>> needed for a proper 1.0 version release of LeoJS. (Hopefully this spring!) 
>>>
>>> Félix
>>>
>>

-- 
You received this message because you are subscribed to the Google Groups 
"leo-editor" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/leo-editor/a8f4c606-47e9-4ae4-98fa-cf803d0c4e63n%40googlegroups.com.

Reply via email to