<adambeynon>
I havent had a chance to look at either project/repo yet
<boberetezeke>
cool, how do I it?
<adambeynon>
boberetezeke: I think I need to grant permission
<adambeynon>
will have a look when im back at my laptop
<adambeynon>
out atm
<fkchang>
adambeynon: cool, any possibility of revisiting the code/comment look up stuff? I'll be a doing a bit of opal work in the near future, will probably write some tooling
<adambeynon>
will be back in a few hours
<boberetezeke>
ok
<fkchang>
meh`: nice, so you're going to enter that?
<meh`>
yeah
<adambeynon>
fkchang: yes, been working on some parser improvements which make it easier to keep track of comments as well
<adambeynon>
comments can now be set on individual def/class/module nodes inside the compiler
<adambeynon>
it also keeps single line comments, but they seem a bit irrelevant
<adambeynon>
but, are available if needed
<fkchang>
meh`: g'luck
<fkchang>
adambeynon: Cool, drop me a line when there's something that I can mess with
boberetezeke has quit [Ping timeout: 255 seconds]
<fkchang>
meh`: btw, u plan to open src opal-overwolf? it points to a local repo on your machine
linguini has left #opal ["ERC Version 5.3 (IRC client for Emacs)"]
<fkchang>
meh`: any thought on prerendering lissio
<meh`>
fkchang, as in prerendered in the backend? or what do you mean?
<fkchang>
prerendered on the backend. I read how react.js can pretty much do server side rendering and the components just "pick up" from that knowing they are already rendered. I remember you talking about something similar
<meh`>
fkchang, I think it sounds hard to do
<meh`>
but I think it's doable
<meh`>
but as soon as you have stuff depending on other stuff
<meh`>
it gets weird
<meh`>
as in, a component depending on an existing DOM, or another DOM
<meh`>
you'd basically have to implement DOM yourself
<fkchang>
my guess is that that react.js' virtual DOM is how they do it, since they diff the DOM before making any changes