Re:Create a Game Character with HTML5 and JavaScript
by mrspeaker on Wednesday July 06, 2011 @06:08AM
(#2733219)
Errrgh! That's a shame his site died - a great tutorial on giving character to your characters. When the player sprite is standing still he independently (and subtly) adds breathing motion and limb motion, and blinking.
If you make games, then bookmark it and come back later!
Re:Create a Game Character with HTML5 and JavaScript
by messel on Wednesday July 06, 2011 @09:22AM
(#2733739)
thanks for the review. I hit the site was about to give up but will review it later. Bringing life to characters through animation is well worth checking out for a budding clientside coffeescripting, canvas slinging, html5'er
Re:Create a Game Character with HTML5 and JavaScript
by jechen on Wednesday July 06, 2011 @05:47AM
(#2733158)
This guy's HTML5 tutorials are freaking amazing, honestly can't express how grateful I am to people who's willing to put in the extra effort to help others learn. The servers are being hammered, though.
Re:Create a Game Character with HTML5 and JavaScript
by gary4gar on Wednesday July 06, 2011 @08:48AM
(#2733620)
All just because of twitter :-(
Warning: file_get_contents(http://api.twitter.com/1/statuses/user_timeline.xml?screen_n...) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 400 Bad Request in /home/content/w/i/l/willieohwillie/html/twitter/twitter-cacher.php on line 86
Fatal error: Cannot use string offset as an array in /home/content/w/i/l/willieohwillie/html/header.php on line 319
Re:Create a Game Character with HTML5 and JavaScript
by jasonkester on Wednesday July 06, 2011 @06:07AM
(#2733216)
Amazing that anybody would actually put 3rd party API code on the main execution path for rendering their site. What's the best case result? That your website renders correctly after only a 1 second pause?
This sort of widget is best lopped off entirely, or if you think it's absolutely essential, it's something that you load from javascript after all your resources have finished loading and rendering.
Never put your users' experience into the hands of a 3rd party. Other people's code is, nearly without exception, non-debugged, brittle garbage. Wrap it in four layers of try/catch and for the love of jebus, keep it out of your critical path.
Re:Create a Game Character with HTML5 and JavaScript
by jqueryin on Wednesday July 06, 2011 @07:24AM
(#2733370)
And here's the straw that broke the camel's back:
file_get_contents(http://api.twitter.com/1/statuses/user_timeline.xml?screen_name=williamMalone) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 400 Bad Request in /home/content/w/i/l/willieohwillie/html/twitter/twitter-cacher.php on line 86
Fatal error: Cannot use string offset as an array in /home/content/w/i/l/willieohwillie/html/header.php on line 319
Add some error handling and skip showing your timeline when this arises and be on your merry way.
If you make games, then bookmark it and come back later!
Edit: nevermind, it doesn't cache the javascript so the example doesn't actually work
The google web cache was viewable: http://webcache.googleusercontent.com/search?q=cache:QKa7OUg...
Yeah I think HN did some hurt :b
Warning: file_get_contents(http://api.twitter.com/1/statuses/user_timeline.xml?screen_n...) [function.file-get-contents]: failed to open stream: HTTP request failed! HTTP/1.1 400 Bad Request in /home/content/w/i/l/willieohwillie/html/twitter/twitter-cacher.php on line 86
Fatal error: Cannot use string offset as an array in /home/content/w/i/l/willieohwillie/html/header.php on line 319
try { file_get_contents(http://api.twitter.com/1/statuses/user_timeline.xml?screen_n...); } catch (Exception $e) { }
OR
if ($contents = @file_get_contents(http://api.twitter.com/1/statuses/user_timeline.xml?screen_n...) { //stuff }
This sort of widget is best lopped off entirely, or if you think it's absolutely essential, it's something that you load from javascript after all your resources have finished loading and rendering.
Never put your users' experience into the hands of a 3rd party. Other people's code is, nearly without exception, non-debugged, brittle garbage. Wrap it in four layers of try/catch and for the love of jebus, keep it out of your critical path.