Reflection Journal
Fourth Cycle - 03/14/05
Developing the interaction:
To determine the functionality (possible/impossible) of this interaction, I've created a simple interaction with very little attention to the design aspects. For now, the properties are simple MCs with only text, no illustrations or animations.
I've chosen this approach so I can focus solely on the programming of the interaction. I can add shine to it later! A key to checking if all parts are working has been utilizing the trace() function in my testing. This has helped me isolate problem areas.
The resulting interaction allows the user to drag-and-drop properties into either a workspace or a house. interface_mar13.swf: Combines all previous successes and failures and multiplies them by five. Includes:
- A moveable, recordable text version of each property (5 properties in 5 categories)
- An area for clues to be displayed one at a time
- A workspace to arrange properties, before moving them to houses
- A method of displaying house properties that has potential for verifying right answers
- All properties change the display of the houses, depending on what kind of property it is (character, animal, song, vacation spot, color)
From my reading in AS for Flash MX, I've learned how to write my own functions, create arrays, and put them all to use with loops. I've essentially cut out a HUGE amount of actionscript that would normally reside on every movable item and its target location. For me, this is a new day in actionscripting!
The interface and corresponding functionality has gone through an iteration of prototypes and revisions:
- interface.swf: only records the color "blue" on house 1. houses can be same color
- interface_event.swf: displays color for all houses. adds one property "opossum" to list (color block on right).
- interface_event2.swf: records answers in a more user-friendly manner. better integrated in to simple interface. shortens drag distance
- interface_event_window2.swf: records answers for all colors and one animal property on all houses.
- interface_compare.swf: checks for and erases duplicate properties on multiple houses. has 5 animal properties (five color blocks on right). "buggy" between checking color and animal properties.
- interface_compare3.swf: changes view of houses when an animal property is selected (turns on house light).
What else do I need to accomplish?
hide upper menu item
a) if it is in work area
b) if it is in property text area (set X value off screen)
show upper menu item
a) if it is released outside of work area or any house
b) if it is removed from property text area
needs:
instructions
a) how does the interface work?
b) how can the puzzle be solved?
example
a) basic three quality puzzle
b) show how to use matrix
helper items
a) printable matrix with clues
check answer
a) create string of prop fields
b) compare myString to correctString
wants:
timer
illustration for each property
animation of properties in action
links to related information
Gal - Footholds on Design (reevaluate knowledge based on new learning)
The rock climber analogy is perfect for this project. I've broken my project down into prioritized chunks and done my best to accomplish my project goals based on what I already know, what I've learned up to this point, and what I expect to uncover in my future learning. A glance into my project folder will reveal probably 100 different project files. Some are mere tweaks, but constitute a large enough change and garner saving (and staving of the terror of saving over the original "good" version). Programming is like that, you hit a problem and try to solve it one way or another. The weak "footholds" are discarded--but remembered, the necessity of learning from mistake and error--and the strong "footholds" are kept, followed or climbed. It may look like a straight line from version 1 to version 5 but there are many diversions along the way -- sometimes skipping steps in a shortcut and other times backtracking to the very beginning.
|
