marcandre has quit [Remote host closed the connection]
harrow has quit [Ping timeout: 252 seconds]
harrow has joined #opal
e_dub has quit [Ping timeout: 240 seconds]
e_dub has joined #opal
meh` has joined #opal
DouweM has quit [Ping timeout: 245 seconds]
dfranciosi has joined #opal
elia has joined #opal
GitHub120 has joined #opal
<GitHub120>
[opal-haml] adambeynon pushed 1 new commit to master: http://git.io/2TE2-Q
<GitHub73>
[opal-haml] adambeynon tagged v0.1.0 at bbd6157: http://git.io/hsus6g
GitHub73 has left #opal [#opal]
GitHub120 has left #opal [#opal]
GitHub73 has joined #opal
<GitHub120>
opal-haml/master 9b1dccd Adam Beynon: v0.1.0
fkchang has quit [Ping timeout: 248 seconds]
GitHub85 has joined #opal
<GitHub85>
opal-haml/master cf5015e Adam Beynon: Add changelog
GitHub85 has left #opal [#opal]
<GitHub85>
[opal-haml] adambeynon pushed 1 new commit to master: http://git.io/WhbYBA
elia has quit [Ping timeout: 250 seconds]
elia has joined #opal
GitHub153 has joined #opal
<GitHub153>
opal-haml/master c6567b2 Adam Beynon: v0.2.0
<GitHub153>
[opal-haml] adambeynon pushed 1 new commit to master: http://git.io/IOqPmg
GitHub153 has left #opal [#opal]
GitHub166 has joined #opal
<GitHub166>
[opal-haml] adambeynon tagged v0.2.0 at a9ec74a: http://git.io/bvZrqA
GitHub166 has left #opal [#opal]
<elia>
adambeynon, (y)
GitHub8 has joined #opal
<GitHub8>
opal-haml/master ea15b55 Adam Beynon: Version
GitHub8 has left #opal [#opal]
<GitHub8>
[opal-haml] adambeynon pushed 1 new commit to master: http://git.io/B8U8QQ
kludge` has quit [Ping timeout: 252 seconds]
<adambeynon>
elia: using haml in all my apps now. much nicerr
<adambeynon>
updating opal-todos to use it as well - and fix some small bugs
<elia>
adambeynon, grrr, still waiting for to show me the appz
<elia>
:D
<meh`>
psh, should have used paggio ( ≖‿≖)
kludge` has joined #opal
<adambeynon>
:D
<adambeynon>
elia: regarding that vienna commit (for the versions), I think it might be a good idea to apply that to all the gems
<adambeynon>
opal-jquery, opal-rspec etc
<adambeynon>
perhaps make it even more libreal in versions
<adambeynon>
>= 0.5.0, < 1.0.0
<adambeynon>
opal api is now pretty much fixed until 1.0.0
<adambeynon>
its just going to be lots of bug fixing until 1.0.0
GitHub103 has joined #opal
<GitHub103>
opal-todos/master f52992d Adam Beynon: Use haml templates
GitHub103 has left #opal [#opal]
<GitHub103>
[opal-todos] adambeynon pushed 1 new commit to master: http://git.io/CeWS4g
<elia>
adambeynon, ok, we can shrink it later if any significant (read breaking) change comes along
<adambeynon>
yep. the tight version constraints are really awkward now in my rails apps - its a choice between using the new source map stuff, or using opal-jquery/opal-rspec etc etc
<adambeynon>
and, for anything 0.5.x, all it needs is an explicit "opal-sprockets" in the Gemfile
<elia>
ok, then
<elia>
meh`, lol, sooner or later i'll try paggio with vienna
<meh`>
elia, can you tweet that opal-browser is now using paggio?
elia has quit [Quit: Computer has gone to sleep.]
elia has joined #opal
<elia>
meh`, sure!
<meh`>
thanks
<elia>
meh`, just not sure if it's better to wait US to fully awake…
<meh`>
elia, better wait
GitHub103 has joined #opal
GitHub103 has left #opal [#opal]
<GitHub103>
[opal-todos] adambeynon pushed 1 new commit to master: http://git.io/72Ln7A
<GitHub103>
opal-todos/master 1ede739 Adam Beynon: Update selected class on router for filters
DouweM has joined #opal
fkchang has joined #opal
fkchang has quit [Ping timeout: 264 seconds]
e_dub has quit [Ping timeout: 240 seconds]
GitHub28 has joined #opal
<GitHub28>
[opal-todos] adambeynon pushed 1 new commit to master: http://git.io/hWNbig
GitHub28 has left #opal [#opal]
<GitHub28>
opal-todos/master 826c42b Adam Beynon: Slight tidy-up
e_dub has joined #opal
elia has quit [Quit: Computer has gone to sleep.]
dfranciosi has quit [Remote host closed the connection]
GitHub12 has joined #opal
<GitHub12>
opal/master cfc5028 Adam Beynon: Support any Tilt template for index_path in Opal::Server
GitHub12 has left #opal [#opal]
<GitHub12>
[opal] adambeynon pushed 1 new commit to master: http://git.io/lsSoAw
GitHub181 has joined #opal
<GitHub181>
[opal-todos] adambeynon pushed 1 new commit to master: http://git.io/eiWe_A
GitHub181 has left #opal [#opal]
<GitHub181>
opal-todos/master 86b41d0 Adam Beynon: Use haml instead of erb for index
travis-ci has joined #opal
travis-ci has left #opal [#opal]
<travis-ci>
[travis-ci] opal/opal#1610 (master - cfc5028 : Adam Beynon): The build passed.
<adambeynon>
meh`: look forward to that. they produce very good screencasts
<adambeynon>
meh`: also, I had a thought about some examples for the website
<adambeynon>
each example could be a big text area on the left, and the output on the right
<adambeynon>
e.g.
<adambeynon>
rspec
<adambeynon>
some example specs, which you can edit and run in the browser
<adambeynon>
so, none of this "install opal-rspec and see how good it is"
<adambeynon>
how about, "go to this page and run some mock() examples"
<adambeynon>
same with asciidoctor - simple text editor on left, and live html generation on the right hand side
<adambeynon>
and maybe an inline app with lissio - live edit and re-run
ryanstout has quit [Quit: ryanstout]
<adambeynon>
or that demo money app you made
<adambeynon>
edit-compile-run on the fly
<meh`>
adambeynon, sounds good
<meh`>
but how feasable is it?
<adambeynon>
meh`: I just wrote a proof-of-concept rspec one, and it works great
<adambeynon>
prefill with a simple User class, with 5 or 6 specs showing off the more complex rspec features, and it makes a killer demo
<adambeynon>
I think if people can see complex ruby code working with things like rspec/haml/erb/etc right there in the browser it will grab attentions a lot more
<adambeynon>
meh`: also, a step-by-step live tutorial .. going from a simple 1-liner app to something like a todos example
<meh`>
adambeynon, yeah, it sounds great for publicity
<fkchang>
adambeynon: I was thinking of a number of "opalcasts" in the near future. Part of opal starter kit is to have 2 steps to a new opal project, i.e. gem install opal-starter-kit; osk new static
<fkchang>
So I'd do one on that, and another on testing js w/opal-rspec
<adambeynon>
fkchang: I have been thinking about that as well. do you think its a good idea to keep it seperate to opal, or for opal to have a template built in?
<adambeynon>
i.e. like `rails new foo` vs `opal new foo`
<fkchang>
adambeynon: I like how this entails what ember is going to try to do in 2014, but I like how the ember cli supports a number of options, going to look at it for opal-starter-kit
<fkchang>
adambeynon: as part of built in vs separate. Right now I've planned to do these things in opal-starter-kit, static html/compiled js, opal-server, sinatra project, opal-rails. Down the road options like which libraries, etc.
<fkchang>
to include osk opalize-rails; osk opalize sinatra
<fkchang>
I have a few ideas behind the project. 1) there are different configs, so if I templatize them and get core team approval, it both makes it easy, and documents what's undocumented in one. With so many possible configurations, I think a separate tool that's easy to add templates to makes more sense than building it into the opal cli. For example, meh's elixir based opal stuff would be another template, and not something to build into
<fkchang>
opal CLI
<fkchang>
I should probably look at how rails app composer allows you to select a bunch of options/recipes
<fkchang>
I think we should put forth std options in the various configs, Rake, rspec, guard, etc..
<meh`>
yeah I agree, a different repo
<meh`>
but I'd still keep it under opal/
<meh`>
as in, the org
<fkchang>
I was going to suggest that maybe opal-starter-kit moves under the opal tree
<meh`>
I don't like the name much, but that's another story :P
<fkchang>
standardize but have options, and make it easy
<adambeynon>
yes, a few different templates is a good idea
<adambeynon>
an opal app vs. an opal lib is an obvious one I have differences with
<fkchang>
yeah, I need add a way to make a new opal gem
<fkchang>
down the road, I want to build sinatra and rack on top of opal node
<fkchang>
and support those as templates
dham_ has joined #opal
<fkchang>
I think the ability to possibly reuse rack code on opal-node would be good
<meh`>
I still see opal-node as a joke
<meh`>
or maybe it's just hope :P
<fkchang>
I think the intention was a joke, but I think running an opal based server on node could have it's benefits
<meh`>
I really can't see them
<meh`>
but it gets subjective, I find node.js a joke as well
<fkchang>
well, if u feel node.js is a joke, then opal-node is by defintion a joke. I think those cases where people use rails for the web app, and then delegate to node for say websockets or something, could instead be done only in ruby/opal
<adambeynon>
I remember the days when opal only ran on node - didnt even run in the browser at that point ^_-
<meh`>
fkchang, well, personally I'd never use Rails either :P
<fkchang>
adambeynon: what did you do w/opal running only in node
dham_ has quit [Quit: Page closed]
<meh`>
run opal :P
<adambeynon>
trying to get a ruby implementation with "megaspeed"
<adambeynon>
then I got bored, and wanted to write iphone apps using ruby
<fkchang>
adambeynon: so do you think "megaspeed" is possible via node?
<adambeynon>
fkchang: not if we want 100% ruby compliance
<adambeynon>
we could get comparable performance
<fkchang>
mabye there's a place for opal.x
<fkchang>
the Xtra fast opal variant
<adambeynon>
by the time we consider mutable strings, integers/floats, real method_missing, better module/method/super definitions, we would be hitting a lot of speed traps
<adambeynon>
saying that, I am very noob when it comes to v8 internals
<meh`>
fkchang, if you want speed, you're looking in the wrong place
<meh`>
Rubinius and JRuby is where to look at
<fkchang>
never used rubinius, I might be one of the longest Jruby users (2004), though
<fkchang>
never tried deploying jruby to heroku, which is also a consideration, opal-node would probably have better start up and resource usages
<fkchang>
adambeynon: on improvments, how do you think ES6 will affect opal. I imagine the translation could be much easier
<meh`>
seeing as how we want to support IE6, it won't affect it in any way
<adambeynon>
yes, the problem is that we still have to support "legacy" browsers
<adambeynon>
current browsers today are legacy tomorrow
<adambeynon>
in 5 years we will still have to target ie9/ie10 for example
<adambeynon>
Hopefully the compiler is easier to subclass now, so you can customize outputted code for certain browsers
<adambeynon>
but, the most general case isnt going to improve too much I guess
<adambeynon>
which is also why I find all the excitement around js improvements quite odd: we cant actually use it in most cases
<fkchang>
meh`: yeah, I should do an opal-inspector video on IE6, and use retro graphics and music
<fkchang>
I have 8bit videogame graphics and music in my head
<meh`>
fkchang, that would be, for lack of a better word, epic