These are chat archives for opal/opal

14th
Dec 2015
Martin Becker
@Thermatix
Dec 14 2015 00:25
@elia does that mean a performance improvement? or a code quantiy reduction?
Elia Schito
@elia
Dec 14 2015 00:33
Hopefully bug reduction, and better code readability
Forrest Chang
@fkchang
Dec 14 2015 01:20
@fazibear very cool, I'll probably make a port
Vais Salikhov
@vais
Dec 14 2015 06:55
@elia
tumblr_mlj0syTLbP1rf1e3ro1_250.gif
elia @elia just lost an entire minute watching dat gif, again 💥
Vais Salikhov
@vais
Dec 14 2015 09:53
LOL, sorry :wink2:
Elia Schito
@elia
Dec 14 2015 09:54
I enjoy it every time :D
Michał Kalbarczyk
@fazibear
Dec 14 2015 09:59
Thanks! @fkchang make a port for what ?
Martin Becker
@Thermatix
Dec 14 2015 11:21
I'm building a history module as the opal-browser history module appears to be broken
I'm wondering, should I need to worry about hash type history
Martin Becker
@Thermatix
Dec 14 2015 11:31
because I'm thinking of building two history modules and just requiring one or the other depending on browser support but I'm thinking of just not bothering with hash type URLS
the other point is I've been wondering do you need a url watcher for HTML5 history or not?
Elia Schito
@elia
Dec 14 2015 11:32
As I see it the problem with hash history is that people might want to use hash anchors for their intended use…
Martin Becker
@Thermatix
Dec 14 2015 11:33
so should I not worry about it and just support html5 History only?
Elia Schito
@elia
Dec 14 2015 11:34
Can't give a definitive answer, obviously it's your choice :) but if you can support regular urls too that should be enough IMO
Martin Becker
@Thermatix
Dec 14 2015 11:35
I thought there was only html5 push-state and hash-urls for javaScript routers
Elia Schito
@elia
Dec 14 2015 11:40
I mean, if the JS app can be loaded at any url and load up in a proper state that can be a solution, just sayin' anyway :)
Martin Becker
@Thermatix
Dec 14 2015 11:56
do I use hashchange event for checking if url has changed in html5?
Martin Becker
@Thermatix
Dec 14 2015 12:11
or do I even need a url listen for state change mechanism?
Elia Schito
@elia
Dec 14 2015 12:12
dunno, try looking up docs in MDN
Martin Becker
@Thermatix
Dec 14 2015 16:46
umm right, well it's done, whilst it still needs to be deployed to rubygems, there is now a pure opal router, one that isn't a wrapper
... almost
Martin Becker
@Thermatix
Dec 14 2015 17:03
ok, now it's done, forgot to deal with root :P
Forrest Chang
@fkchang
Dec 14 2015 17:30
@fazibear I was going to port asciify to something that runs on opal-playground
likely react.rb too
Michał Kalbarczyk
@fazibear
Dec 14 2015 17:31
@fkchang where I can find opal-playground ?
Forrest Chang
@fkchang
Dec 14 2015 17:39
a quick react.rb example on opal-playground. I could add inesita as one of the included libraries
ok here's a link to the repo, there is a link in the readme for an example app using the router
and now version 1 is available on ruby-gems :D