Thach: well I am thinking.

Cedrone: Use grunt then, it’ll give you perspective on how good gulp is

Rux: Chowder: garb the element do***ent.getElementById”element1″ then add the onclick event in your code

Rux: Element.onclick = update

Kalinoski: Django_ it is client-side, a feature of jQuery

Rizzuto: Lewix: so for each div I’d add an event listener? note: each cell in the grid is a div

Wach: Kalinoski: i wanna call the instagram api

Kalinoski: Hmm do they allow cross origin requests to the endpoint you want to hit?

Buczek: Idk how to call this:

Kobus: Https:// on step #3 for server side

Kovalchik: Is this how you call the a nested closure function line 32? –

Cadice: Not seem to be working for me.

Schaub: Not sure if the closure symantics is correct, either

Buyak: Can some have a look?

Kalinoski: Django_ are you getting an error when you request the token over AJAX?

Kalinoski: Codecutter: you need to wrap your functions in parentheses

Kalinoski: Function { console.log’woop’; }

Mate: Kalinoski: undefined; Console: ‘woop’

Kalinoski: Function { console.log’woop’; }

Mate: Kalinoski: SyntaxError: syntax error

Kunich: I just. ಠ_ಠ I don’t know why I was making things so difficult. This order invoice PDF uses 2 lines for each order and I was thinking in portals figuring I’d need to know the line height difference and what not, to get the content from the 2nd line. But the info on the 2nd line still follows the info on the 1st line, as the PDF is p****d from top to bottom, left to right. I can just treat it as one big line.

Granger: After parsing there’s no such thing as 2 lines, it’s just a big pile of consecutive information

Kiedrowski: Pedubeer. Just swallow it.

Weader: Woelfel, it’s two ‘#’ and more

Mondella: Kalinoski: like this? do I have to do it for line 3 too?

Unkn: Yeah, ## will require at least two ‘#’

Aus: What does that ‘g’ do?

Kalinoski: Codecutter you have to put the function whose result is being stored in “message” in parentheses also

Rudnicky: Woelfel: you’re not replacing it with anything

Swanberg: Woelfel: ”.replace//g, ‘new text’, function {}

Mate: Gillice: string ‘#testtesttest’

Laurenceau: That works as expected

Glunz: The function is useless

Manila: Kalinoski: can you update the pastebin?

Hornbrook: The second parameter is a string or a function

Degregorio: Yansanmo: it’s not very useful no

Cerecer: Console.log’#test###test####test’.replace/##+/g, ”

Mate: Gillice: undefined; Console: ‘#testtesttest’

Mate: Gillice: string ‘#testtesttest’

Mincy: The third parameter is flags

Kalinoski: Codecutter no I am on my phone and I don’t have a web server right now

Gwynes: I am starting out a new project for a client read-heavy, write-not so much, my stack up to now has been python flask. Would I gain anything by switching over to node + express + react?

Polakoff: Kalinoski: how about now?

Cuva: Added parenthese on line 3 and line 30

Thach: Absolute0: you can use React without switching to Node. You may get a lot from React if you’re writing very interactive applications. Switching to Node+express? Not really.

Thach: Absolute0: unless Python happens to not have libraries for the things you need, in which case if Node has, then switching to Node means you don’t need to write those yourself

Tomkus: Thach: well I am thinking of changing around my stack. Python has been my language of choice, but there a bunch of cool new kids on the block: Go, node.js, etc.