Addendum: I just thought Id specify to readers unaware of VSCode's integration into github that yes, It's not a typo: *Press the dot "." on your keyboard* when viewing a particular branch on repo that you own. Tada! :)
Félix On Wednesday, December 20, 2023 at 11:13:38 PM UTC-5 Félix wrote: > Thank you Edward, Viktor, HaveF, and Thomas for trying out and reporting > your experience! This will help me polish LeoJS and get rid of hard-to-spot > bugs! > > Viktor, > About rst3: I've implemented all of the rst related code in LeoJS, (see > leoRst.ts > in the repository > <https://github.com/boltex/leojs/blob/master/src/core/leoRst.ts>) but > there's a part that I could not transliterate. Here is the magic lines > that I cannot reproduce easily in typescript... :) > > # Third-part imports... > try: > import docutils > import docutils.core > from docutils import parsers > from docutils.parsers import rst > > haha! ;) There's no library in javascript that exist (that I know of) > I was lucky in some other instances (pickle, zip, md5, sqlite, etc.) in > finding libraries for javascript. But none so far for docutils/rst document > reading/writing so far. I'd really like to offer rst3 support in LeoJS just > like in Leo, so I'll keep an eye open, or, I'll implement it all myself > eventually! Please don't hesitate to suggest other ways for me to support > this if you can think of any, your ideas are greatly appreciated! (perhaps > Leo only uses a small subset of the rst python library and that > implementing it in javascript is not that harsh of a task ...I'd have to > look more into it. ) > > I'll open an issue right away for this: #80 > <https://github.com/boltex/leojs/issues/80> where we can accumulate > knowledge and plan more specifically how to go about to accomplish this > (important) part of Leo. > > Thanks again Viktor for your report! > > -- > > HaveF, > Thank you also very much for trying out LeoJS and reporting your > findings! Much appreciated!! > About your questions: > > 1- LeoJS *is *"Leo Editor for Visual Studio Code". Not 'based on'. > And LeoInteg integrates the real Leo by running an instance of > BridgeController in leoServer.py, and talking to it via simple websocket. > > But you are right in that LeoInteg is 'mostly complete' and is now > somewhat in a 'maintenance phase'. (Although *future features of LeoJS > will be added to LeoInteg as soon as they are done*. e.g. multiple *different > *opened body panes opened at once, UNL @URL click handling, etc.) > > 2- If you're talking about '@buttons' : LeoJS, like LeoInteg, has full > support of *@command* via the minibuffer (Alt+X), and * @button* via its > button panel. The button sub-menus are even implemented! see screenshot: > [image: screen.png] > Otherwise, LeoJS also has regular buttons for most common Leo commands > displayed if your mouse hovers the outline-pane: > [image: screen2.png] > Along with the body-pane: > [image: screen2.png] > Hover your mouse over them to see a description ! :) > > Thanks again HaveF for your questions and suggestions!! :D (please clarify > if I didn't address the particular point you were trying to make) > > -- > > Lastly, thanks again to Thomas. > > I hope the latest patches and updates that I did in the last few days now > allow the tests you had tried to do with LeoJS to actually work now! :) > > (And the tutorial I promised about how to use it live on the web in a > browser via github.com is coming soon! *hint: do not go to vscode.dev > <http://vscode.dev>, instead go to github.com <http://github.com>, login in > the usual way, navigate on a repo that you own, switch to a branch that you > own and have write access, and press the dot "." on your keyboard*. ) > > Félix > > > On Wednesday, December 20, 2023 at 8:21:07 PM UTC-5 [email protected] > wrote: > >> - Like its predecessor, LeoInteg, LeoJS employs VSCode's robust GUI to >> host a variety of panels and controls, offering a smooth and familiar user >> experience. >> >> Hi, Félix, >> >> Congratulations! >> >> I have two questions: >> >> 1. "Leo Editor for Visual Studio Code" is based on LeoJS, while "Leo >> Editor Integration with Visual Studio Code" is based on Leo. Currently, >> development will primarily focus on the former, with the latter >> transitioning to a maintenance phase—is that correct? >> >> >> 2. Additionally, having relied heavily on "buttons" in Leo, I am curious, >> based on the screenshots of the doc, whether there is a plan to incorporate >> this feature? >> >> >> >> Congratulations again on the milestone! >> >> >> >> >> -- 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/73c15b8b-fb4e-4625-b316-073a1d9e5a90n%40googlegroups.com.
