Had a difficult time with ExternalInterface today. Ok, swfs work nicely together with javascript on a webserver, but when you access them locally, there are some security issues you have to deal with. The app I needed to created needed communication in both ways, so from swf to javascript and vice versa.
When you run the app locally through your browser, you get the security warning. In the security settings, you can add locations of local trusted files. Thing is: if you need communication in both ways, you need to specify the directory of the swf file, not just the file itself. Otherwise, only swf to javascript communication would work!
I’ve been playing around with the Apollo public alpha for a few hours now. One thing I was looking for, was creating those cool custom chromed applications, so you aren’t stuck to those rectangular windows.
Tout court, this is how I did it:
- Create your Apollo application :-)
- Adjust your application xml, so it has systemChrome=”none” and transparent=”true”
- Add some style to your application mxml:
ApolloApplication
{
background-color:”";
background-image:”";
padding: 0px;
show-flex-chrome:”";
}
And magic: The application borders are gone!
The first public alpha of Apollo has launched!
Apollo is the code name for a cross-operating system runtime that allows you to leverage your existing web development skills (Flash, Flex, HTML, JavaScript, Ajax) to build and deploy rich Internet applications (RIAs) to the desktop.
I already experimented a bit with converting Flex Apps to Apollo standalone applications, and it rocks!
Get Apollo on Adobe Labs…
Recent Comments