Hello Félix,
As a regular user of Leo and VSCode, this is awesome!
Following Matt Wilkie's great step-by-step account of how to get things
going under Anaconda Python, I edited some leo outlines and was very
impressed by the potential of this project.
Not knowing much about VSCode extensions, do you imagine that further down
the road a user of VSCode will just be able to open a .leo file and have
the various components start up so that manipulating Leo outlines will be
seamless?
Thanks again.
Kind regards,
Brad
On Wednesday, July 8, 2020 at 12:54:46 PM UTC-6, Félix wrote:
>
> Here's a quick list of most of the new features now on the "dev" branch.
> Going to make little touch-ups and cleanup before merging to master.
>
> *New option setting : Use Leo Tree Browsing. (find better name!)*
>
> *New option setting : Show/hide 'edit headline' hover icon. (allowing to
> remove all icons lets the user go directly from the tree to the body pane
> with a single 'tab' hit on the keyboard.*
>
> *New Visual Helper: when changing option-settings, a new popup will appear
> indicating the options have been changed but are still pending 'saving' in
> the user's settings file. 1.5 Seconds later the 'Auto-saved' message should
> appear as usual. (Some users were closing / changing tabs too fast after
> changing settings and not realizing they had not waited long enough for the
> 'auto-save' to kick in.)*
>
> *After changing the option-settings, if any changes involved the
> hover-icons, the tree will refresh (debounced / timeout of 200ms) to
> reflect the changes.*
>
> *The "currently selected node" attributes are now watched by leoInteg in
> order to strictly show and allow relevant commands and icons only. (in
> command palette and on the top title bar of outline views)*
>
> *Outline tree nodes also have more properties to allow stricter set of
> commands to be offered in via the right-click context menu
> ("goto-next-clone" only shown on cloned nodes, "refresh from file" only
> shown on '@clean/@files etc...)*
>
> *Hoist and dehoist commands have been implemented for the currently
> selected node *and* also for any visible node in the outline tree via
> right-click context menu. De-hoist command is accessible as an icon in the
> tree top title bar, as a regular command, and as a context-menu entry on
> the single topmost ode of a hoisted tree.*
>
> *Keyboard editing improvements: Commands try to bring focus back into the
> right pane after execution to improve the keyboard editing experience and
> fluency.*
>
> *Keyboard editing improvements: CTRL-T and Tab shortcuts that match Leo's
> behavior to switch active panel*
>
> *"Direct" keyboard navigation in the outline tree: Move the selected tree
> node and body pane with single arrow keys, as in Leo. Replaces vscode's
> usual tree navigation system. Optionally toggled on/off as an option
> setting.*
>
> *New keyboard shortcuts: *
> *gotoFirstVisible : alt+home,*
> *gotoLastSibling : alt+end,*
> *gotoNextClone : alt+n,*
> *sortSiblings : alt+a,*
> *showOutline : alt+t,*
> *Toggle outline/body focus : ctrl+t,*
> *Focus Body : alt+d,*
> *Focus body (from tree) : tab",*
> *Alt+Arrow keys: Direct Tree Navigation.*
> *Arrow Keys: (with 'Leo-tree-browse' option) Direct Tree navigation*
>
> As usual, please report anything that comes to mind while using this so I
> can make adjustments :)
>
> Thanks for trying this stuff out you guys!
> --
> Félix
>
>
>
> On Wednesday, July 8, 2020 at 11:47:45 AM UTC-4, Edward K. Ream wrote:
>>
>>
>>
>> On Wed, Jul 8, 2020 at 9:29 AM Félix <felix...@gmail.com> wrote:
>>
>>> Note to self: Test under windows just before pushing after adding
>>> features!
>>>
>>> Turns out vscode commands are case-insensitive under linux! Which leads
>>> to compile errors when trying to run under windows with erroneous case
>>> inconsistencies!
>>>
>>> Thanks for trying, and sorry for this rookie mistake! All fixed under
>>> the dev branch now!
>>>
>>
>> Everything looks good now.
>>
>> Edward
>>
>
--
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 leo-editor+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/leo-editor/5665598d-5441-4162-97ac-1f7bff385d7ao%40googlegroups.com.
