Live data from Hacker News

Walkway.js

connoratherton.com

31–40 of 53 posts

Re: Walkway.js

#31
Firefox 33.0.2 on OSX 10.9 here.

It renders well if the tab is in focus (fantastic work!) but there's a bug: if I open it in a tab in the background, and visit it later (after the animation would have completed?) I see only a nearly-blank page. Confused me for a bit, as I open mass-tabs here on HN...

Re: Walkway.js

#32
post #29

Earlier quoted context omitted.

Switched to Google domains a few days ago, still configuring it properly. Thanks for letting me know about the link, looking into it.

Do you happen to have any extra invites for Google domains?

Got one. Thank you to the folks on HN :)

Re: Walkway.js

#33
post #29

Earlier quoted context omitted.

Switched to Google domains a few days ago, still configuring it properly. Thanks for letting me know about the link, looking into it.

Do you happen to have any extra invites for Google domains?

I do if still needed, drop me a line (email in profile)

Re: Walkway.js

#34

Firefox 33.0.2 on OSX 10.9 here. It renders well if the tab is in focus (fantastic work!) but there's a bug: if I open it in a tab in the background, and visit it later (after the animation would have completed?) I see only a nearly-blank page. Confused me for a bit, as I open mass-tabs here on HN...

Same here (Chrome 38 on Win 8.1)

Re: Walkway.js

#35
Hey! Guy who did the Polygon PS4 and Xbox review SVG animations here.

This is really great stuff; has a super friendly API to boot.

FWIW, we also released a generalized library for some of the things we were doing WRT frame-based and duration-based animation:

https://github.com/voxmedia/metronome

(Reason being that for some animations, we wanted it to finish in a precise amount of time, but for others, maintaining frame rate was paramount, even if total elapsed time was longer)

Re: Walkway.js

#36

Firefox 33.0.2 on OSX 10.9 here. It renders well if the tab is in focus (fantastic work!) but there's a bug: if I open it in a tab in the background, and visit it later (after the animation would have completed?) I see only a nearly-blank page. Confused me for a bit, as I open mass-tabs here on HN...

I get the same problem, tried on both Chrome and Internet Explorer (Windows 7).

Re: Walkway.js

#37

Firefox 33.0.2 on OSX 10.9 here. It renders well if the tab is in focus (fantastic work!) but there's a bug: if I open it in a tab in the background, and visit it later (after the animation would have completed?) I see only a nearly-blank page. Confused me for a bit, as I open mass-tabs here on HN...

I guess OP doesn't use requestAnimationFrame, otherwise, it would wait for the tab being focused.

Edit: Checked the code. He uses requestAnimationFrame.

Re: Walkway.js

#38

Firefox 33.0.2 on OSX 10.9 here. It renders well if the tab is in focus (fantastic work!) but there's a bug: if I open it in a tab in the background, and visit it later (after the animation would have completed?) I see only a nearly-blank page. Confused me for a bit, as I open mass-tabs here on HN...

In Linux, I get a varying, incomplete image with Firefox (33) and nothing with Chrome (38).

Re: Walkway.js

#39
post #10

How would somebody do this w/ D3? Are there any similar bl.ocks that anybody knows about?

You can transition the stroke-dasharray property and use element.getTotalLength to determine the total length of the path. Here’s a bl.ock:

http://bl.ocks.org/mbostock/5649592

And here’s an older graphic that demonstrates the technique in use:

http://www.nytimes.com/interactive/2013/02/20/movies/among-t...

We also used this technique to render the progress map in The Russia Left Behind:

http://www.nytimes.com/newsgraphics/2013/10/13/russia/

Re: Walkway.js

#40
post #37

Firefox 33.0.2 on OSX 10.9 here. It renders well if the tab is in focus (fantastic work!) but there's a bug: if I open it in a tab in the background, and visit it later (after the animation would have completed?) I see only a nearly-blank page. Confused me for a bit, as I open mass-tabs here on HN...

I guess OP doesn't use requestAnimationFrame, otherwise, it would wait for the tab being focused. Edit: Checked the code. He uses requestAnimationFrame.

You meant the opposite though, right?
Post reply on HN