01:31 <fkchang`> adambeynon: what causes sprockets to compile opal files into 1 file instead of separate. When I include opal-irb in a rails project, all the opal files get compiled into the application.js in dev mode and then jquery is not included

04:55 <GitHub134> [opal] elia pushed 3 new commits to master: http://git.io/d9BGqQ

04:55 <GitHub134> opal/master 0ca07f0 Kyle: Removing giant if statement...

04:55 <GitHub134> opal/master 2f49543 Kyle King: Make the Opal Tilt template work in any context.

04:55 <GitHub134> opal/master fc841f1 Elia Schito: Merge pull request #570 from kylekyle/tilt...

11:35 <wmnnd> Hey there, recently I asked about the status of the DateTime class from the Ruby standard libary in Opal.

11:35 <wmnnd> I was told that it is not yet supported and there are no plans to implement it.

11:36 <wmnnd> However, I have just tried using the native JavaScript date element and it seems to be accessible by Opal pretty much like a Ruby Date object.

11:37 <wmnnd> So I wanted to ask: Is this the way Dates should be dealt with in Opal? http://ur1.ca/i2der

11:44 <meh`> wmnnd, Time is accessible

11:44 <meh`> you don't need to wrap it yourself

11:44 <meh`> it works for you because Time is bridged to `Date`

11:45 <meh`> DateTime isn't

11:45 <meh`> Time, Date and DateTime are different things

11:54 <wmnnd> I see, JavaScript Date objects seem to get mapped to Ruby core Time objects.

11:56 <meh`> wmnnd, yes, Time is bridged to `Date`

12:00 <wmnnd> Mhm, the Time class even brings consistent "rolling over" for dates like 2014-02-29 as in Ruby. Though, I personally find that rather undesirable^^

12:08 <wmnnd> But I keep being impressed by Opal :-)

19:06 <IlIlIlIlIlIlI> is it possible to build js code from .rb files from the command line utilities opal or opal-build?

19:07 <IlIlIlIlIlIlI> I'm trying to build kramdown with $ opal --compile -I lib/kramdown/ lib/kramdown.rb

19:07 <IlIlIlIlIlIlI> the stdout is kind of not what I'd expect :D

19:14 <IlIlIlIlIlIlI> I've read the documentation, but the command line interface doesn't seem to be explained or exemplified

19:14 <IlIlIlIlIlIlI> and as a ruby non-native, I'm pretty much looking for a quick and dirty solution :)

19:15 <ryanstout> IlIlIlIlIlIlI: I’m not sure where the command line tools is at the moment, my guess is adambeynon or elia would know

19:16 <IlIlIlIlIlIlI> thanks

19:57 <wmnnd> Hey there, I just came across a problem because Opal seems to handle while loops different from Ruby MRI.

19:59 <wmnnd> Hey there, I just came across a problem because Opal seems to handle while loops different from Ruby MRI.

19:59 <meh`> wmnnd, what's the issue?

20:01 <wmnnd> meh`: Sorry, irssi died. The problem seems to be that MRI evaluates the condition after running the scope once regardless of the condition whereas Opal seems to evaluate the condition before running the scope.

20:02 <wmnnd> meh`: So, this will give you no output in Opal, unlike in MRI: http://ur1.ca/i2g81

20:03 <meh`> wmnnd, open an issue please

20:04 <wmnnd> Sure!

20:25 <fkchang`> adambeynon: ping

20:46 <adambeynon> hye fkchang`

20:46 <adambeynon> hey*

21:05 <fkchang`> adambeynon: need a tip in debugging running opal-irb with opal-rails, just including the gem causes all the opal files to be compiled to application.js instead of as individual files. That would not be so bad, but jquery also doesn't get included. Looking for some pointer to how opal interacts w/sprockets to try to figure out what's wrong.