Montes: Dekok: ok, yeah that COULD be
Clemmens: Dash: getUrl might be possible to solve differently i.e. by recreating the js-shim for each extension with the right return value built in
Mcalarney: Dash: there are other examples though which might be more problematic
Knotts: Dash: https://developer.chrome.com/extensions/runtime#method-connect
Cos: This returns a Port from a content script to the extension/background page
Herbison: Figuring out the chrome API as I go myself
Sowders: Anyone know canvas stuff? i can’t seem to get a rectangle to draw
Bromagen: Zap0: gist what u has
Sherratt: Dash: https://developer.chrome.com/extensions/extension#method-getViews — this one is particularly problematic
Todisco: As its used by lots of extensions
Dumphy: Returning the window objects of the other pages in the extension, for example the background page can control the options page
Matsushita: I can put those pages in the same webprocess, my idea would be to write another shim that posts messages between those pages when they call each others fake window objects and then eval on each others real window object
Kauo: This will be ugly, but fortunately is only 0.1% of the API
Jeffress: Dadada: yeah this is something you’ll need to add platform support for
Lurye: Dash: and this is why the last 10% take 90% of the work
Darbro: Rurik Dumb question: How do I know which callback function to use ? does the do***entation tell me?
Linzie: Rurik: what do you mean which callback function?
Kaak: Like, sometimes you do functionerr { }
Langdon: And sometimes functionreq, res
Linzie: Yes the do***entation will specify the arguments the callback will receive
Mullice: Hmmm. is there an easy way to link to the current page in html? Maybe “#” would cut it. although that would add # to the url in the browser.
Nasalroad: Do***ent.URL , location.href, .
Tuason: Yeah, with some js thats possible. guess there is no way without it.
Naz: Does anyone here know if gulp-livescript is working well?
Nason: Hey guys, did $array.splice get replaced?
Riesen: You mean array.splice? nope
Berlin: I keep getting a array.splice is not a function
Bessone: It’s not an array then
Tishler: And nothing is ever removed from JS
Manderscheid: I would like to migrate my personal projects from coffeescript to livescript and want to know if there is decent tooling support
Parsa: Xnil, were you ever in ##learnanylanguage before?
Trucchi: Boogymanx: might these happen to be DOM NodeLists?
Fugle: Maybe I should ask in jQuery though
Bergdoll: Https://dpaste.de/dU5U#L50 this is the line that gives me an error
Pulido: Xnil: LiveScript and CoffeeScript are far from anything that gets enough attention to have decent tooling.
Koning: Coffeescript has nice tooling. i really just need a linter
Canon: Xnil: it’s also not possible to write really decent tooling for either languages. Worse for CoffeeScript, though, which doesn’t even have correct lexical scoping
Olshefski: Can someone help me with this?, I have an arraw of ‘pending requests’
Ruezga: Xnil: you have a very broad definition of “nice tooling,” I guess…
Sohre: Dekok: what do you think about typescript? I just checked it out yesterday, looks like a nice abstraction
Pernice: Then for each new request I check if the key exists in the array and if it does it tries to reject the promise
Klostermann: I would really like to use javascript without actually writing any javascript
Appiah: Is that a correct approach to handle mulitple requests?
Trucchi: Xnil: unfortunately, there isn’t much in the way of tooling. it’s the major downside, and a shame. I gather that after the conversation earlier you read over all the differences and that’s why you’re asking the question ;-