elia has quit [Read error: Connection reset by peer]
elia has joined #opal
_elia has joined #opal
elia has quit [Read error: Connection reset by peer]
_elia has quit [Ping timeout: 260 seconds]
elia has joined #opal
dimaursu16 has joined #opal
elia has quit [Quit: Computer has gone to sleep.]
e_dub has quit [Quit: ZZZzzz…]
e_dub has joined #opal
Steve21 has joined #opal
elia has joined #opal
elia has quit [Client Quit]
Steve21 has quit [Quit: Steve21]
elia has joined #opal
_elia has joined #opal
elia has quit [Ping timeout: 276 seconds]
Steve21 has joined #opal
Steve21 has quit [Client Quit]
ylluminate has joined #opal
[o__o] has quit [Remote host closed the connection]
<_elia>
ryanstout, any progress on extracting reactive from volt?
[o__o] has joined #opal
<adambeynon>
ryanstout: would also like to know about that :D
<ryanstout>
so I’m rewriting it to have the change notifications be async in the browser and using bloom filters instead of a graph to know which objects have events to trigger on. (It makes it much faster in the browser)
<ryanstout>
once thats done I’ll pull it out
<ryanstout>
should be easy to extract, its just taking me a while to rewrite it
<ryanstout>
and I’ve been sidetracked with another project
<_elia>
:)
<ryanstout>
adambeynon: I saw you were working on Vienna the other day, how’s that going?
<adambeynon>
ryanstout: going ok. Extracting stuff out of current apps. Using a batman/angular style data-x attributes. Don't really like that style, but it was quick to get going :)
<ryanstout>
yea
<_elia>
adambeynon, about that syntax error on named groups… ok if I change it to be a runtime error? (rationale is that someone can use libs that have them and just redefine methods)
<_elia>
adambeynon, ryanstout, btw when we put up an opal job board? (enough of activeadmin these days…)
<ryanstout>
_elia: sorry, maybe I’m reading it wrong, what are you asking?
<_elia>
ryanstout, is more like a rant… I still have an 8hr job
<ryanstout>
ah, yea
<_elia>
ryanstout, but am always open to hear about "opportunities"… (← recruiter parlance here) :P
<ryanstout>
hehe, yea
<ryanstout>
so I’ve got the next two weeks off from my current contract, so I’m hoping to finish up the reactive stuff by the end of that
<_elia>
ryanstout has quit [Quit: ryanstout]
_elia has quit [Quit: Computer has gone to sleep.]
dimaursu16 has quit [Ping timeout: 265 seconds]
e_dub has quit [Quit: It's a hard knock life]
dimaursu16 has joined #opal
[o__o] has quit [Remote host closed the connection]
[o__o] has joined #opal
dimaursu16 has quit [Ping timeout: 245 seconds]
ryanstout has joined #opal
dimaursu16 has joined #opal
elia has joined #opal
elia has quit [Quit: Computer has gone to sleep.]
elia has joined #opal
wasnotrice has quit [*.net *.split]
wasnotrice has joined #opal
tils` has joined #opal
dimaursu16 has quit [*.net *.split]
ryanstout has quit [*.net *.split]
tils has quit [*.net *.split]
elia has quit [Quit: Computer has gone to sleep.]
elia has joined #opal
<elia>
brixen, is it ok to use not_supported_on inside an it {} block? (in mspec)
ryanstout has joined #opal
ryanstout_ has joined #opal
ryanstout has quit [Read error: Connection reset by peer]
ryanstout_ has quit [Ping timeout: 265 seconds]
e_dub has joined #opal
<brixen>
guards shouldn't be used inside it blocks
<elia>
brixen, ok, should I then wrap the whole it block?
<elia>
this the code:
<elia>
it "raises a TypeError when pattern can't be converted to a string" do