Ok. We all know that there are currently 3 methods of
embedding data into our stacks.
We can:
1- Choose to import our elements
2- Use the full path to the element (begins from the HD name
right to the element)
3- Start from the stack's position and point to the image
directory (whatever you may call it)
The new "set directory to URL" is a feature that I (and
likely others) have asked Scott to implement. Basically you
would build your stack and point to all the elements locally on your
disk. When your stack is ready, you can publish it to the web
using a "set directory to URL" and then the stack can be
used by anyone on the net while the resources you used to build it are
being called from a directory at a specified URL. The first
implementation may require that you call the images directly from the
server while building it, but I'm hoping that provisions will be made
so we can build locally then using some type of "preference
setting" toggle the set directory to point to either a local
folder or to a desired URL.
So, instead of all your images or movies having the following as
a filename "data/images/bony.gif" they would actually look
like this
"http://www.your-url-here.com/projectskull/images/bony.gif". This way you can send out a runtime stack that loads
the resources from your server as the viewer runs through the stack.
Like me, you could build a MetaCard browser, this stack serves as
the MC engine and is actually devoid of any information. When
the stack is run it looks at your server and checks to see if there
are a list of other stacks, if so then it lists them. The user
clicks on a stack (typically 16k) and it instantly opens on their
desktop in runtime mode (due to the MC browser). When that stack
opens it calls all the resources from the server. You are
actually deploying stacks over the web in realtime!
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.
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)).
Clear as mud?
Simon,
Could you elucidate what this new "set directory" command is all about and how it will work?
rgds,
Blair
-----Original Message-----
From: Simon Lord [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, March 06, 2001 12:02 PM
To: [EMAIL PROTECTED]
Subject: RE: Making the case for non-browser "Web apps"
All we are waiting for now is for Scott and his crew
to implement a new *set directory* command which would allow all MC
users to point to "http://www/amigo-3.com/discreet/images/" rather
than to "data/images/story.gif" (the URL actually being the one you
want, not mine:^).
--
Cheers,
Simon
All your .com .net and .org domains for only $14.50 each.
Get them while they last... http://www.amigo-3.com/hosting/
--------------------------------------------------
"The great discoveries in science are not punctuated by 'Eureka! I've found it!' but rather "Hmmm,that's funny...." Isaac Asimov
Cheers,
Simon
All your .com .net and .org domains for only $14.50 each.
Get them while they last... http://www.amigo-3.com/hosting/
--------------------------------------------------
"The great discoveries in science are not punctuated by 'Eureka! I've found it!' but rather "Hmmm,that's funny...." Isaac Asimov
