Hiya Mark, Grimmwerks...
An thorough explanation seems to be in order.
I'm posting shockwave content (100 different SW movies) on the net. To be
able to keep User information, I have been told to use some kind of content
management system, which basically gives the Identificator appended to the
URL. The HTML containing the SW-movie is not dynamically generated (wish it
was), but is basically the default shockwave HTML. The URL targets, the
topframe, (which is not of my making), which in turn loads the correct
HTML-middleframe (containing the SW), and a non-dynamic bottomframe.
Thenagain, due to my total incompetence in HTML, Javascript etc, this has
ebcome an excercise in futility. I really do not know, where the proble is,
but I am not able to grab any "externalparameterValue" - things into the
shockwave at all....
Pekka
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]On
> Behalf Of Mark R. Jonkman
> Sent: 23. heinäkuuta 2001 2:46
> To: [EMAIL PROTECTED]
> Subject: RE: <lingo-l> Retrieving HTML parameters from URL
>
>
> Hi Pekka
>
> are you perhaps simply looking for
>
> externalParamValue ("SRC")
>
> -- this will give you the portion of the object and embed tag
> that contains
> the shockwave movies location (at least relative to the html page
> laumching
> it. It will also retrieve the querystring if any that has been added to
> the url of the dcr (does that make any sense?)
>
> IE. if you had the src param setup as
> something.dcr?what=nothing&who=someone
>
> then the externalParamValue("SRC") would return
>
> something.dcr?what=nothing&who=someone
>
> and you can then parse it out if you so desire.
>
> A much better way to handle the situation if your say using asp
> or something
> similar to generate the page would be to have the asp page parse the
> querystring as handed to the page and place them into sw parameters. If I
> recall correctly, you will need to use sw1 to sw9 as the parameters.. I
> believe IE pukes if you use custom named parameters while netscrap will
> handle custom named parameters properly.
>
> Therefore if I was using asp it would work out something like
>
> param = sw1 value= <% =Request.QueryString("what") %>
> param = sw2 value = <% =Request.QuerySting("who") %>
>
> (or however the appropriate method of writing the object tag
> parameters is).
> Then inside the movie, you make the assumption that sw1 is equal
> to what and
> sw2 is equal to who and handle it accordingly.
>
> don't know if that helps you or not
>
> Sincerly
> Mark R. Jonkman
>
>
> [To remove yourself from this list, or to change to digest mode, go to
> http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
> email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
> Lingo-L is for learning and helping with programming Lingo. Thanks!]
>
[To remove yourself from this list, or to change to digest mode, go to
http://www.penworks.com/LUJ/lingo-l.cgi To post messages to the list,
email [EMAIL PROTECTED] (Problems, email [EMAIL PROTECTED])
Lingo-L is for learning and helping with programming Lingo. Thanks!]
