Inputting the Films + Interactive Skin

Today was a very crucial part towards the development of my IMP. I was able to finally input my films into my media product along with the skin. This was not a very simple stage, which caused me to have a few sessions with my tutor regarding the stages involved in putting these into the mix. However, in the end I managed to link the films with my actual media product. I managed to integrate the skin into the film, which was done in the process, i.e. when actually importing the film, it was an option which I had to use my initiative to create. However, this was the code that I used to get the “Subtitled” version of my film into my IMP, and here is how it worked.

“function loadSubs(evt:Event)
 var urlReq:URLRequest = new URLRequest(“Subtitles.swf”);  
 var myLoader:Loader = new Loader();     
 myLoader.x = 120 ; myLoader.y= 60 ;
 myLoader.load(urlReq);   // passed to the ldr
 try { removeChildAt(4); }  //One bigger than the number of forms, starts from 0
 catch (e:Error) { }

 addChild(myLoader);   // display object container”

I first of all copied the code from a seperate document and then subsequently modified it to input my own details. Load  “Subs” is the name of the film, i.e. subtitles. Then the function acquired the URL which was in SWF format, and then loaded it in the IMP, about the coordinates (120,60), and then the object (the film and the skin) was then displayed.

This was a crucial part of my media product because without it, my product would not meet the requirements of the target audience and the Client Brief. Therefore this was mor ethan necessary, as the client brief desired 2 films; subtitle and non-subtitles. I was therefore able to integrate this succesfully.


Creation of Interactive Quiz

After the gallery, I managed to make significant progress regarding the completion of my quiz. I planned to incorporate a quiz that is interactive and useable by my audience. Thus, I managed to take the initiative to design my quiz which features a few questions and possible answers. The quiz is designed to develop the knowledge and understanding of the user.
Here is how the interactive feature’s code works:

var questionAndAnswers =
[“What do Muggers tend to use?”,      “Knife”, “Sock”,  “Spoon”, 0],

unction loadQuiz(evt:Event)
var urlReq:URLRequest = new URLRequest(“Quiz.swf”);
var myLoader:Loader = new Loader();
myLoader.x = 120 ; myLoader.y= 60 ;
myLoader.load(urlReq);   // passed to the ldr
try { removeChildAt(4); }  //One bigger than the number of forms, starts from 0
catch (e:Error) { }

addChild(myLoader);   // display object container

The question is posed at the top along with its possible answers, the URL from the actual media product requests the one from the actionscript that obtains the Quiz. This is then loaded in the coordinates (120,60). Then the objects are displayed.
These codes formulated the question and possible answers. Also they load the quiz in media product. This is relevant to the client brief because without it, it may not be as interactive as it could be, this provides a sense of amusement which is needed to fulfil the purpose of my media product and effectively appeal to its audience.

From One Form To another – Linking Frames

This is unquestionably a critical part of my entire media product. Today I managed to link every form to the main menu, which in turn allows easy access to each and eevery section of my media product. This allowed the user to navigate their way to my “scene selection”, “Outtakes”, “Quiz” and “Gallery” branches of my media product. This meant that I had to use the appropirate codings which had to be of supreme accuracy.
Here is how the frames work:

“frminteractive.btnplayquiz.addEventListener(MouseEvent.CLICK, loadQuiz); ”

This bit of coding works by looking at my interactive quiz form button (which opened the quiz) and allowed it to run after listening to the event.
This renderd me to be extremely accurate and careful with wordings as I made some mistakes which I fortunately rectified. This is crucial development process was relevant to my client brief because it allows the user to interact with my media product and find out some information regarding the subject of assult.

Creating Outtakes

Today I restored the movie clips (outtakes) to begin building it. As they were encoded, I had to”import” them to the library, after linking it. I also created the “skin” of the movie clips to ensure greater interactivity. These skins for my media product provided the user with the opportinity to fastforward, rewing, pause, stop and play as well as adjust the sound intensity.

It works like this:

” function OpenOuttakesForm(evt:Event)
if (frmmain.visible == true)
frmmain.visible = false; frmouttakes.visible = true”

The outtakes form is opened , which is the event, the main frame then allows the outtakes frame to become visible.This allows the user to view my outtake as it turned “visible” when the form “outtakes” is opened.

This is more than critical to my clients brief because it allows for the user to view uneditted footage filmed during my film. This adds greater value to my media product ensuring professionalism.

New Media product

I experienced a multitude of problems. This was mainly in terms of “visibility”. The frames were unusually refusing to dissapear causing major troubles and difficulty moving forward with my media product. We had absolutely no idea as to why these problems acrued, in which we spent days trying to figure out. This led me to delete the whole file and sadly starting all over again.

But nevertheless I still have access to these attributes in the files library. Hence, I shall apply those entities into my new media product as well as the codings.

Creating Home Button

Today I created a back “home” button. This was also a fundamental characteristic I previously planned to have, This button allows the user to easily navigate around my media product. It makes it functional and professional as it effectively works well and looks good too. This did however, mean that I had to consistently test it. As the buttons were added on each and every slide, connecting to the main page, it meant that I had to use accurate coding.

In fact, here is how the code works on every frame, i’ll use the scenes as an exmaple:

“frmscene.btnbackfromscenes.addEventListener(MouseEvent.CLICK, CloseSceneForm); ”

Starting at the scene frame, the home button is clicked on this page which causes the system to listen to the even, then after the click of the mouse the scene form is then closed; taking you back to the home page.
This code allows me to navigate back to the home screen, thereby making the entire media product  functional and useable. This is more than necessary than necessary to the client brief because it allows the viewers to navigate their way throughout my media product, again it makes it fuctional.


Whenever I built a new frame, incorporated a button and background image, I tested each and every one of them ensuring they work and mistakes are easily spotted. These tests proved beneficial as I encountered some minor problems which I overcame.

Previous Older Entries