These are chat archives for opal/opal

16th
Jan 2016
Jamie Gaskins
@jgaskins
Jan 16 2016 01:10
@elia: It was on an array, actually. It might be fixed on master, but I tried it on one of the released versions and it didn't work.
Elia Schito
@elia
Jan 16 2016 01:12
@jgaskins as usual let me know if you think it makes sense to backport a fix (if it's feasible of course)
Jamie Gaskins
@jgaskins
Jan 16 2016 01:14
@elia: Okay, I honestly don't remember what I was doing at the time, tbh. I just remember being confused when it didn't work.
Elia Schito
@elia
Jan 16 2016 01:16
@jgaskins :+1: keep me posted on this type of issues, hopefully 0.10 will take less time than 0.9 before it comes out : )
Jamie Gaskins
@jgaskins
Jan 16 2016 01:16
Sweet
Bernhard Weichel
@bwl21
Jan 16 2016 10:09

I am still trying to understand more of Native() vs. .JS
@vais thanks for the pointer to the documentation.

Is it correct to say:

  • Native() pulls an object from Javascript to Ruby-land by creating wrapper (decorator) for a javascript object
  • .JS pokes in javascript Land using ruby style syntax
  • Native returns a Ruby Object and is executed at runtime
  • JS by itself returns nothing, even if it looks like a method. It is kind of syntactic sugar and is basically handled at compile time. Methods sent to JS usually yield the return value of the invoked javascript method/property ... which is a javascript object.
Elia Schito
@elia
Jan 16 2016 11:16
@bwl21 that's correct