🚀 Announcing LeoJS 1.0 🦁

[Félix]

📢Announcing LeoJS 1.0🥳

Dear Leonistas and Fellow Developers,
I am beyond thrilled to announce that after more than five years of relentless development, refinement, and passion, LeoJS has reached its 1.0 release! This milestone marks the beginning of a new era for Leo and VSCode, and I couldn't be more excited to share it with you all.

Join the Community!
This release would not have been possible without the incredible support and feedback from the community. I invite you all to join the discussion, share your experiences, and contribute to the ongoing development of LeoJS here on this forum, or on the LeoJS issues page.

Try LeoJS 1.0 Today!

Get it via auto-update, or download LeoJS 1.0 and experience all the features of Leo from within VSCode. (Also available on open-vsx.org for VSCodium)  Your feedback is invaluable, so please don't hesitate to share your thoughts and suggestions.

What's New in LeoJS 1.0 Since 0.2.15

• Support for Older .leo Files: LeoJS can now open older formats of .leo files (from version 4.7 and before) that contained 'tnodelist' attributes.
• Improved Command Icons: Fixed the disabled/enabled state of 'Refresh from disk' and 'Extract Names' command-icons in the menu above the body-editor.
• Customizable Command Icons: The command-icons above the outline pane are now customizable. They can also be set/unset in the LeoJS setting panel.
• Optimized Log Pane: The log pane is only forcefully shown at startup on first installation or during version updates.
• Default .leojs JSON Format: The .leojs JSON file format is now the default when saving new untitled files, instead of the .leo XML format.
• Bug Fixes: Fixed an elusive bug where sometimes a false Leo file change detection was triggered when saving.

Thanks to Edward and All of Leo's Contributors!
I will quote Thomas, who rightfully said "Leo as we know it today is the result of a long evolution, during which the ideas of many people helped to shape the present-day Leo.  I want to emphasize the idea of an "evolution", because this evolution has led to the amazingly wide utility that Leo users learn as they use it more and more.  The continuous improvement over decades is one of the things that separates Leo from so many other editor and even outliner projects."

Since I merely translated Leo's codebase from python to typescript, you are all in fact the authors of LeoJS! So thank you again for being a part of this journey.

Here's to many more years of innovation and collaboration!

Best regards,

Félix Malboeuf

[Edward K. Ream]

On Sat, Jul 27, 2024 at 5:08 PM Félix <felix...@gmail.com> wrote:

> I am beyond thrilled to announce that after more than five years of relentless development, refinement, and passion, LeoJS has reached its 1.0 release! This milestone marks the beginning of a new era for Leo and VSCode, and I couldn't be more excited to share it with you all.

Félix, nobody else in the world could have done what you have done.

For over a decade I dreamt that a "young genius" would come along and port Leo to a more popular platform. But I never dreamt that anyone would rewrite all of Leo's core in Typescript for vs-code. LeoJS is way beyond a dream come true.

With love, admiration and affection,

Edward

[Thomas Passin]

Congratulations and thank you!  But these words seem too weak to acknowledge the commitment and effort you have put into the work (not to mention the additional effort to get the LLM-generated images for each release).

I think we should all acknowledge Edward Ream too.  He has supported the project in every way where another, lesser person could have been jealous, proprietary, and obstructive.

[jkn]

I fully agree on both counts. I am not (yet?) a 'strong' user of LeoJS, but am full of admiration for the effort and results.

    J^n

[Viktor Ransmayr]

Congratulations on this achievement !

Viktor

--
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 leo-editor+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/leo-editor/10822ab0-11d6-4964-bfe0-ca6eb6795135n%40googlegroups.com.

[Ray wang]

wow,  good news.   Thank you verrrrry much.

[Félix]

Thanks to all of you for your kind messages! I'm really glad that you like it!

🎉 I've just published a minor update with LeoJS 1.0.1 🥳

This update is intended to facilitate and simplify using common javascript libraries from Leo Scripts: Until LeoJS supports 'imports/require' statements in its Leo Scripts, all the libraries already included in LeoJS are available on the global scope of Leo Scripts, as if imported at the beginning of the script.

They are: 

Default Node.js librairies: Buffer,  crypto,  os,  path, process, child_process (Some with limited functionality when using in VSCode for the web)

Other 3rd party libraries: SQL, JSZip, pako, showdown, dayjs, md5, csvtojson, elementtree, ksuid

For more details, and for actual Leo Script samples that demonstrate the usage of each of those, please see: https://github.com/boltex/scripting-samples-leojs

Note: You can also press the '.' dot on your keyboard when viewing a github repo to edit its content live in VSCode for the web ! 

