Hello Félix, I appreciate your hard work on this project!
My workflow in VSCode is normally as follows: - Store directories as projects using the Project Manager extension. Directories can contain a variety of file types (Python, Jupyter, markdown, Leo, ...) - Open a project and click on various files in the VSCode Explorer to open them in tabs and make edits. For Leo files, it would be nice if opening a Leo file from the Explorer would start all of the necessary 'machinery' (e.g., server) if it is not started already so that I can immediately see the outline and work on it. I suppose the idea is that, if someone has python and the leointeg extension installed, operating on leo outlines will take no more setup than editing a text file. If the procedure requires command line operations or creating special shortcuts, I am guessing that the uptake of the extension may be limited to 'experts'. Kind regards, Brad On Wednesday, July 8, 2020 at 3:14:42 PM UTC-6, Félix wrote: > > Hi Brad! > > Glad you like it! > > Knowing that other people understand and use what i'm doing is a great > motivator and a pleasant experience! So thank you for taking the time to > report your usage of leoInteg! > > 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? >> > > Well for some, (I think Ar-jan made it work seamlessly under > conda/anaconda, see > https://github.com/boltex/leointeg/issues/10#issuecomment-654665776 ) it > feels 'seamless' if you've configured the python command line option to > start the server and connect automatically... I guess I could start the > leoInteg extension all the time even if there's no .leo file in the current > workspace... (there's many little details that could be fined tuned to > offer a more pleasant experience) > > But I guess actually it depends what you mean exactly by 'seamless' and > 'open a leo file'. > > And with that, I'm inviting you to describe what the user experience would > be in your mind, the best or nicest way to more fully integrate the 'open a > leo file' and seamless concepts, in a detailed and precise way. > > People who take the time to describe very precisely how a feature could > (or should) be experienced and implemented sometimes make a project move > along faster than people who submit actual code! > > Thanks again and don't hesitate to address any issues at all :) > -- > Félix > > > > > On Wednesday, July 8, 2020 at 3:52:07 PM UTC-4, Brad wrote: >> >> 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 <[email protected]> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/bfd5264a-4b6f-4166-a065-e9517652e5e8o%40googlegroups.com.
