>I would rather you make leoserver.py work exactly the way you want, rather than the other way around. For example, you mentioned switching the "escape" convention so that "!" denotes a server method rather than a Leo method.
Yes, I do change the implementation details to make it work properly, hehe ;) but I keep the hierarchy and general code layout that you had put in place in leoserver.py. (with the log/verbose flags, error checking, etc. that was missing in my original implementation) > In short, delaying the official launch of leoInteg by a week or two might be a good idea. What do you think? What are your plans? Yes indeed, I don't want to rush anything, and I'm comfortable in releasing after june 21st / july if needs be to cleanup most apparent bugs and glitches. For now I'll concentrate in finishing the server rewrite and I'll make a more official post / list of things to do before release. Oh - while you're checking out the latest release ... the one issue that warrants the most pressing fix (for the sake of completeness) is https://github.com/boltex/leointeg/issues/140 perhaps that by being aware of it, you'll give me a suggestion to fix it easily, as you often do! :) -- Félix On Saturday, June 5, 2021 at 7:53:39 AM UTC-4 Edward K. Ream wrote: > On Thu, Jun 3, 2021 at 11:30 PM Félix <[email protected]> wrote: > >> >> Hey you guys, >> >> I just pushed 0.1.14 with a bunch of new features (Find-panel, >> import-file(s), and many more) along with bug fixes on the master branch! > > > Congratulations. I'm just back from a short vacation. Playing with the > master branch will be my top priority. > > *One last step:* I'm now going to finish re-writing/de-bugging the >> leoserver.py script to match Edward's architecture, structure and naming >> conventions. (And also to be completely client-agnostic) To then use it as >> the sever for leointeg directly from Leo's installation folder, instead of >> the original 'leobridgeserver.py' from leointeg. (which won't be needed >> anymore) >> > > I would rather you make leoserver.py work exactly the way you want, rather > than the other way around. For example, you mentioned switching the > "escape" convention so that "!" denotes a server method rather than a Leo > method. > > Are you planning to issue a PR against Leo? That's what I expect :-) > > *This is the last step before releasing the 1.0 version of leointeg, Which >> will be released as a 'real' extention. (which would then obviously be much >> more easy to install and use via the standard 'Extension panel' of vscode.)* >> > > Just before I left on vacation I created Leo #1964 > <https://github.com/leo-editor/leo-editor/issues/1964>: Prepare for > leoInteg. This is just a placeholder for some of my thoughts. > > To summarize: we want the launch of leoInteg to go as smoothly as > possible. We want to help present Leonistas to become comfortable with > vs-code, and leoInteg itself, so that soon after the launch we can all > up-vote leoInteg. > > In short, delaying the official launch of leoInteg by a week or two might > be a good idea. What do you think? What are your plans? > > 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/33a6ec9d-ac16-44b6-8104-f914d3198f8an%40googlegroups.com.
