Yes. You have two options, get the value back in the repl with the portal atom or use the new portal.api/register! to register a var as a command with portal.

hello Chris! long time, we need to get more beers in a vault again 🙂

hey, not sure if I get how to do that

what I would like is to highlight a value in the UI, and run a command (from Portal itself if possible) get a result

maybe, in the command pallet, being able to run things like: (slurp *v), being *v the selected value on the UI, makes sense?

slurp should already be available if the value is slurpable 👌

https://github.com/djblue/portal/blob/master/src/portal/runtime/jvm/commands.clj#L16

I also added https://github.com/djblue/portal#commands which might be a useful read 👌

gotcha, that's nice, altough I still think would be cool to have the option to run arbitrary code on the selected value, is that something you consider to add support for?

(it's something Reveal supports, just FYI)

yeah, that's what Im getting the inspiration from, there the selected value is bound to *v, so we can do these arbitrary runs

I have not missed that functionality since switching to Portal -- but both Reveal and REBL had something equivalent.

I do, however, have Portal setup as an atom (as dev/portal) so if I really need to run arbitrary code on a selected value, I can do it via my editor in an RCF with (some-fn @dev/portal)

(but I haven't needed to do that, expect to test it works 🙂 )

cool, I just tried to do that atom setup, does this look right?

(do
  (require 'portal.api)
  (def user/portal (portal.api/open))
  (add-tap #'portal.api/submit))

when I look that up I see:

user/portal
=> {:session-id #uuid"43472179-f905-4cf1-9f22-a67a184a7cfd"}

(deref user/portal)

which doesn't seem to be an atom, is it a differnet open fn?

It implements the interface/protocol 👌

strange, its coming nil here

Do you have anything selected in the UI?

ah

let me try that

nice!! gotcha 😄

yeah, that works 🙂

It's a pretty cool feature 🙂

Some inspo if it ever is a candidate for inclusion, is from shadow-cljs’ inspector. There’s a small REPL prompt/area where $o is bound to the currently inspected object.

My main reluctance to adding a repl window is doing it will would be a lot of work and it would still fall short of the customized experience each user has within their editor.

Yeah, I think it makes sense to encourage using the atom.