Just make sure you installed / updated to LeoJS 1.0.1 when using in VSCode for the web 😁

Cheers!

Félix

[Félix]

🎉 LeoJS 1.0.3 is here! 🎉

I'd like to announce that the latest version of LeoJS now supports the functionality of leoMarkup.py commands:

• adoc
• pandoc
• sphinx

If you've used these commands in Leo before, please give them a try in LeoJS and report any issues on the LeoJS issues page. Your feedback is invaluable!

About leoRST.py and its rst3 command:
A big thank you to Viktor Ransmayr for helping me test the various available third-party 'docutils' equivalents. Unfortunately, they still don't cover enough RST directives to be worth including in LeoJS—yet. But don't worry, I’ll keep searching for the right docutils alternatives or actual JS/TS implementations. Stay tuned for future updates!

As always, your suggestions for new features or workarounds for missing ones are what keep this project moving forward. Your ideas and feedback are my greatest motivation! 🚀

Cheers,
Félix

[Félix]

Oups! Released LeoJS 1.0.4 because of last minute fix to support VSCode on the web after having changed dependencies without proper testing! (Doh!)

Félix

[Félix]

Just thought that I'd should add that today marks the fifth anniversary of the beginning of this incredible journey! I want to extend my deepest gratitude to Edward and everyone who has contributed to Leo over the years.


Félix 

[Viktor Ransmayr]

Hello Félix,

Am So., 11. Aug. 2024 um 04:06 Uhr schrieb Félix <felix...@gmail.com>:

Just thought that I'd should add that today marks the fifth anniversary of the beginning of this incredible journey! I want to extend my deepest gratitude to Edward and everyone who has contributed to Leo over the years.

I double-checked & shortly before that - on August 2nd, 2019 - Edward had just released Leo v6.0 .

Now Leo is at version 6.8.1, LeoInteg at version 1.0.23  & LeoJS is at version 1.0.4. - What a great journey indeed ...

THANKS A LOT to Edward, yourself & everybody else from Leo's great community !

With kind regards,

Viktor

[Viktor Ransmayr]

Félix schrieb am Sonntag, 11. August 2024 um 00:44:56 UTC+2:

🎉 LeoJS 1.0.3 is here! 🎉

I'd like to announce that the latest version of LeoJS now supports the functionality of leoMarkup.py commands:

• adoc
• pandoc
• sphinx

If you've used these commands in Leo before, please give them a try in LeoJS and report any issues on the LeoJS issues page. Your feedback is invaluable

Has anyone been able to test / try out the @sphinx implementation in LeoJS ?

Since I did not have any own examples available I looked for some w/i  Leo-Editor ...

The closest I found was the outline 'sphinxDocs.leo'.

When I tried the 'sphinx-with-preview' command I received the following output:

    LeoJS 1.0.4, master branch, build 221cbb7
    2024-08-10 20:08:03 -0400
    Node.js v20.14.0, VSCode version 1.92.1
    linux x64 (build 6.6.42-1.qubes.fc37.x86_64)
          home: /home/user
    leo-editor: /home/user/.vscode-oss/extensions/boltex.leojs-1.0.4-universal
    reading settings in leojsSettings.leojs
    reading settings in /home/user/.leo/myLeoSettings.leo

    ...

    reading settings in /home/user/PyVE/PyPI/Leo/lib/python3.12/site-packages/leo/doc/sphinx-docs/sphinxDocs.leo
    read 14 files in 0.09 seconds
    read outline in 0.10 seconds
    preview not available for sphinx
    sphinx: wrote 0 files in 0 sec.

With kind regards,

Viktor

[Thomas Passin]

That's in the LeoPython code too:

    if preview:
        if kind == 'sphinx':
            g.es_print('preview not available for sphinx')

Félix has just reproduced the Python code. The only way I can see how to get a "preview" for Sphinx would be to get Sphinx to process the tree and generate its standard output: a tree of HTML files, then load the top file into a browser.  Not much of a "preview", that.

[Félix]

Just a quick message added to this thread to let you know I've just released LeoJS 1.0.5. 

This release solves a problem when writing .md markdown files that removed the leading newline inside sections. 

I really want a good support for this type of documentation files in Leo and LeoJS, as it's becoming one of the most popular format - along with rst - so, I'm really glad I caught this bug early! 

Félix

[Edward K. Ream]

On Mon, Aug 19, 2024 at 9:43 PM Félix <felix...@gmail.com> wrote:

Just a quick message added to this thread to let you know I've just released LeoJS 1.0.5. 

This release solves a problem when writing .md markdown files that removed the leading newline inside sections. 

Excellent. Keep up the good work ;-)

Edward