Thanks Tony An easy to use simple solution to this may be complex in the making, but > there is much that can be done to tame the complexity. >
I figured as much. In my other life, I translate between business requirements and tech spec for CMS. > I would be happy to provide some help and guidance on this especially if I > can generalise the solution, not your content. Especially if you are > prepared to work hard with me to achieve spectacular results. > A solution that others can use (which might even result in more, better books being written) could never go amiss. And, yes, I fully appreciate the work that will go into getting this right. It's far less than would go into having to rewrite a book a dozen times to try to fix all the continuity errors that result from not having it. > First are you the author or an analyst of another's work? This can change > the tools you will need. > I'm the author. As mentioned in a previous post, this is about building the material to be able to cleanly write the final manuscript rather than deconstructing something that already exists. > whilst you may wish to focus on character arcs I think others, perhaps > even your future self may want more. Imagin locations, story lines, > timeines, objects, periods and even time travel. Thus I think a generalised > method for various archs is best. Even more if it were a script for a play > or film. > No argument there. I was only focusing on the characters and their arcs because those are - at least in most cases - the more dynamic elements. (I already have a lot of data about family relationships, and these evolve through the course of the story with births, deaths, etc; I wasn't expecting to include that level of detail, and it would really complicate things because my world uses a different calendar.) Of course, time travel would make for a serious fun sort of dynamism. > We can simplify the ability to reorder items but it would be difficult to > ensure that the new order is valid depending on the structure and content. > There may be value if you are the author having a way to indicate pre post > or co requisites where necessary to warn against erroniouse reorders. > I wasn't imagining any sort of continuity enforcement in the model (though I would if I developed it from scratch as a more comprehensive tool, per a previous reply). I see it more as a case that, in reviewing something, I realise that an additional interaction is needed mid-story, so insert it and categorise appropriately. Then, I can check each of the arcs, story lines, etc it impacts and ensure it ahsn't broken any of those. > Structured correctly you would not need hundreds of different tiddlers > just effective ways of viewing the content from different perspectives and > the ability to record details to the side of such perspectives. > I won't complain about that. > In may ways you want a structured repository from which you can extract > mentions and relationships across the whole repository. > > This is an ideal application for tiddlywiki. > > What's the best way to approach the project? > -- You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywiki/b6cc3c55-006e-43de-b567-347e8aeae7cc%40googlegroups.com.
