Interactive Storytelling (IS)

xholonWorkbook.xml

<?xml version="1.0" encoding="UTF-8"?>
<!--Xholon Workbook http://www.primordion.com/Xholon/gwt/ MIT License, Copyright (C) Ken Webb, Sun Jan 18 2015 18:05:29 GMT-0500 (EST)-->
<XholonWorkbook>

<Notes><![CDATA[
Xholon
------
Title: Interactive Storytelling (IS)
Description: 
Url: http://www.primordion.com/Xholon/gwt/
InternalName: e5f1938c697204257895
Keywords: 

My Notes
--------
I just discovered this.
"Interactive Storytelling (IS) is a form of digital entertainment in which users create or influence a dramatic storyline through actions, either by issuing commands to the story's protagonist, or acting as a general director of events in the narrative. Interactive storytelling is a medium where the narrative, and its evolution, can be influenced in real-time by a user."[1]

It appears to be different from Interactive Fiction. It's more of an academic research area.

I ned to explore this some more.

References
----------
(1) http://en.wikipedia.org/wiki/Interactive_storytelling

(2) http://tecfalabs.unige.ch/mediawiki-narrative/index.php/Main_Page
    this looks very interesting

(3) http://www.erasmatazz.com/library/interactive-storytelling/what-is-interactive-storyte.html
    there's lots of interesting stuff at this site
(4) http://www.erasmatazz.com/library/interactive-storytelling/downton-abbey.html
    "I think of a soap opera as a collection of related stories without an overarching plot.
    Downton Abbey is precisely that.
    ...
    My observation here is that there is no higher story;
    the entire series is simply the conflation of all these intertwining small stories.
    ...
    This suggests a possible structure for interactive storytelling: a sequence of short stories.
    Each short story is small, but they combine in interesting ways.
    Such a structure would utilize something close to my interstitial story concept.
    The trick would be in coming up with a big set of interstitial stories AND a system for linking them together.
    That linking system is the killer problem."
    I like his description of this idea (KSW).

]]></Notes> 

<_-.XholonClass>

  <!-- domain objects -->
  <PhysicalSystem/>
  <Block/>
  <Brick/>
  
  <!-- quantities -->
  <Height superClass="Quantity"/>
  
</_-.XholonClass>

<xholonClassDetails>
  <Block>
    <port name="height" connector="Height"/>
  </Block>
</xholonClassDetails>

<PhysicalSystem>
  <Block>
    <Height>0.1 m</Height>
  </Block>
  <Brick multiplicity="2"/>
</PhysicalSystem>

<Blockbehavior implName="org.primordion.xholon.base.Behavior_gwtjs"><![CDATA[
  var a = 123;
  var b = 456;
  var c = a * b;
  if (console) {
    console.log(c);
  }
]]></Blockbehavior>

<Heightbehavior implName="org.primordion.xholon.base.Behavior_gwtjs"><![CDATA[
  var myHeight, testing;
  var beh = {
    postConfigure: function() {
      testing = Math.floor(Math.random() * 10);
      myHeight = this.cnode.parent();
    },
    act: function() {
      myHeight.println(this.toString());
    },
    toString: function() {
      return "testing:" + testing;
    }
  }
]]></Heightbehavior>

<Brickbehavior implName="org.primordion.xholon.base.Behavior_gwtjs"><![CDATA[
  $wnd.xh.Brickbehavior = function Brickbehavior() {}

  $wnd.xh.Brickbehavior.prototype.postConfigure = function() {
    this.brick = this.cnode.parent();
    this.iam = " red brick";
  };

  $wnd.xh.Brickbehavior.prototype.act = function() {
    this.brick.println("I am a" + this.iam);
  };
]]></Brickbehavior>

<Brickbehavior implName="org.primordion.xholon.base.Behavior_gwtjs"><![CDATA[
  console.log("I'm another brick behavior");
]]></Brickbehavior>

<SvgClient><Attribute_String roleName="svgUri"><![CDATA[data:image/svg+xml,
<svg width="100" height="50" xmlns="http://www.w3.org/2000/svg">
  <g>
    <title>Block</title>
    <rect id="PhysicalSystem/Block" fill="#98FB98" height="50" width="50" x="25" y="0"/>
    <g>
      <title>Height</title>
      <rect id="PhysicalSystem/Block/Height" fill="#6AB06A" height="50" width="10" x="80" y="0"/>
    </g>
  </g>
</svg>
]]></Attribute_String><Attribute_String roleName="setup">${MODELNAME_DEFAULT},${SVGURI_DEFAULT}</Attribute_String></SvgClient>

</XholonWorkbook>