~~[PlutoVariableExplorer.jl](https://github.com/JackDevine/PlutoVariableExplorer.jl)~~
[PlutoWorkspaceExplorer.jl](https://github.com/JackDevine/PlutoWorkspaceExplorer.jl) creates a table of the variables in your current Pluto session.
Given my background in MATLAB, this is a feature that I have wanted for a while. Unlike MATLAB (or any other variable explorer that I have ever used), ~~[PlutoVariableExplorer.jl](https://github.com/JackDevine/PlutoVariableExplorer.jl)~~ [PlutoWorkspaceExplorer.jl](https://github.com/JackDevine/PlutoWorkspaceExplorer.jl) is aware of the dependencies between your variables. It also lets you jump to a variable definition through the pluto-links functionality.
Before I register the package I wanted to give people a chance to bikeshed the name or suggest an umbrella package that this functionality could be included in. Feel free to leave any suggestions/feedback here or on Github 🙂
I’d like to thank @fonsp and others for all their work on Pluto and related tools. If Pluto wasn’t such a high quality product, then this work would be much harder and much less rewarding.
### From the package README:
Interactively inspect your workspace values and topology in a [Pluto](https://github.com/fonsp/Pluto.jl) session.
# Usage
Create the following cells: ~~(for now you will have to do `import Pkg; Pkg.add(url="https://github.com/JackDevine/PlutoVariableExplorer.jl")` first)~~
```julia
import PlutoWorkspaceExplorer as PWE
```
```julia
@bind _update PWE.update_notebook()
```
```julia-auto
_update; PWE.variable_explorer(PlutoRunner)
```
If you dont create the `_update` variable, then the workspace explorer will only be updated when you run the cell that defined it. The `_update` variable will change every time you press Shift+Enter.
Example view of the variable explorer:
## Link to the repo
[https://github.com/JackDevine/PlutoVariableExplorer.jl](https://github.com/JackDevine/PlutoVariableExplorer.jl)
## Some known issues
There are some open issues that I am not sure how to fix:
[https://github.com/JackDevine/PlutoVariableExplorer.jl/issues/1](https://github.com/JackDevine/PlutoVariableExplorer.jl/issues/1)
[https://github.com/JackDevine/PlutoVariableExplorer.jl/issues/2](https://github.com/JackDevine/PlutoVariableExplorer.jl/issues/2)
[https://github.com/JackDevine/PlutoVariableExplorer.jl/issues/3](https://github.com/JackDevine/PlutoVariableExplorer.jl/issues/3)
EDIT I also remembered an issue with how pluto-links are handled
[https://github.com/JackDevine/PlutoVariableExplorer.jl/issues/4](https://github.com/JackDevine/PlutoVariableExplorer.jl/issues/4)
I should be able to come up with solutions to these problems in my own time, but any advice or help would be greatly appreciated 🙂
Happy Plutoing and have fun using the variable explorer in your own notebooks!
---
I have missed the workspace explorer too! (but from RStudio). I even recently wrote about it in the feedback field in Pluto, so seeing this post makes me very happy. This package is going to make my life so much easier when writing Pluto notebooks, thank you! Tracking dependencies between objects listed in the inspector and links to the object definitions are two features that make this explorer even better than the equivalents in RStudio and Matlab.
I like the name, on point and descriptive. 👍 Or maybe name it PlutoWorkspaceExplorer? Just because it doesn’t only list variables but everything with a name attached.
But I think the term “Prependencies” is confusing. I suggest finding better terms for these two concepts. Maybe “parent objects” and “child objects”? I think these terms make it more obvious where the different objects are relative to each other in the dependency tree.
---
Thanks for your kind words!
> … maybe name it PlutoWorkspaceExplorer?
> I think the term “Prependencies” is confusing. I suggest finding better terms for these two concepts. Maybe “parent objects” and “child objects”?
Thanks for these naming suggestions, they are really good and I completely agree that they are an improvement over what we have now.
I will make the parent/child change as soon as I can set aside some time.
While I agree that PlutoWorkspaceExplorer is a better name than PlutoVariableExplorer, I will wait a little bit to see if anyone has any other name suggestions, or umbrella projects to suggest before I change the name of the repository, which will break links.
---
Hi all, sorry for the delay. This package has been registered and the naming suggestions above have been applied. That means that you can now try out the workspace explorer with just
`import PlutoWorkspaceExplorer as PWE`
---
Ohhh so cool!! Very exciting @JackDevine !
Did you see this new Pluto feature? It might be useful!
>
>
> \## NOTE: this PR is merged but not yet released! Use \`Pluto#main\` to try it out,… and please let us know how it went! Good feedback is also welcome :)
>
> New JavaScript API to request calculations and data from Julia dynamically. This is useful for:
> \- Lazy loading more data in a display
> - An infinite zooming mandelbrot display
> - A table with millions of rows, that loads data on demand
> \- Letting Julia calculate something on-demand, without requiring a \`@bind\` interaction
> - A \`@bind\` input widget that lets you type Julia code with a submit button, but it validates your input while you type.
> - An interaction where you select two points on a map, and Julia calculates the shortest path between them, and they are displayed \*on the same map\*.
> - Play chess against an AI written in Julia.
>
> Matching AbstractPlutoDingetjes PR: https://github.com/JuliaPluto/AbstractPlutoDingetjes.jl/pull/13
>
> Supersedes #991 and #2392
>
> \# API
>
> The easiest way to use this API is with HypertextLiteral. The use is very similar to \`APD.Display.published\_to\_js\`: the new function \`AbstractPlutoDingetjes.Display.with\_js\_link\` returns a "piece of JavaScript code" that you interpolate directly into a \`\\` tag.
>
> In JavaScript, the "piece of JavaScript code" returns a function. You can call this function with an argument (which will be passed to your Julia function), and it returns a Promise that resolves to the answer from your Julia function.
>
> \`\`\`julia
> @htl("""
> \
> const sqrt\_from\_julia = $(AbstractPlutoDingetjes.Display.with\_js\_link(sqrt))
>
> // I can now call sqrt\_from\_julia like a JavaScript function. It returns a Promise:
> const result = await sqrt\_from\_julia(9.0)
> console.log(result)
>
> \
> """)
> \`\`\`
>
> \# Serialization and inner workings
>
> The request and response use Pluto's internal communication protocol (with MsgPack and WebSocket), so the performance is optimal. The same serialization is used as \`published\_to\_js\`, so in particular, \`Vector{Float64}\` or \`Vector{UInt8}\` are really fast.
>
> Since this API is designed for one-off requests, this communication does not go through Pluto's state management (the request and response are not stored in the state). If multiple clients are connected in parallel, then the messages are not shared between clients.
>
> \# When not to use it
> This API is only meant to support use cases that can not be covered with \`@bind\` and \`Display.published\_to\_js\`. If possible, the use of these APIs is preferred over \`with\_js\_link\` because they will work with the Static HTML export and PlutoSliderServer.
>
> \# Example
> \
>
> \
> \Code\
>
> \`\`\`julia
> @htl("""
> \
> \Input:\
> \ \\
>
> \Output:\
> \