22:10 <ryanstout> adambeynon: how's it going? have you had time to work on that experimental branch much?

22:11 <ryanstout> adambeynon: the one where method names were the same in JS and opal

22:12 <adambeynon> hi ryanstout: not played with it too much for a week or so. The problem of method clashing it too much. We would have to special case about 12 arrays methods, same on string and numeric as well. then there is the problem of not being able to call methods on nil

22:12 <adambeynon> I think it has potential as a coffeescript style language, but not so much as a opal style with a ruby corelib

22:15 <ryanstout> yea

22:15 <ryanstout> oh well, it was an interesting idea

22:15 <ryanstout> probably better to prefer ruby compatibility

22:26 <adambeynon> ryanstout: yeah. maybe come back to it when I have some more time

22:26 <adambeynon> ryanstout: how do you handle formatting in voltrb

22:27 <adambeynon> say, a model attr into a currency

22:27 <adambeynon> or does the reactor stuff do that in itself

22:27 <ryanstout> in most cases the reactive stuff will handle it

22:27 <ryanstout> so if you had a method like this:

22:28 <ryanstout> def dollars(number) ; return '$' + number.to_s ; end

22:28 <ryanstout> that would work fine

22:28 <ryanstout> but things like string interpolation don't return another reactive

22:28 <ryanstout> so there's a few gotchya's

22:28 <ryanstout> usually though anything interacting with a reactive value produces a new reactive value with the dependencies tracked

22:29 <ryanstout> and from bindings, all method calls go to the controllers, so you could just include a "helpers" module in the controller

22:29 <ryanstout> I'm planning on doing some of those number formatting, time, etc.. out of the box

22:34 <adambeynon> yeah, would be nice to have a default set in there

22:34 <ryanstout> yea

22:34 <adambeynon> also good to know the reactive stuff should be able to handle the helper things

22:34 <ryanstout> I really think there's some cool stuff you could do with reactive time values

22:35 <ryanstout> like having it where you can make a reactive time, then say .live_minutes or something, and have it issue a changed value every minute, to automatically create a countdown timer or something

22:35 <ryanstout> so times handle their own updating

22:35 <ryanstout> {some_time.in_minutes.strftime('....')}

22:36 <ryanstout> ^live_minute, not in minutes

22:42 <ryanstout> adambeynon: how does it work in vienna with helpers?

22:42 <ryanstout> I haven't really put a ton of thought into it for volt yet

22:43 <adambeynon> ryanstout: kinda struggling with it. at the moment, I dont really use a reactor style approach, but more of a simple observer

22:43 <adambeynon> like cocoa/ember

22:43 <adambeynon> so, you have to do something like:

22:44 <adambeynon> <div data-bind="amount | format_currency"></div>

22:44 <adambeynon> so when it updates, it runs each formatter in turn (which are either global or methods on the view class)

22:44 <ryanstout> cool, yea I've seen that style a lot

22:45 <adambeynon> batman.js uses it as well (the more I read on batman, the more I like it)

22:45 <adambeynon> just glad I dont have to have lots of get() and set () methods :)

22:46 <ryanstout> yea, the get/set stuff is a pain

22:46 <ryanstout> I think thats part of the reason angular is winning over ember