>From: Simon Lord <[EMAIL PROTECTED]>
>---- stuff deleted
>For CBT developers this would be great as it allows for total control
>over the text and other elements in a stack (just like a browser
>there is only 1 repository). If you shipped a CD ROM and decided to
>change a graphic then you'd be toasted. If you change an element on
>the server then all stacks running around the globe get the update
>the moment the stack calls it.
Not necessarily *toasted* with the CD implementation..you just need
to keep track of it. In my case, I have to reach teachers in *all*
parts of Texas (i.e. where a phone line is a luxury :), I am putting
all of the media on a CD, *but*..the system logs in to a server and
gets *updates*. The updates are either stored locally (user choice,
downloaded in the background) or I just store a link. Then, each time
that I am about to load a resource, I check to see if the
image/stack/movie/external object has been updated, and if the update
is local or remote. If it is remote, then I grab it from the server.
Of course, if we update *everything*, then I'm doing what you are
doing, only slower :)
>
>I'm telling you, MetaCard will really make it easy for us to deploy
>anywhere and still control our content. You can do this now but you
>really need to build a finely tuned script to keep track of all the
>resources being copied to the disk (you may want the user to cache or
>actually store a copy as they run through your stack - depends on the
>content, such as large movies (why download more than once in a
>session)).
Tracking is kind of a pain, but not technically difficult.
Mark J. Luetzelschwab [EMAIL PROTECTED]
Graduate Research Assistant (v) (512) 232 6034
Instructional Technology (f) (512) 232 2322
Reading and Language Arts:
http://www.texasreading.org
Archives: http://www.mail-archive.com/[email protected]/
Info: http://www.xworlds.com/metacard/mailinglist.htm
Please send bug reports to <[EMAIL PROTECTED]>, not this list.
