On Thursday, May 3, 2012, C B wrote:
> I don't believe I saw any mention of this anywhere, but particularly
> in light of interested developers taking a look at the codebase again,
> has anyone looked at or had any luck with the notion of saving story
> state to allow a longer story to be "paused" and resumed from the same
> point later?

> I have not looked over the codebase myself, but those that are more
> familiar with it... how well structured is it as far as being able to
> simply serialize the variables and dump that out as a json file or
> something which could them be reloaded for a given user. I realize
> there would need to be some backend glue (like a user registration/
> login system). But if there was some simple function added that could
> "export" story state, and then an inverse function that could simply
> be fed that exported json (or whatever) file, to restore a story to
> the exact point in time/state (for stories with more complex branching/
> variable states) that would make longer form stories a hugely more
> enjoyable (user friendly) experience.

> I'm just beginning to play around with twee/twine, and it seems like
> an awesome tool (so if there is already a way to accomplish this,
> would appreciate anyone pointing it out to me).

> Otherwise, I would definitely submit this as a big wishlist item
> (forcing a user to keep a browser session seems like a step backwards
> from even paper books).

> Thanks :)

> --
> You received this message because you are subscribed to the Google Groups
> "Tweecode / Twine" group.
> To post to this group, send email to tweecode@googlegroups.com<javascript:;>
> .
> To unsubscribe from this group, send email to
> tweecode+unsubscribe@googlegroups.com <javascript:;>.
> For more options, visit this group at
> http://groups.google.com/group/tweecode?hl=en.