<meh`>
the other stuff is in production either internal or NDA
<meh`>
knoopx, were you looking for something specific?
<knoopx>
nope, just wanted to see how ruby on the frontend looks like
<knoopx>
and how creative people can be
<meh`>
knoopx, then lissio is a nice example :)
<meh`>
everything is Ruby
<meh`>
including CSS and HTML
Kilo`byte has quit [Ping timeout: 248 seconds]
<meh`>
it was part of the presentation of rubyconf
<knoopx>
opal is an interesting project, lets see how everything evolves
<knoopx>
a ror-alike on the top of opal running on the frontend could be a epic
Kilo`byte has joined #opal
<meh`>
knoopx, that's the direction vienna is taking
<meh`>
it strives to integrate with the rails backend
<meh`>
lissio goes a different way
Kilo`byte has quit [Ping timeout: 248 seconds]
<knoopx>
by ror I mean the meaning of "the defacto web framework implementing industry practices for rapid web development and developer happiness"
Kilo`byte has joined #opal
<knoopx>
not to copy ror api/practices
knoopx has quit []
Kilo`byte has quit [Ping timeout: 252 seconds]
Kilo`byte has joined #opal
Kilo`byte has quit [Ping timeout: 248 seconds]
Kilo`byte has joined #opal
meh` has quit [Read error: Operation timed out]
Kilo`byte has quit [Ping timeout: 246 seconds]
Kilo`byte has joined #opal
Kilo`byte has quit [Ping timeout: 265 seconds]
Kilo`byte has joined #opal
ryanstout has joined #opal
Kilo`byte has quit [Ping timeout: 245 seconds]
Kilo`byte has joined #opal
kludge` has quit [Ping timeout: 246 seconds]
Kilo`byte has quit [Ping timeout: 272 seconds]
Kilo`byte has joined #opal
ryanstout has quit [Quit: ryanstout]
Kilo`byte has quit [Ping timeout: 265 seconds]
Kilo`byte has joined #opal
kludge` has joined #opal
Kilo`byte has quit [Ping timeout: 252 seconds]
Kilo`byte has joined #opal
Kilo`byte has quit [Ping timeout: 252 seconds]
Kilo`byte has joined #opal
Kilo`byte has quit [Ping timeout: 272 seconds]
Kilo`byte has joined #opal
elia has joined #opal
Kilo`byte has quit [Ping timeout: 272 seconds]
Kilo`byte has joined #opal
adambeynon has joined #opal
<adambeynon>
hi elia !
<elia>
adambeynon, hey there!
<elia>
doing well?
<adambeynon>
yeah, not too bad actually - got the day off, so Im going to work on an opal demo app
<elia>
(cool we have HashRouter, LocationRouter and TurbolinksRouter btw!)
<adambeynon>
something a bit better than a simple todo thingy :)
<elia>
good!
<elia>
I'm slowly sneaking some work on refactoring rake tasks…
<elia>
mspec rake tasks especially
<adambeynon>
ah yes, I saw the branch - looks good
<adambeynon>
it did need a cleanup
<elia>
adambeynon, yeah, you use the rackup or rake mspec for testing (usually)?
<elia>
…or rake spec:foo:bar
<adambeynon>
elia: I always run `rake mspec`
<adambeynon>
I never use the rackup config
<elia>
mmm, thinking of ditching the config.ru stuff then
<adambeynon>
It was only there to debug cross browser, but thats not really needed anymore
<elia>
adambeynon, I have another doubt… where you think it's better to keep mspec fixes? (talking about the mri side of things, I'm leaning toward lib/mspec/opal/*)
<adambeynon>
elia: yeah, that seems fine to me - lib/ is in our loadpath anyway, so it should be fine in there
<adambeynon>
elia: btw, I cant think of any good example apps to build - any ideas? :)
<elia>
adambeynon, for the codemotion I was prepping a websocket chat
<elia>
adambeynon, I'd steal from angular/ember though
<elia>
adambeynon, if we can get anywhere near those in terms of "doing nothing" and "just works" would be awesome
Kilo`byte has quit [Ping timeout: 252 seconds]
<adambeynon>
elia: I have a lot of "just works" extensions to vienna I use in my apps, but not sure if its a good idea for vienna to have them
<adambeynon>
vienna feels a lot like backbone style
<adambeynon>
but the extensions move towards emberjs style apps
<adambeynon>
luckily its easy to extend the classes to be more useful
<adambeynon>
I really dont want to have to start supporting 2.0.0 and 1.9.3 versions of opal
<adambeynon>
once we have everything done for 1.9.3, we split it off onto a branch, and then master becomes for 2.0.0
<meh`>
and I really don't want to fix specs for 1.9.3 that then will be broken on 2.0.0
<meh`>
adambeynon, yeah, not gonna happen on my side
<meh`>
it's useless work
<meh`>
just stick to 2.0 and fix the bugs
<meh`>
if something breaks in rspec, set 1.9.3 on in opal-rspec
GitHub87 has joined #opal
<GitHub87>
opal-rspec/master fe80fe9 Adam Beynon: Redefine Enumerable#flat_map for rspec to use
GitHub87 has left #opal [#opal]
<GitHub87>
[opal-rspec] adambeynon pushed 1 new commit to master: http://git.io/M-mRnA
<meh`>
not keep everything behind because of a single library
<adambeynon>
meh`: we are nowhere near 1.9.3 support, let alone 2.0
<meh`>
adambeynon, that's exactly my point
<meh`>
there's no point in targeting 1.9.3
<meh`>
let's just target 2.0
<meh`>
otherwise set to 1.8
<meh`>
because we're lying about 1.9.3 too
<meh`>
if the problem is in rspec
<meh`>
fix it in rspec
<meh`>
set RUBY_VERSION to 1.9.3 in rspec for the time being
<meh`>
there are already other fixes
<meh`>
one more won't hurt
<meh`>
and leave 2.0 so I can keep working on fixing the specs
<meh`>
and I repeat, I won't fix specs for 1.9.3
<meh`>
because it's useless work, we should target 2.0 and be done with it
<e_dub>
for what its worth, jruby is moving towards supporting only 2.0, and then 2.1 in next major release i believe
<adambeynon>
right, and I want opal to be targetting 2.0.0 as well, but we cant release gems stating we are 2.0.0 when we start breaking libs that use RUBY_VERSION to feature check
<adambeynon>
and
<adambeynon>
0.6.0 should be for big changes like that
<meh`>
adambeynon, that's what I'm saying
<meh`>
adding back native in the corelib
<meh`>
and setting back to 1.9
<meh`>
should have been commits in a stable branch
<meh`>
not on maste
<meh`>
r
<meh`>
maste is for development
<meh`>
e_dub, yeah, everyone is doing that
<meh`>
JRuby and Rubinius
DrShoggoth has joined #opal
GitHub101 has joined #opal
<GitHub101>
[opal] adambeynon pushed 1 new commit to master: http://git.io/PTEtqw
<GitHub101>
opal/master 26876e1 Adam Beynon: Rename -@NUM parser token to tUMINUS_NUM
GitHub101 has left #opal [#opal]
GitHub99 has joined #opal
<GitHub99>
opal-rspec/master 571f57e Adam Beynon: Add very simple mock spec for testing stubbed methods...
GitHub99 has left #opal [#opal]
<GitHub99>
[opal-rspec] adambeynon pushed 1 new commit to master: http://git.io/3AnBAA
<adambeynon>
meh`: 0.5.x is hardly stable. There is a load of compiler/lexer rewriting that applies to both 1.9.x and 2.0.x
<adambeynon>
its not as if our current impl is stable and ready to go
<meh`>
adambeynon, call it release, call it stable, call it however you will