Major update 🍪

[JerryI]

Client app

• Wolfram Kernel troubleshooting assistant
• Automatic authorization and activation using Wolfram ID and password provided

Frontend

• Improved cursor movement between cells (can jump into the hidden input cell).
• More snippets: code formatting, file uploader.
• More examples.
• More features for editable decorations (try Bra[2] or Ket[-2], for example).

Binaries

• added M1 architecture

---

This discussion was created from the release Major update 🍪.

[amindanial]

First of All, Thanks a lot for this great project. However, there are some issues with Plot3D. The results are not as expected for example, please take a look at the attached two images for the output produced by Jupyter Notebook and the output produced by WLJS.


It would be great to solve this issue. Or let me know if I am mistaken.

[JerryI]

Thanks, @amindanial !

I have forgotten about BoxRations completely. So, now it should be fixed. I also made some changes to the zoom of a camera.
The following changes are in this commit (src/kernel.js file, the rest is recompiled JS from this src).

Shortly after you restart an app it will download a new version of this package.

[JerryI]

PS: Ticks are a bit harder to implement, but at some point it will be done as well.

[userrand]

I am just mentioning that you left what might be some initial text from an llm.

[JerryI]

Hah. Laziness is a bad thing.

[amindanial]

Thanks a lot for your quick response. However, the solution of a differential equation did not present nicely. , check the output of a solution of a differential equation:
From Jupyter:

from your project:

Why does "TemplateBox" appear?
I think it can be presented as in Jupyter, which is a better look and natural.

[JerryI]

In Jupyter this is just picture, however in WLJS this comes as a real editable expression with syntax sugar and so on. The last one comes with some compromises, since we had to recreate all template boxes from scratch using JS and HTML ;)

This C we just haven't implemented yet (probably by accident). However this is a relatively easy fix...

If you prefer to have Jupyter-like view, you can add // Rasterize to your expression. This will do the same trick done by J in the background.

[userrand]

Is it possible to set $PrePrint or $Post to Rasterize or TeXForm as a temporary solution until whatever object gets syntax sugar ? That might be easier than using Rasterize multiple times.

OP could also consider using maybe a replacement rule with another constant if that works (but they might need to be careful that they do not give it a value. Something like \[FormalC] would be nice but that might also need syntax sugar).

Could also be easier if there were as an issue tag for "needs syntax sugar" with a template that shows directly the object that has not been implemented rather than reading through text to find it.

[JerryI]

UPD: fixed in #84

$Post might cause some issues with regular graphics object, so that they will also be rasterized...
In general we constantly improving the editor, so I believe we can make it much better in the future.

Could also be easier if there were as an issue tag for "needs syntax sugar" with a template that shows directly the object that has not been implemented rather than reading through text to find it.

I 'v added the corresponding label to issues. So. please, feel free to report! Mathematica has a lot of those decorative things, however, sometimes it is covered by a few "real" TemplateBoxes.