emmaccode
commented
8 months ago Thank you for kind words @PallHaraldsson , and your support for all this time.
A ( I )
This certainly would not be a bad idea -- I plan to expand this documentation (and rewrite some sections) into an eventual documentation that hosts Olive. The thing is that languages are added to Olive via an extension. OlivePy is cited as an example because this package is nearly done. And yelp, it ties the objects from all languages in together -- just as the tomlvalues cells do for data into Julia. There are just a few things left to do on that project, mainly some fixes for the ability to open .py files (rather than just using python in a .jl file) and updates to the syntax highlighter.
I did not use any Pluto tech-stack. Pluto files are not regular Julia files, though they do contain normal Julia code; they contain special characters which denote cells and a list of cells with their evaluation order at the top. Fortunately, IPyCells checks if a .jl file contains Pluto cells, Olive cells, or just regular Julia text -- so reading Pluto is in fact supported.
Writing to pluto... not so much.
A (II)
Hmm.. If I understand this correctly, you mean you are able to select from the end of the text but not the start? I will try to replicate the issue on my machine tomorrow. The error C seems to be coming from the fullstack parser -- I will look into making some updates to fix both of those. Thank you for bringing these to my attention :)
B
The line that this code comes from just does Pkg.add("Pkg"). This error might be some sort of fluke or something. I am not exactly sure how I could replicate this, or if solving such an issue falls into my hands. I will make sure to look into it a bit more before writing it off though.
Thanks for the issue and letting me know all of this, as well as the feedback ! Have a wonderful rest of your day 👍🏻
VarLad
PallHaraldsson
Hi,
It's great to see your project finally registered and I also noticed your new Gattino plotting. I can't understand how productive you are.
A. Your doc could mention R (and Python) more prominently, since I see it supported too: "Here is an example from OlivePy, the python Cell"
I'm looking forward to trying out your project more, it seems to simply just work, after a (one-time, I guess) small delay.
Since this is a Julia project, Python users would need to set it up. I'm a Julia user first, and unlike Pluto which (kind of) Julia only, I think it's great you support more. I'm thinking it might draw in more Python and R users; to call Julia, reuse both ways. Possibly a really good setup for them could be done with a python package using JuliaCall from PythonCall.jl, at least when the protect more polished.
I'm curious, did you reuse much of Pluto (or its dependencies), since I can't see that done? Do you support importing all Pluto files, since they are plain Julia code? They have features that are based on JavaScript, so I'm not sure, maybe all of their features on from Jupyther just work?
I've seen people argue against (Python) notebooks, for some reasons, mostly that I recall, not being reactive, or reasons not applying to Pluto nor your project, except maybe if importing.
A. There were slight editing/cursor and display issues:
A = [1 2;3 4] 2×2 Matrix{Int64}: 1 2 3 4
A^2.1 2×2 Matrix{ComplexF64}: 8.24768+0.02953im 11.8464-0.0135078im 17.7695-0.0202617im 26.0172+0.00926826im
[I could copy paste if highlighting from the result up, but strangly not if highlighting my code A, and "down" if you understand.]
I meant to type, ^2 and did, but sometimes ² which I could do with the keyboard (by accident, with same keys on my Icelandic keyboard), and it does display, but see concole error in C. on it.
B. When using first there was a slight wait, I thought frozen explained by:
[that error seemingly didn't stop me, at least not yet.]
C.