Archive for the ‘100 DAYS PROJECT’ Category

100 DAYS PROJECT: #60

Monday, July 20th, 2009


On The Question of Ascension

60theascension
When I read Steve’s story the image I got was of Remedios the Beauty, a lovelier part of the family in Gabriel Garcia Marquez’s 100 Years of Solitude. I still see the women folding sheets in the breezes of the day when Remedios ascends into the sky.

So I took those ideas in this story and put it in the first person narrator telling about something that was going on when he was a child that affected his life in ways we can only grab a glimpse.

The mapping appears disorderly–like my early hypertexts–and yet I believe because the story is for the most part non linear there is some fun in hopping about to different thoughts and perspectives with the narrator.

100 DAYS PROJECT: #59

Sunday, July 19th, 2009


The Library

59thelibraryWhew. This one was a test of patience and skill and I’m not sure I’ve passed. It is a quest. There are clues that lead one through the story to discover what is required to complete what is essentially a word puzzle. While you may leave without guessing the answer–since unlike IF, this had to be based upon the honor system to allow progression of the story and a conclusion.

The map ended up becoming wonderfully geometrically symmetrical and if you’re stuck, you may choose to click above to enlarge it.

If you’re really stuck or just plain give up, you can email me for the solution.

HYPERTEXT & 100 DAYS PROJECT: Weaving Patterns

Sunday, July 19th, 2009


071999hThis is the Tinderbox map of Hypertext #59 The Library. What I’m planning here is a sort of IF influence on the piece by incorporating a quest, or task, separating the library into rooms, and providing clues within the stories that will lead to a successful ending.

Not all that easy. If I’m writing for the IF value, I find myself sacrificing story through the language as there are instructions and descriptions to be given to the reader. If I concentrate on the story, I lose the thread that must run through to allow the reader full access to paths leading to the ultimate ending while making sure all necessary information or clues are given and accessible via several choices of path.

But here’s the fun part: I’ve discovered the key to the puzzle is language-based and while I need to figure out how the clues can be ‘taken’ as ‘inventory’ as in IF so that they will all be available no matter how or in what order they are collected. The neat part is how the puzzle, the clues, and the solving all came in a pattern that I have to work to coordinate while making the story entertaining.

100 DAYS PROJECT: #58

Saturday, July 18th, 2009


The Appliance War

58theappliance-warWell, from a car that ignores a key and ignition, we anthropomorphized a kitchen.

Simple map, simple story of life in a normal society where those who are different make everyone else grouchy and anxious to rid themselves of the problem in the easiest way. The action taken isn’t always necessary if both sides are willing to compromise.

This just may be my first children’s hypertext story and I’d like to dedicate it to Sam (with parental approval, of course!) who just turned eight and may prefer warriors and good guys and may just inspire me to make up a few stories like that.

100 DAYS PROJECT: #57

Friday, July 17th, 2009


Listening

57listeningSteve did a magical thing with his offering this morning; telling an entire story from one side of a conversation over a telephone. It was touching and extremely well done.

I don’t hope to match it, but hypertext allowed the other side of the conversation to be heard. Then it dawned on me, why not try two different responses or calls being played out while still using the same comments from the central caller.

I’ve had some problems here with linking, but I think the reader will soon discover the trick in the story threads. The map is fairly simple, the stories are simple but completely separate though you may never know which one you’ve followed out until you get to the end.

100 DAYS PROJECT: #56

Thursday, July 16th, 2009


What We Missed

56whatwemissedCan’t believe I’m done early today. This story sort of wrote itself once I got into the mood of a bit of silliness though it can be construed as very dark and apocalyptic in nature depending on the path you take.

It’s more obvious in this piece what I took from Steve’s: a play on words of the title, but still a car trip with a family that travels in a time and place that lives in imagination. Mine’s not as weird as Steve’s, but then, I’ve always been a bit restricted in my writing.

The mapping process once again leaves it open as to just how much information the reader gets based on his own curiosity and nature.

100 DAYS PROJECT: #55

Wednesday, July 15th, 2009


Windows

55windowsFrom Steve’s story I picked up the second person point of view and its reflective nature. What came to mind was a scene from my own errand driving and the deep thinking one often does when alone in a car. From there it went on to more important problems than my own.

There are several ways to go through this story. Each is open to the trauma of losing one’s job and the fear that goes with losing even more. It could be nice to know all the random thoughts, but it’s just as well to see only a few, for those few are enough.

100 DAYS PROJECT: #54

Wednesday, July 15th, 2009


Semantics

54semanticsIn trying to establish a voice and a pace of story through dialogue, hypertext allows other issues to be separated out. In a previous hypertext, #49 Earth to Moon, it was pretty much all dialogue with some thought patterns and action interspersed. In #51 Snakes and Snails, there was a thread established where one could follow story by dialogue alone, with background information on the two characters as side trails.

In this, I have hoped to establish another dialogue-only thread but there is also an action and thought-only thread composed of body language between the two character. Alternately, the entire story can be read with all of the elements used.

HYPERTEXT & 100 DAYS PROJECT: Story

Tuesday, July 14th, 2009


Had a hard time with this last story, #53. It came in a flash as it used to, meaning the opening lines were all there. Without knowing where it was going, I started writing it out and stumbled many times through it. It was taking a direction that seemed forced into a hypertext structure and I think it would have been a very different story had I let it be straight text.

Also have a problem letting go of some of the stories sometimes and they affect what comes after. 24 hours just isn’t always enough to shake a story or characters out of my head. The last two stories were tough to write because the boys of #51 Snakes and Snails were still with me. I think that may be one of my favorite stories so far but when this happens, it’s a blight on what comes after. There’s a change of mood, a change of world, a change of comfort zone.

100 DAYS PROJECT: #53

Monday, July 13th, 2009


He Was What He Ate

53hewaswhatheateThis story started out as a brainstorm. Unfortunately, something about the hypertext form had me extending it into a tangle that was not what I had originally thought it would be.

It’s a fun little story but with some meaning in there about friendships, human nature, relationships, and one of my favorite subjects, food.

The map is pretty straightforward and I don’t think there’s any way of reading all spaces in one reading. The links and spaces are almost on a mesh pattern that just seemed to form naturally as I was writing.