For the critique session in tutorial, I actually missed out the multipath part and just went ahead with a single-framed approach. Nonetheless, what I prepared was something like a slideshow that users can click and shuffle through the panels, creating a single-framed comic.
The above was what I presented in class. Because of technical incapabilities, I went online to search for various single-frame codes before plonking in my images. Among all the many many codes that I found, I eventually chose this because I liked the little panels shown at the bottom. I thought allowing users the ability to navigate through different parts of the story.
However, there were quite a number of critiques for my work:
1. First and foremost, the multipath was missing from the presentation and was pointed out by Jing and peers.
My take: Would definitely edit the whole sketch to make it a single-frame, multipath comic. Some peers suggested that I could simply include different htmls for different paths, which might be the easiest and most effective approach for a dreamweaver un-saavy person like me. :( I took their advice and created a brand sketch 2 eventually (to be updated below).
2. The panels have to be looked through one by one before the shuffling takes place. If not, it would result in an ultra slow-motion of the shuffling action.
My take: I wasn't aware of this at all before the tutorial! My solution to this would be to change the whole thing because the lagging when shuffling among panels is just not acceptable as it reduces effectiveness and readers' interest when such things happen. I eventually remove the whole layout and changed into a new style of presentation. (Not using the slideshow code anymore)3. The panels before and after the selected panel are very distracting. Meaning the peek of the previous and the next panels are very distracting .
My take: Yup, I kind of agree with that. Especially when all the panels are white. I also thought that since it's a single-frame, the showing of the previous and the next panels might not be fulfilling the "SINGLE-frame" part well enough. Hence, I will definitely be changing the whole layout and codes to fulfill the single-frame and the multipath requirements.
--------------------------------------------------------------------------------------
UPDATE
I re-did everything and managed to code without using external source codes! Claps! :D
I did a simple single-frame comic and readers navigate by clicking on the image itself. When clicked, the image changes to the next panel (which links to another html page). This is for the single-frame requirement part.
As for the multipath part, since my story has different endings, I used the approach for the part whereby readers had to decide between going for surgery or not.
Buttons for "reject surgery" and "go for surgery" are created. By clicking on "reject surgery", readers will be led to a path which gives an ending of the princess waking up with lips still swollen. At this particular panel, a button "go for surgery" is placed at the end so that readers can always make a new decision to explore a new path.
When clicked on go for surgery, readers will be brought to this panel. Further decision needs to be made - for Sleeping Beauty to go through a gender change surgery or a failed lip construction surgery (thicker lips).
A gender change selection would lead readers to an eventual male Sleeping Beauty at the end of this path. Similarly, other decisions can be made by clicking on any button at the end.
The thicker lips path would end off with this panel. Of course, readers can choose the "reject surgery" path as well if that was not explored previously.
By changing the whole format for Sketch 2, I managed to fulfill both single-frame (click to move to next panel) and multipath (through the use of buttons) requirements. The buttons are carefully thought out to be placed on the ending of each path so that readers can easily navigate through the paths they have not explored. Also, through this tutorial, I learnt how to use adobe fireworks to create buttons and how to link the buttons to different htmls.
It was a TOUGH but fruitful experience exploring the tools and softwares. Phew! :))
Reflection
The technical part was crazy but I learnt that we could actually find codes online for whatever effect we want and then just edit accordingly to what we want! Woo! That's something I didn't know in the past. I thought codes have to self written. Haha. So it was really fruitful for me! :D
No comments:
Post a Comment