DAY 1: The Ambiguity and Complexity of Initial Study

I have set myself up for a journey of undoubted challenge and stretch. I never thought I would get into computer programming in my study of illustration. I never thought I could, it all looks overwhelming. When I found my purpose to employ programming into my work I also remembered something a role-model of mine said; “if you think you can't, then you must.” John Grinder said this, and it basically means if think you can't do something, then you must do it for the purpose of stretching, growing and expanding your horizons. I love this simple statement because it presupposes that you can do it. So, because I must learn it I will be stretching and expanding my horizons greatly. Not only that, I will be transitioning my identity from being an illustrator into a illustrative designer/programmer.


I have been mentally assimilating lots of learning material in relation to the programs that I will be using. How much of it I am actually digesting? I am not completely sure about that. What is important though is that I am learning enough to be able to render the work I am committed to achieving in this project. I am learning to use Flash CS5 and the inclusive scripting language, namely ActionScript 3.0. Flash is easy enough to work with because it is similar to other design applications I have used such as Photoshop and Illustrator. ActionScript is the computer programming element of this project.


ActionScript is an Object Oriented Programming language (OOP). Basically OOP is a way of creating a system of objects and events that interact with each other with the initiation from the user. More simplistically, it runs like a car does – in parts but runs as a whole. There are many multiple objects that come together to form a car. They all work in a system for the purpose of transport. Each of these objects systematically compile into components that interact with other components. These actions of objects and interactions between objects are called events. Just like a car also, there is a user (driver). The driver initiates events based on the interactivity with objects.

The Illustration I have presented is not exactly how OOP works but it works as a good representation for me in accordance with the analogy of the car. I am still learning and will make many more new distinctions. Although the information abundance has left me a bit confused in parts, it also leaves me excited with the opportunities it will bring.


Comfort, adventure, purpose, love, expansion and giving.


Sebastian