[aida] Aida use case
Søren Skogstad Nielsen
skogstadnielsen at gmail.com
Tue Mar 3 14:23:13 CET 2015
Thanks for your interest in the PicturesInYourHead app !
Here is a single screen shot where the user is caught populating his
library with an Interactive fiction story.
More screenshots can be found here:
A screencast video will show up later in this facebook group.
The project uses the AIDA 6.0 Dolphin Version. Ported by Bruno Buzzi
Brasesco I should say I am very thankfull to Bruno for this work :-)
And to Janko for the AIDA platform of course!
The combined editor/presenter is written in Dolphin 6.03.
In the following link you will find a lot of instruction videos which
presents the facillities.
of the editor part.
Video 3 and video 7 presents many of the facillities. Video 0 presents
principles and exerpts of three interactive fiction stories.
Concerning the architecture I forgot to mention that I created a proxy
layer between the Dolphin generated windows and views and the channels to
This Idea turned out to work very well.
Den torsdag den 26. februar 2015 kl. 17.16.08 UTC+1 skrev Hilaire:
> Hi Søren,
> I changed the subject to match the discussion topic.
> Your project looks like an interesting one, do you have any screen shot
> or video to share with us?
> Which exact version of Aida are you using?
> I guess you have the Desktop editor developed with Dolphin as well?
> Le 25/02/2015 13:10, Søren Skogstad Nielsen a écrit :
> > Hi Hilaire
> > A short note concerning the archetecture of my PicturesInYourHead app.
> > In interactive fiction the story unfolds depending on the activity of
> > the reader, the reader 'reads', then decides for some response and the
> > next section of text
> > is presented depending of this response.
> > In the PicturesInYourHead app. The server may respond on
> > one Textual channel, two sound channels and three image channels.
> > The channels may be updated each time the user responds.
> > Furthermore the authoring platform makes it possible to set up delayed
> > action events on server side.
> > When such an event occurs one or more channels may have to be updated
> > -------
> > I knew Smalltalk but had no knowledge of Server or Web architecture,
> > HTML or CSS.
> > But studying the AIDA architecture and bolts and nuts - ' How is this
> > happening?', 'Can I copy this trick?' i ended up with
> > the following architecture of the client server interface:
> > --------
> > 1 Sound channels
> > The server maintains two queues of soundfiles to play.
> > Whenever the client observes it has no sound to play/playing it asks
> > the server to deliver one.
> > This request is set up through a timer controlled ajax (soundhandling
> > I could not use a page refresh, because ongoing playing sounds was
> > then disturbed, (repeated/ truncated/stopped).
> > 2 Image channels
> > The server will update each channel at each reader response if needed.
> > I use an Ajax construct for that, so only the Image page elements are
> > updated
> > because a page refresh would disturb an ongoing sound.
> > 3 Textual channels
> > This channel is updated through ajax too, to just change this channels
> > element on the page.
> > 4 Delayed events on server side.
> > This is actually 'COMET' architecture i suppose.
> > A timed request is repeatedly sent to the server from the client.
> > And if a delayed event has happened, the server will ask the channels
> > to update the client.
> > Here is a link to the non web parts of the platform (Warning
> > everything is in danish) ;-)
> > http://picturesinyourhead.vpweb.dk/
> > many regards
> > Søren
> Dr. Geo - http://drgeo.eu
> iStoa - http://istoa.drgeo.eu
> Aida mailing list
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Aida