boberetezeke has quit [Read error: Connection reset by peer]
boberetezeke1 has joined #opal
boberetezeke1 has quit [Ping timeout: 272 seconds]
alexst has joined #opal
alexst has quit [Client Quit]
alexst has joined #opal
boberetezeke has joined #opal
f-3r has joined #opal
boberetezeke has quit [Ping timeout: 272 seconds]
boberetezeke has joined #opal
boberetezeke has quit [Ping timeout: 272 seconds]
alexst has quit [Quit: leaving]
BlapecOol has quit [*.net *.split]
BlapecOol has joined #opal
j_mcnally has joined #opal
j_mcnally has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
f-3r has quit [Remote host closed the connection]
boberetezeke has joined #opal
boberetezeke has quit [Ping timeout: 272 seconds]
Zackio has quit [*.net *.split]
Zackio has joined #opal
professor_soap has joined #opal
professor_soap has left #opal [#opal]
elia has joined #opal
elia has quit [Quit: Computer has gone to sleep.]
fntzr has joined #opal
fntzr has quit [Client Quit]
e_dub has quit [Read error: Connection reset by peer]
e_dub has joined #opal
boberetezeke has joined #opal
elia has joined #opal
<adambeynon>
elia hey, so was playing with require_tree, and it all works great, I just needed it to support *.opalerb and also *.haml, which is supplied by opal-haml
<adambeynon>
so I have changed the code a bit to support custom processor subclasses
<adambeynon>
look ok for you? its currently on adambeynon/opal, not sure why
boberetezeke has quit [Ping timeout: 272 seconds]
<elia>
adambeynon, thumbsup
<elia>
:)
<adambeynon>
elia: also, I think its fair to say that .rb or .opal will be the main entry point from sprockets, so I think we can scrap the ERB processor, and just use our new one for Builder
<elia>
I don't follow (because I don't remember :S)
<elia>
adambeynon, long term I'd like to swtch the builder processors to speckets 4 api, which avoids tilt and resembles rack in simplicity
<elia>
that way they can work for both sides
meh` has joined #opal
<adambeynon>
elia: as in, to let sprockets go back to handling all our require stuff, or to keep with Builder/BuilderProcessors
<elia>
adambeynon, handling our require stuff I don't think (at least without explicitly boot the main file)
<elia>
adambeynon, actually I'm not sure where that could bring, what I'm sure of is that I don't like the builder as it is
<elia>
and uniforming apis could open new possibilities
<adambeynon>
elia: well, we seem to be reinventing sprockets just to avoid having to specify the main entry point to the application
<elia>
also it deals with passing on sourcemaps and metadata
<elia>
that's true
<adambeynon>
im going for a quick lunch.. and to ponder
<elia>
adambeynon, buonappetito ;)
boberetezeke has joined #opal
f-3r has joined #opal
GitHub137 has joined #opal
<GitHub137>
opal/master fa7e6f8 Adam Beynon: Support custom extensions in require_tree
GitHub137 has left #opal [#opal]
<GitHub137>
[opal] adambeynon pushed 1 new commit to master: http://git.io/vr8rHA
<elia>
adambeynon, should I start the release of beta1?
<adambeynon>
elia: couple of very small changes I need to implement first
<adambeynon>
supporting .erb files
<elia>
adambeynon, (Y)
<adambeynon>
although, I do wonder whether .erb files should be handled by Opal::ERB, as in to stop supporting sprockets style erb files
<adambeynon>
.opalerb as en extension is very ugly
<adambeynon>
then again, maybe being able to `require()` an erb or haml file isnt a great idea
<adambeynon>
actually scrap that, I do like being able to require them
ylluminate has joined #opal
boberetezeke has quit [Ping timeout: 272 seconds]
ylluminate has quit [Client Quit]
<elia>
:)
<elia>
adambeynon, totally up to you, I never used them so can't give any worthy advice
ylluminate has joined #opal
<adambeynon>
elia: the more I think about it, the more I think we should distance ourselves from sprockets. I like the idea of using sprockets as the entry point, but I think keeping it as just an entry point is a good idea
<elia>
adambeynon, fine by me, at the same time I feel that reuing the design effort that has been put in it's processor system is a good thing™
boberetezeke has joined #opal
e_dub has quit [Quit: ZZZzzz…]
professor_soap has joined #opal
<elia>
adambeynon, sidenote currently we can't require coffee files
professor_soap has quit [Client Quit]
meh` has quit [Ping timeout: 255 seconds]
<adambeynon>
elia: hmm, thats true. Adding it should be simple. I dont think we should rely on coffee-script though, but if it is available (required) then we can just process the file
j_mcnally has joined #opal
e_dub has joined #opal
e_dub has quit [Quit: ZZZzzz…]
e_dub has joined #opal
meh` has joined #opal
<meh`>
elia, ping
<elia>
meh`, hulla
<meh`>
elia, what's constructor in Opal.klass?
<meh`>
in a typical call
<elia>
it's a generated named function
GitHub111 has joined #opal
<GitHub111>
opal/master 1640296 Elia Schito: Update sinatra example app to use SM prefix
GitHub111 has left #opal [#opal]
<GitHub111>
opal/master 850469b Elia Schito: Relax sprockets requirements a bit
jingo has quit [Remote host closed the connection]
e_dub has joined #opal
e_dub has quit [Read error: Connection reset by peer]
e_dub has joined #opal
elia has joined #opal
meh` has quit [Quit: I don't want to live on this planet anymore.]
meh` has joined #opal
GitHub173 has joined #opal
GitHub173 has left #opal [#opal]
<GitHub173>
[opal-rspec] elia pushed 2 new commits to master: http://git.io/uoz7gQ
<GitHub173>
opal-rspec/master 88f8ce6 Elia Schito: Add the handy link to local opal
<GitHub173>
opal-rspec/master 830efb0 Elia Schito: rake is already in the gemspec
<elia>
adambeynon, you still around?
<adambeynon>
Hey elia
<adambeynon>
Sup
<elia>
I'm releasing a fixed opal-rspec
<elia>
and was thinking about getting out the first beta round
GitHub65 has joined #opal
<GitHub65>
[opal-rspec] elia pushed 1 new commit to master: http://git.io/U5MRcw
GitHub65 has left #opal [#opal]
<GitHub65>
opal-rspec/master 92ecba6 Elia Schito: Bump version
<adambeynon>
elia: sounds good. Beta seems a good idea. From what I can tell everything is working fine, but a chance to test with rspec would also be good
<elia>
yep
<adambeynon>
I was thinking about some extra jquery stuff as well, e.g. Timeout, interval and web sockets. Maybe a good idea to make them API compatible with opal-browser to try and keep a bit of consistency
GitHub123 has joined #opal
<GitHub123>
[opal-rspec] elia pushed 2 new commits to master: http://git.io/AWxM2w
<GitHub123>
opal-rspec/master 84d7f57 Elia Schito: Add default gem building tasks
<adambeynon>
elia: I am still confident that now we have real requires, we won't need to bundle a pre built version of rspec, and it should build any version
GitHub24 has joined #opal
<GitHub24>
[opal-rspec] elia pushed 1 new commit to master: http://git.io/Zn9wuQ
<GitHub24>
opal-rspec/master b123b18 Elia Schito: Build rspec.js before running the specs
GitHub24 has left #opal [#opal]
<adambeynon>
(Probably)
<elia>
adambeynon, yes, the only problem would be if the app already has rspec 3+ for cruby
j_mcnally has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<adambeynon>
Yes, that is true
<elia>
adambeynon, an alternative would be to ship the all rspec gems
j_mcnally has joined #opal
<adambeynon>
elia: you mean, vendor them in the git repo?
<elia>
adambeynon, yep, probably via submodule
<elia>
surely vendor em in the built gem
j_mcnally has quit [Client Quit]
<adambeynon>
That could work
<adambeynon>
Actually that's a nice solution
<elia>
I exhausted my cognitive resources, just enough to watch big bang theory… :)