I've rewritten everything during the weekend, I've changed the whole system into a client / server tcp/ip relationship. not polished yet, so i've pushed it on the dev branch before I cleanup and get it merged into master.
(gotta cleanup and add buttons and text on the outline bar among other things to make the start process easy and bulletproof) You may try this new method of the dev branch (before i make it user firendly) if you'Re so inclined: you may start the server by running leobridgeserver.py which is at the root of the project folder. (needs websocket dependency: pip install websockets) then start running another instance of vscode with the leointeg expansion running with F5. In a day or two i'll finish adding buttons to ask for adress and port to connect and facilitate the process in a much needed way, (and then push to master) but for now, if you want to try it: leointeg will try to connect to localhost on port 32125 : the one set in leointegserver.py defaults constants. just make sure to start the server beforehand. About F5 : This does not start running and debugging the expansion, rather, it starts to run another instance of vscode with the leointeg expansion activated in it. So doing another F5 in that other vscode window is not recomended, as I dont know upon what workspace it will open into! (may be the last one you worked with in vscode or some other depending on your vscode settings and past usage) The workspace it opened into will also trigger all sorts of suggestions about installing tools to code and debug depending on what filetypes are present in this workspace. That may be where that 'extensions select environmen thing' came from, really not sure about that. So doing F5 should not be performed other than once to start a debug/run session of a vscode instance with the leointeg expansion enabled in it. Of course, when the expansion is more fleshed out, i'll wrap it up in a real expansion bundle, which eliminates all installation procedures into a seamless 'one click'. -- Too late for me now, gotta go to sleep its past midnight!! - i'll finish making the whole thing into a more professional looking procedure, with a two step process of 'connecting to server' and then 'opening a leo file' during the week. ...but if anyone is brave enough, they can try the dev branch. -- Félix p.s. Leo rocks! On Monday, October 14, 2019 at 3:23:31 AM UTC-4, Edward K. Ream wrote: > > On Sat, Oct 12, 2019 at 2:02 PM Félix <[email protected] <javascript:>> > wrote: > > > @Edward (on windows) those modified 'package' files are getting small > modifications when doing 'npm install' because of versions of dependencies > getting updates.( Something I overlooked in my explanations. ) > Solution : Revert those files to their original states before doing "git > pull" so that git lets you apply updates you pulled... > > Did that. npm install said everything was up to date. > > Please me what I should do within VS Code. I see a LEO and OUTLINE areas, > but they don't seem to do much. > > I'm confused about F5. Doing F5 in the bottom area puts the cursor in a > top area that says Extensions: Select environment. Selecting node.js gives > ${file} can not be resolved. > > 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/5b8dec97-7151-4230-bc95-83cb1ab52451%40googlegroups.com.
