12:07 <wmnnd> Hey there, I'm trying to get/set the state of an input[type=checkbox] with opal/opal-jquery. However, I'm not quite sure how to do that. This is what I have tried so far, but with no success: http://pastebin.com/D14psz61

12:52 <wmnnd> Alright, checkboxes can wait, but how do I pass data to a request with HTTP.post?

12:52 <elia> wmnnd, you sure the selector is right (just to sort out common errors)

12:55 <wmnnd> Yes, I'm pretty sure. If I call remove, the checkbox vanishes.

12:55 <wmnnd> Also, nevermind about the POST request, I figured that out by looking at the opal-jquery source :)

12:58 <adambeynon> wmnnd: I have never tried to use checkboxes via opal-jquery, so it might be the case that it isnt implemented

12:59 <adambeynon> or rather, the method hasnt been bridged from jquery

12:59 <adambeynon> give me 10 mins and I will have a look

13:01 <wmnnd> adambeynon: That would be awesome. However, I will be away for a little while now so no hurry in looking it up :)

13:02 <wmnnd> Maybe, if it isn't bridget yet, it would be even nicer (or more rubyesque) if checkboxes would return true/false for their value, because that seems to me what they're really all about :)

13:04 <adambeynon> wmnnd: yep. I want to make opal-jquery a lot more rubyeqsue

13:04 <adambeynon> I dont like the element.html("foo") style

13:05 <adambeynon> hmm, a bit late for that message perhaps..

13:08 <elia> adambeynon, no worries, I'm still reading :P

13:16 <adambeynon> :D

13:20 <elia> adambeynon, you done anything on the sprockets side?

13:20 <elia> adambeynon, I'd hate to overlap work

17:11 <adambeynon> elia: sorry, completely missed those two notifications

17:11 <adambeynon> I havent got any further than what was discussed

17:12 <adambeynon> I think we could go down the route of handling a ruby require vs a normal sprockets require specially

17:13 <adambeynon> elia: do you think it is a good idea to include a version of jquery.js inside opal-jquery

17:13 <adambeynon> the demo code works well until I keep having to say "go download a version of jquery and add it into the load path"

17:14 <adambeynon> Im thinking maybe an optional jquery.js version

17:14 <adambeynon> require 'opal-jquery/jquery.js'

17:14 <elia> adambeynon, I'd go with jquery-rails

17:15 <elia> it's already bundled with rails and does just that

17:15 <adambeynon> elia: problem is that it requires the whole rails stack

17:15 <elia> ouch

17:15 <meh`> in lissio

17:16 <meh`> I minified marked.js, converted it to base64 and added it to the __END__

17:17 <elia> classy

17:19 <elia> adambeynon, yes I think it's ok to bundle under a namespace and tell rails ppl that they can use their own

17:20 <elia> adambeynon, if you also vendor zepto that could be a good excuse to ask for an explicit require

18:37 <wmnnd> adambeynon: Your message was not too late, I read it in the log :-)

20:33 <dragonnkh> evening

21:30 <wmnnd> Hey there, I have yet another question: How do you use window.setInterval in Opal/opal-jquery? The $window element doesn't seem to support it and if you use `window.setInterval(Opal.$something, time)`, the called function will not work. It seems to get called but it tells me that self.$puts is not a function. When I call the function directly from Opal, everything works fine.

21:41 <kings> I'm loving opal !!!

22:27 <fkchang> wmnnd: u still having problems with that?

22:27 <wmnnd> Yes.

22:28 <fkchang> wmnnd: not exactly your issue, and possibly dated but I show how to wrap setInterval and have a block get called taht calls ruby. I hope it's not out of date, haven't tested it since, but it should give you ideas

22:28 <fkchang> http://funkworks.blogspot.com/2012/10/game-of-life-in-opal-ruby-in-browser.html

22:29 <fkchang> wmnnd: I also think it's wrapped elsewhere in opal now, maybe opal-browser

22:30 <wmnnd> fkchang: Thank you, I'll take a look later :)

22:31 <fkchang> wmnnd: ok, hope it helps

22:51 <fkchang> ryanstout: do any clojure?

22:51 <ryanstout> I've been learning it

22:51 <ryanstout> but the syntax drives me crazy

22:51 <ryanstout> I'm just not a lisp person, hehe

22:51 <fkchang> I've been pointed to pedestal -- haven't checked it out yet, but I imagine lots of ideas to life

22:51 <fkchang> s/life/slift

22:51 <fkchang> lift

22:51 <ryanstout> yea, I was checking out pedestal yesterday actually

22:51 <ryanstout> similar ideas

22:53 <ryanstout> fkchang: have you done much clojure?

22:54 <fkchang> ryanstout: I haven't, but I actually did lisp early in my career, ages ago

22:54 <fkchang> so in theory, I'm a real good fit, but never got around to spending any time w/it

22:56 <fkchang> ryanstout: re: pedestal, this sentence from a friend describing pedastal seems to fit my desired philosophy "Pedestal is similar. You write your app, it seems to worry about what goes where. At least from the short time I played with it."

22:57 <ryanstout> fkchang: not sure I follow

22:58 <fkchang> I was talking about how meteor "blurs" front and backend, same code running on both sides, and that was the answer... but the idea of writing the code in 1 place and the framework knowing what to put where is the experience I believe I want to provide

22:58 <meh`> wmnnd, $$.setInterval -> { whatever }, time

22:58 <ryanstout> fkchang: yea, I'm going for something similar I think

22:59 <ryanstout> though its nice with stuff like validations to just have it run on both sides

23:01 <ryanstout> fkchang: so are you going to work on your own framework?

23:08 <fkchang> ryanstout: If I can help it, I will contribute/extend someone elses

23:09 <ryanstout> fkchang: I'm almost to the point on mine where I'll be needing some help :-)

23:09 <ryanstout> fkchang: I need to do another video, its come a long way since last time

23:09 <fkchang> ryanstout: then maybe that's the one. I have to admit I'm very partial to the components in lissio

23:10 <ryanstout> mine's very componetized as well. I didn't show any of that in the last video

23:10 <fkchang> and you saw my DSL from the other day, I think building that on top lissio, makes some sense

23:10 <ryanstout> and I have all of the reactive stuff working :-)

23:10 <fkchang> ryanstout: I'm certain win-over -able

23:10 <ryanstout> fkchang: cool, I'll probably do another video tomorrow :-)

23:11 <fkchang> ryanstout: that's cool, keep in mind, I'll want to build framework specific panes/editors into opal-inspector

23:11 <ryanstout> yea, thats something I want to have in mine

23:35 <ryanstout> fkchang: does lift do anything on the front end? I thought it was just a backend framework

23:36 <wmnnd> meh`: Thanks, as always :-) I'll try it out tomorrow.

23:50 <fkchang> ryanstout: I thought lift had front end support

23:50 <ryanstout> fkchang: maybe, I haven't looked at it in a while

23:51 <fkchang> though I don't think I want to go that direction, I got the impression that lift was super powerful, and thus correspondingly complicated, which is why TypeSafe went w/Play instead

23:51 <fkchang> I'm looking for a top level DSL that is "easy enough for your kids to webapps"

23:52 <ryanstout> seemed like Play was basically scala on rails

23:52 <ryanstout> (or java)

23:52 <fkchang> play started out that way, then diverged