On Thu, Jun 4, 2020 at 3:54 PM Félix <[email protected]> wrote: > > This conversation is very valuable because I want to make the experience > of installing and using LeoInteg easy and straightforward for all long-time > (or not) users of Leo, irrespective of their familiarity with vscode. So > thanks for putting out your very own thoughts as you experience the process > of trying out this extension still in development! >
My pleasure. Because of my professional deformation for using vscode/sublime daily for > the last 7 years or so, I'm having a hard time presenting the installation > and usage methods to people unfamiliar with vscode in a clear and concise > way. > > That is to be expected I guess :) > Yes. There is even a term for it: "the curse of knowledge". Although most of this will be irrelevant once I deem the project advanced > enough to be compiled and distributed as an actual vscode extension > (installed and ran seamlessly via the extension/market panel) It's still > very much important because I also have to fine-tune what I show in the > leoInteg panels, and in the readme, etc. > I'm glad you think so. It will help us all understand what you are trying to do, and how. Which brings me to what I think is the subtlety that make the whole process > of 'testing a vscode extension still in development' a bit confusing: > you're not running nor debugging my extension : you're running the whole of > vscode's source itself (the second vscode window that opens when you press > F5) with leoInteg in it, as if it was installed as a real extension. > An important clarification. > > I hope that last paragraph made sense... English is a second language to > me, so my sentence structures may be flaky at times. It's referred in the > official doc as "compiling and running the extension in a new Extension > Development Host window" > https://code.visualstudio.com/api/get-started/your-first-extension > It was perfectly clear. To help in clarifying all of this, I'm currently working on > https://github.com/boltex/leointeg/issues/44 , so this is changing the > appearance of the interface and, hopefully, going to help a lot in the > startup, and automation of the server startup and the connection to it, so > I'll make video captures right after I'm done with this. Hopefully before > the week end. (I'm open to doing zoom sessions: as soon as I finish those > changes on the interface) > I'll look forward to it. > > But in the meantime, I'll address the numbered points you raised : > > *Point 1:* yes, I meant the folder itself as such via the right-click > context menu (once vscode is installed with defaults behavior on windows) > see this screenshot: > One thing grammarly keeps reminding me of are unclear antecedents like "this" and "it". *Point 2: *addressed above, when pressing F5, you're running/debugging the *whole > of vscode,* with the addition of leoInteg installed and running in it, as > an extension. It's the normal way to try an extension that's still in > development. > Ok. *Point 3: *(see pic below for nomenclature) leoInteg adds a (stand-alone) > view in the side bar, accessible via the 'lion' icon in the activity bar. > It's also 'reflected' (a "clone" in Leo's parlance if you will) by default > in the explorer view of the side bar. > Thanks for the picture. It does clarify the terminology. I don't see any lion icon anywhere, either in your picture or my running copy of vs-code. > *Point 4:* you're right, and that's why i intend on making a small video > by capturing myself installing and running the whole thing in a > straightforward and unambiguous way. > Thanks. I'll give some more updates and details later - thanks again for trying and > reporting ! > It's my pleasure to help with this project. 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/CAMF8tS0i5t2ReL99-%3DpVhvHYrUChfh8PdPdn%2BV5GwCF%2B%3DKv%2BJA%40mail.gmail.com.
