I am not a computer science major, but I am acquainted with the Tree structure. If you are familiar with Ficly, you might realize that Ficly stories are arranged like a tree-like structure. What I like about Ficly though, is that their trees are much closer in form to real trees.
Every story in a Ficly tree has one very important relationship: the story that spawned it, except in the case of the very first ficlet written in that tree: the ultimate seed. Ficly allows for users to compose not only sequels to a story, but also prequels. Much as a tree grows both up as branches and down as roots, Ficly trees grow forward with sequels and backward with prequels. Much like a tree’s thick trunk, the most content is usually concentrated around that ultimate seed. As well, any story can spawn more content both forward and back in time – much like the Banyan tree can drop roots from its branches.
The problem that arises with actually reading through Ficly trees is that there is no single thread that a reader can follow – the stories cannot be arranged in any ordered way along a line that will make sense. What Ficly needs is a way to view the entire tree. I have participated in other’s trees, and have spawned a tree of my own – the story of Verdanus and Tertius which I tagged with “Elysium” for easy searching. There are 14 stories (13 by me), and reading them in the order they appear in the search may or may not give you any idea of what is happening. However, after fifteen minutes of crude photoshopping, I’ve come up with this:
I’m not the programmer for the job – but you might be. If you have any experience with programming visual displays of node-to-node relationships, then this is right up your alley.