<wmnnd>
meh`: I'm not quite sure if I understand what you mean. If I do it like this, my own code still doesn't get mapped, but it works fine for opal/stdlib things: http://pastebin.com/C2RFPjjb
<meh`>
wmnnd, weird
<meh`>
sorry, I don't have any more ideas, guess you'll have to go with the cascading thing like I do in opal-browserf
<wmnnd>
meh`: However, unlike when I try to use a path under /__opal_source_maps__/ that actually doesn't exist, the links to where my maps should be return an empty 200.
Kilo`byte has joined #opal
<wmnnd>
So *something* seems to be there, maybe Opal is just not actually generating the maps.
gravityblast has quit [Read error: Connection reset by peer]
gravityblast has joined #opal
<gravityblast>
has anyone already tried ruby with opal on v8 loaded from c# on monogame deployed on wp8? cause I'm going to try, just to waste some time.
<meh`>
nope
<gravityblast>
nice answer, I can start then.
GitHub13 has joined #opal
<GitHub13>
[opal-browser] meh pushed 2 new commits to master: http://git.io/6fePiQ
GitHub13 has left #opal [#opal]
<GitHub13>
opal-browser/master 9e98954 meh: history: cleanup code and documentation
<GitHub13>
opal-browser/master 13ef6a3 meh: storage: cleanup code and documentation
<elia>
lol
travis-ci has joined #opal
<travis-ci>
[travis-ci] opal/opal-browser#67 (master - 9e98954 : meh): The build was broken.
<adambeynon>
we override the #run method, so we could use instance_variable_set()
<meh`>
I'll give it a shot
<adambeynon>
meh`: Its all coming back how painful it was to customize the rspec stuff for our current async stuff
<meh`>
adambeynon, is there a way to know if an example has finished?
<adambeynon>
meh`: again, not built into rspec, so we would need to track that manually inside the subclass
<meh`>
man
<meh`>
this shit is awful
<meh`>
I think I'm done
<meh`>
just have to stand up and go back to my room to test =_=
<adambeynon>
meh`: try looking through the rspec2 codebase :P rspec3 is much nicer
<adambeynon>
meh`: lol :D
<meh`>
ok, just a small problem
<meh`>
the header remains as passed
<meh`>
even if there are async failures
<meh`>
and it doesn't work in IE11
<meh`>
but that's another story
<meh`>
it works in Safari 5.1
<meh`>
adambeynon, were you using the async specs?
<wmnnd>
I'm having trouble with using erb files again. I have my file, item.opalerb and I have required it. But when I use Template["item"], I get a NilClass.
<adambeynon>
meh`: yes, quite a bit actually
<adambeynon>
It may be struggling due to the dom wrappers in IE11
gravityblast has joined #opal
<adambeynon>
I have only tried those in chrome
<adambeynon>
wmnnd: try inspecting Template.paths
<adambeynon>
It lists all templates
<meh`>
well, this should work
<meh`>
adambeynon, want to review the patch before I push it?
<wmnnd>
Oh, I have to use Template[full/path/to/template] ...
ryanstout has joined #opal
dfranciosi has quit [Remote host closed the connection]
gravityblast has quit [Quit: gravityblast]
<wmnnd>
adambeynon: If I want to pass a variable with a certan name to the template, do I have to do this via a wrapper class or is there a more elegant way?
elia has joined #opal
elia has quit [Quit: Computer has gone to sleep.]
<adambeynon>
wmnnd: variables in templates is a little tricky, as the template is getting compiled ahead of time
<adambeynon>
during compilation we dont know what are variables, and what are method calls
<meh`>
adambeynon, is the patch fine?
<adambeynon>
meh`: yeah looks fine
<meh`>
ok, pushing
<adambeynon>
if you want to use it now, you need to bump the gem release too
<adambeynon>
(and add a note in the changelog under "edge")
<meh`>
right
<adambeynon>
meh`: also, make sure to "rake build" first ;)
<meh`>
I can't
<meh`>
adambeynon, you have to do the release, I can't push the gem
<adambeynon>
meh`: oh, thats true
<adambeynon>
ok
<meh`>
pushing the change
<meh`>
then do your thing whenever
<meh`>
I'm using it from path temporarily
<meh`>
still a long night to fix it to work on IE11 =_=
GitHub133 has joined #opal
<GitHub133>
[opal-rspec] meh pushed 1 new commit to master: http://git.io/IyC59g
<GitHub133>
opal-rspec/master c7d6e14 meh: Add a timeout to async examples
GitHub133 has left #opal [#opal]
<meh`>
and by it
<meh`>
I mean opal-browser
<meh`>
adambeynon, yeah, wait a sec before pushing the gem
<meh`>
I have to figure out if the syntax error is in rspec or somewhere else
<meh`>
forgot about it
<meh`>
adambeynon, yeah, I didn't introduce the syntax error
<adambeynon>
meh`: so there isnt one?
<meh`>
there is one
<meh`>
it's pointing at runner.rb:24
<meh`>
specifically at the compiled source of Runner.new.run
<meh`>
I tried replacing setTimeout
<meh`>
with $$.setTimeout
<meh`>
so it's not the inlined thing that's broken
<adambeynon>
meh`: what complains? the opal compiler?
<meh`>
no, IE11
<meh`>
it raises a SyntaxError
<adambeynon>
meh`: can you copy/paste the generated source line
<meh`>
adambeynon, yeah, gimme a sec
<meh`>
trying to install IE6 so I can see what's going on
<adambeynon>
meh`: it might be something before that, and the parse keeps on parsing optimistically
<ryanstout>
elia: what's the real requires branch?
<elia>
basicaly switches from passing requires from sprockets directly to handling them inside the processor
<ryanstout>
cool, I like that idea
<elia>
required files are included as sources inside Opal.modules
<elia>
and then executed at the require place
<ryanstout>
so then opal wouldn't depend on sprockets?
<elia>
probably
<elia>
I copied a bunch of stuff from the sass_importer inside sprockets itself
wmnnd has quit [Ping timeout: 260 seconds]
<ryanstout>
for my framework, my asset compilation is sort of different from how sprockets does it, so I'm debating if I want to write a simple thing to do the basics of what sprockets does, but how I need it
<elia>
how's different?
<ryanstout>
so I've got it where stuff is broken up into components like this: app/component1/controller, app/component1/views, app/component2/controller, etc... So I want it where you could go to /assets/component1 and get the stuff from component1, but the problem is if I just ass the /app/component1 to the path, then all of the other files will be visible, some of which within the component shouldn't be. If that makes since
<meh`>
adambeynon, it wasn't what I thought
<meh`>
adambeynon, it was actually querySelectorAll
<meh`>
I didn't think it would raise on syntax error in the selector
<meh`>
so I didn't wrap it up
mneorr has joined #opal
<meh`>
but still
<meh`>
none of those xpaths work
<meh`>
must have done something wrong that doesn't work in IE
<meh`>
wait
<meh`>
what
<meh`>
they discontinued xpath in IE10
<meh`>
...
<meh`>
this is madness
<ryanstout>
meh`: really?
<meh`>
UPDATE 26/7/2013 IE11 isn't stable yet, but it still doesn't support document.evaluate. If it won't support it in the stable release, I doubt it will ever support it. Needless to say this is ridicolous.
<meh`>
yes
<meh`>
really
<meh`>
UPDATE 23/11/2013 IE11 is stable now but, sadly, it doesn't support document.evaluate. As heavy-weight XML documents are used less and less in web applications in favor of JSON or other light notation formats, this is becoming less of a problem, but still.
<meh`>
what the fuck is wrong with them
<ryanstout>
meh`: that sucks, I was looking up special comments with that
<meh`>
ryanstout, I'm not going to add a huge dependency like that to opal-browser
<meh`>
especially not something by Google
<ryanstout>
yea
<ryanstout>
you could just say if you want IE11 support, conditionally include it
<ryanstout>
what do you use xpath for in opal-browser?
<meh`>
ryanstout, tests
RoxasShadowRS has quit [Quit: Leaving]
gravityblast has joined #opal
<meh`>
ryanstout, you know what? fuck that, I'll support wgxpath
<meh`>
adambeynon, can we fix async specs ending up in random groups?
<meh`>
it's not helpful
<meh`>
adambeynon, also I think there's a bug in IE with yield
<meh`>
without I think, it's failing, hard
<adambeynon>
meh`: I suppose we could tag the example group elements with an id, based on its object id to make them easier to find later on
<meh`>
adambeynon, even having them format AFTER everything would be better than this
<meh`>
now I'm getting even asynchronous issues with IE11
<meh`>
that don't make sense
<meh`>
and since I can't trust stacktraces
<meh`>
I don't even know what I'm looking at
wmnnd has joined #opal
gravityblast has quit [Quit: gravityblast]
gravityblast has joined #opal
<meh`>
adambeynon, disregard that
<meh`>
it works
<meh`>
adambeynon, ok, all is green
<meh`>
adambeynon, how do we proceed with opal-rspec?
<meh`>
I can't push these changes without those fixes
<meh`>
I think
gravityblast has quit [Quit: gravityblast]
gravityblast has joined #opal
<gravityblast>
the first day in the opal channel has been exciting. I've also drunk a lot o camomilla and I'm going to sleep. have a good night brothers. coding vobiscum. aloha.