Summer 2010 week 3:—5/27/10: Wednesdays 12:25 - 3:25

Hi Everyone,
Once again, I really enjoyed class on Wednesday. I know this is not easy stuff and that it can sometimes be frustrating, but it seems to me that all of you are actively really trying to figure things out. This is what is important, not whether you get it right 100% of the time. I don't want to run this point into the ground, but it's worth mentioning again, so good for you. The main thing you should take out of this class is learning how to figure this stuff out, when you have an error or a problem that you want to solve, how is it that you go about figuring out how to do that.

With that point in mind, I want everyone to bring whatever text you have purchased to class this week. If you do so, you will receive the equivalent of a homework of credit. The main thing you need, the first piece of ammunition in your arsenal, the first tool you should have in hand when confronting the enemy of script errors is a reference text, so please make sure you get one and bring it to class. We may not have had a need to use it yet, but we will, I promise. Things do get more demanding in this class.

I'm sorry for posting this so late, but I figured two things: first, I told you what I wanted you to do for me for class next week; and second, it's a holiday weekend and so I'm sure you all understand if it has taken me a bit longer than usual to post. Enjoy your Memorial Day.
Carter-

1. WEEK 3
   
   1. Classwork
   • LINK    class file
   2. Homework
   • Exercise 1:    Using the file that I send you during class-time, with a working script that makes the movieclips work as buttons (this we did in class), make the FIVE BUTTONS load the FIVE EXTERNAL FILES (one.swf, two.swf, three.swf, etc) into the index when the buttons are CLICKED ON.
   • Exercise 2:    Remember to come in to class on Wednesday with an idea for your final project. This should include a basic mockup in the computer or drawn (NOT a 30-second sketch) and colored on a piece of paper. Use arrows or a storyboard to explain how the interactivity (when the user does things) might change the look of the page. Also, if you come in with some references to other sites with aspects that you like and would like to do this term, please do. Make decisions now even if you think you may change your mind later. Be prepared to stay a few minutes after class to discuss your ideas with me.
   • Exercise 3:    Come to class with your text, and remember, this can be any text that you think best, just make certain you have a reference. Bringing this and showing it to me will be the equivalent of a homework grade.

Summer 2010 week 2:—5/20/10: Wednesdays 12:25 - 3:25

Hi Everyone,
I'm excited about this class this term, and excited to have all of you in the class. It may seem difficult to some of you, but if you stick with it you'll be very happy with what you produce this semester. I enjoyed class this week because most of you (with a few exceptions) seem interested, engaged, and enthusiastic. The rest of you who are NOT, if you make a bit more of an effort to try and be excited, I promise that there is an interesting payoff at the end, when finally you'll begin to wrap your hands around coding and programming.

I'm sorry, once again, for being late in posting this week's blog. I seem particularly busy this term, and that business last week with my computer failure has just put me off-balance. Anyway, let's hope I'm back on track this week.

About this class, understanding is the most important thing, NOT getting it completed perfectly without mistakes. Challenge yourselves to truly understand what we're really doing, THAT is the key. Please don't just use your neighbor's script. Go step-by-step through the lesson, and the moment you come to a term or something that you do not understand, ask someone to explain it to you until you grasp it. Don't just ask for the script that I'm looking for for you to type down. That will NOT help you in the end.

Because of my tardiness this week, you'll only have two simple things to do. Please do NOT come to class without them.

Have a nice weekend!

1. WEEK 2
   
   1. Classwork
   • LINK    class file
   2. Homework
   • Exercise 1:    Remember to come in to class on Wednesday a MOCKUP of your final portfolio project.
   1. You must do this mockup in PhotoShop and/or Illustrator;
   2. It must look as close to your idea for the OPENING PAGE of your portfolio site as possible—this is NOT a finished and final design, however, only a first draft, but please do not come to class with a bunch of plain rectangles;
   3. Decide your colors, your fonts, where the title will go, where your menu will go, etc.
   4. Also, if you come in with some references to OTHER sites with aspects that you like and would like to do this term, please do. Graphic ideas too, like sketches, drawings, storyboards also help. The more work you do each week, the better your final project will be, especially now early on when your homework and projects aren't yet piling up.
   • Exercise 2:    Create a very simple Flash file that uses a looping structure to do something. Try to be CREATIVE!!!

Summer 2010 week 1:—5/12/10: Wednesdays 12:25 - 3:25

Hi Everyone,
This is the blog for our class, DMA213, Interactive Multimedia.

Regarding this week's work, please make certain you understand most of what we did in class this past Monday. Each week, I will post two things: (1) the files that we produced in class that week; and, (2) the homework that will be due the following week.

Since I am really just now starting this blog, it will take me some time to get it into shape. So, if you have any difficulties with it, please let me know.
Carter-

1. WEEK 1
   
   1. Classwork
   • LINK    class file
   2. Homework
   • LINK    homework files
   • The first file in the folder that you download contains a few things that may be new to some of you but which you should know about:
   1. an invisible button--This kind of button contains graphics in only one frame.
      To Do:
      • Enter into edit mode for the invisible button to find out in which frame the graphic is drawn.
   2. a trace() action--

      The trace action functions similarly to the alert() function in JavaScript. It is simply used to provide some sort of information, some "output" to the user or to the person who is writing the script. Often, the alert() actions in JavaScript are only used temporarily, allowing the one who writes the script to find out something about what is happening in the script. That is the same for the trace() action in ActionScript; however, the trace() action is ONLY used by the programmer.

      In this case, we can see that the function is actually functioning. How do we know this? Well, we know that the button is calling on the function to activate this. How do we know this? We know it because the trace action actually 'happens'. If the function named invis_fun() weren't working, the trace action would never happen, even if you click on the invisible button. So, we know that the function is occurring simply because the trace() action actually appears.

      To Do:
      • Enter into the ActionScript and tell me what is the name of the function and what is the instance name of the button that activates it.
   3. an animated button--This is a button that contains movieclips inside of it.
      To Do:
      • Enter into edit mode for this button and tell me how many movieclips does it contain?
   • The second file and the third file do the same things, only the code for these two files is slightly different.
     To Do:
     • Enter into the ActionScript for each of these files and then list for me the differences that you notice between the scripts you see there. Once you do that, analyze the differences and try to explain to me what would be the purpose of the differences may be. If you are not sure, that's fine, just create a hypothesis.
   3. Extra Credit
   • exercise 1:
   1. Create a rectangle.
   2. This rectangle should have both a fill and a stroke.
   3. Select ONLY the fill and convert it into a movie-clip symbol.
   4. Once you do that give it an instance name.
   5. You should then select the entire stroke (but not the fill) and convert it into a movieclip as well.
   6. It should also have an instance name.
   7. Then, select both of these new movieclips together and convert them into a single new movieclip symbol.
   8. Provide it also with an instance name
   9. Then, enter into symbol edit mode.
   10. Once inside, select the fill and stroke movieclips and select 'distribute to layers'.
   11. Create another layer (put it on top) with a dynamic text field inside of it.
   12. You should also give this text field an instance name.
   13. Exit edit mode
   
   
   
   14. In ActionScript, type the necessary code to make the stroke and the text change colors (both to the same color) when you mouse over the rectangle.
   15. You should also type the necessary code to make both the stroke and the text go back to their original colors when you mouse back off the rectangle.