colision detection , sounds, score keeping, and timers

well i posted all four of these because i did them the same day and i would like to consider them similar projects that and i hate having 100 short blog posts instead of a long hearty post. Oh and im kind of lazy.
collision detection was my first one which i ended up playing with on the last part of the game presentation last semester .hitTest ftw

we quickly moved from collision detection to score keeping mostly with the "if x is over y then points go up" .hitTest also during the score keeping we also had hit the button situations i used squids and during this i found out that you can have said buttons move so i have moving squids that when clicked either plus or minus the score.

after this i kept the same file open and made these same squids my player for music, so at this point i have the worlds most interactive mp3 player. (sad part is it only plays my story)

timer was added to my game test which is my constantly changing game file and i chose to use the dynamic text mySeconds++ type of code from the topic on the wiki.
i sitll got a lot to figure out but im starting to get the hang of this

finding solutions and learning from others

roughly both of these topics are relative because that's the pure basics of our class. to learn from others we got to be sure we are learning and not simply just plagiarize so when and if we copy code we make sure that we look up or try and figure out why the action script does what it does. As for finding solutions we roughly study look it up on the wiki, google solutions, and even you tube.

practice makes perfect

covered basically ways to code and making it so we remember strategies to encoding this flash.

welcome to the grind house (intro)

so this one's late but intro to action script was reiterating some basics. involving changing variables and some of the easier commands