Off topic: http://blog.juxt.pro/posts/why-clojurescript-matters.html really interesting piece in that it applies equally well to Opal (at least the first half of the article, titled "Avoid Splitting"). I feel there's a sea change taking place - just a year ago splitting a product team into back-end and front-end made all the sense in the word to me, and felt like the right way to do it.
So I took 2 separate approaches at integrating opal-irb w/opal-playground
embedding it in the object
pros - easy to make it span the bottom
cons - need to extend it to communicate remotely w/the iframe (coz we want to run everything against the iframe's objects, not that of opal-playground)
embedding it in the iframe directly
pros - it runs against the objects in the iframe
can't pull the ui away from the iframe Kind of stuck at which way to continue, approach 1 would require rewriting a lot of opal-irb to make it work w/a remote iframe, approach 2 limits the UI strongly. Maybe approach 2 to start, giving the capability now, and then down the road doing approach 1, but that would be reinforced more if I could see another use for this functionality