does flash wrapper mess with absolute url or flash params?
does flash wrapper mess with absolute url or flash params? My application reads an xml file which it gets from an absolute url string passed in as a flash parameter. It works without the widgetbox flash wrapper, but with the flash wrapper it acts like it cannot find the config file. Is there a problem with absolute urls, flash parameters, or flash xml when adding a flash wrapper? it works without the flash wrapper.
1
person has this question
I have this question, too!
Tell me when someone answers.
The more people who ask this question, the more it gets noticed.
The more people who ask this question, the more it gets noticed.
-
Inappropriate?Hi,
When your widget runs in our JavaScript wrapper or in a browser on it's own, it makes the request to your server to get the xml file which it can fetch fine because the flash and your XML file come from a shared domain. When your widget runs in our flash wrapper, the request for the XML comes from a widgetserver.com domain (the domain of our wrapper.) If you place a crossdomain.xml file at your server's root, you can grant access to *.widgetserver.com (See http://www.adobe.com/devnet/articles/... for more information on crossdomain.xml files)
Omar -
Inappropriate?I have added the crossdomain.xml with permissions already. I had to do that to get it to work on myspace http://www.myspace.com/boardermindtrick as a flash object without any widget service. So I have eliminated that as the issue. The code is in CS3, is that an issue?
I’m indifferent
-
Inappropriate?CS3/AS2/AS3 shouldn't matter. Our wrapper is AS3, compiled for Flash Player 9 and can load anything that is compiled for 9 or lower.
I see your SWF requesting the crossdomain file and then the settings XML file which means it was granted access for the request. My next guess is that there may be a silent runtime exception being thrown while parsing the XML when running in our Flash wrapper. The context of your SWF is slightly different when running in our Flash wrapper, for instance, because our Flash file is the top most SWF, the usages of 'Stage' will cause runtime errors as your SWF no longer has a reference to its Stage object when it's loading. (It does however once it's been added to the Stage or a MovieClip that is already on the Stage.)
Have you had a chance to look at our Flash Documentation? It may provide some insight into something that is either a "Gotcha" or something that is not supported. http://docs.widgetbox.com/developers/... -
Inappropriate?Thanks for the reply. I have thoroughly gone through the documentation and found one thing I missed. That is adding the wbx_softkey parameter.
However, that did not fix my issue.
Also thank you for mentioning the stage problem. I did not see that mentioned in the documentation, however, I am not calling stage anywhere so that did not resolve my issue either.
I am really running out of ideas but need the flash wrapper to work for me to use widgetbox. If I am getting a runtime error somewhere, is there a simple way to trap any runtime error from anywhere in the app so I can pop up a javascript alert to see what error it is?
I’m sad
-
Inappropriate?I've tried the javascript alert, but I think that is blocked so I can't see what is wrong. Any suggestion on how to popup a message in flash so I can see the value of the suspect variables when I am testing the flash wrapper?
I’m frustrated
-
Inappropriate?To catch an exception in AS, you'll want to wrap the suspect code in a try/catch block:
try{
//some code that throws an error
} catch(e){
//do something if an error occurs
}
To display an error from within Flash, you can do 2 things: either change the allowScriptAccess parameter to "always" on the embed code snippet that we provide so that your single instance of the widget IS allowed to call javascript. The other option is probably more work, but you could display a textfield inside your widget when the error happens and fill it with the text you want to alert. -
Inappropriate?I used the textbox method of displaying variables and figured out that the xml file is being read properly and the page urls are also being read properly. They are just not rendering for some reason. I will have to try some more try/catch statements to see what I can find.
Since I have exhausted the technical docs for flash wrapper compatibility and have not found any other "gotcha", do you know of any "gotchas" that are not in the documentation? I would even be willing to let you look at our actionscript to see what is conflicting with the wrapper. I need the wrapper to work with this control for the myspace and facebook functionality.
Thanks
I’m confident
-
Inappropriate?Sure, go ahead and zip it up with the necessary files and email it to support@widgetbox.com with my name in the subject line. It'll be sure to get to me that way.
Thanks,
Omar
I’m gonna figure it out
-
This reply was removed on 04/06/09.
see the change log
Loading Profile...




