{"author_name":"GFM","cat":"LD #27","comments":[],"epoch":1377982800,"likes":3,"metadata":{"p_key":"38007","p_author":"GFM","p_authorkey":"7375","p_urlkey":"73623","p_title":"Good practices on coding during the compo","p_cat":"LD #27","p_event":"LD27","p_time":"1377982800","p_likes":"3","p_comments":"0","p_status":"UPD5","us_key":"7375","us_name":"GFM","us_username":"\/author\/gfm\/","event_start":"1377216000","event_key":"18","event_name":"LD27"},"text":"

Normally I’m really concerned with optimization and processing time. I’ve read about static variables and function calls being slow in as3, with some pretty convincing tests (which I’ve never tried, but seemed reasonable).<\/p>\n

But, this LD I didn’t want to waste time encapsulating stuff, creating a .xml file with all my constants and keeping references\/constants in the proper place. I’ve simply made use of a “Registry” class which holds everything that need to be accessed elsewhere.I’ve also added some many groups, each with lot’s of objects, to simplify things when recycling\/drawing. Well, I’ve just checked how long update and draw was taking and (surprisingly) update was 10 times slower than drawing! It should be the other way around!!<\/p>\n

Now I’ll have to try to find all the slow parts and rewrite it… and that’s probably most of the code…<\/p>","time":"August 31st, 2013 4:00 pm","title":"Good practices on coding during the compo"}